@conference { ISI:000382672700052,
	title = {Botched Releases: Do we Need to Roll Back? Empirical Study on a Commercial Web App},
	booktitle = {2016 IEEE 23RD INTERNATIONAL CONFERENCE ON SOFTWARE ANALYSIS, EVOLUTION, AND REENGINEERING (SANER), VOL 1},
	year = {2016},
	note = {23rd IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER), Osaka, JAPAN, MAR 14-18, 2016},
	pages = {574-583},
	publisher = {IEEE; IEEE Comp Soc; IPA; Reengineering Forum; Informat Proc Soc Japan, Special Interest Grp Software Engn; Japan Soc Software Sci \& Technol, Special Interest Grp Fdn Software Engn; Osaka Univ, Grad Sch Informat Sci \& Technol; Mitsubishi Elect; Microsoft;},
	organization = {IEEE; IEEE Comp Soc; IPA; Reengineering Forum; Informat Proc Soc Japan, Special Interest Grp Software Engn; Japan Soc Software Sci \& Technol, Special Interest Grp Fdn Software Engn; Osaka Univ, Grad Sch Informat Sci \& Technol; Mitsubishi Elect; Microsoft;},
	abstract = {Few minutes after a web-based software release, the release team might encounter log traces showing the new system crashing, hanging, or having poor performance. This is the start of the most nerve-wrecking moments of a product{\textquoteright}s release cycle, i.e., should one run the risk of not doing anything and users losing precious data, or of prematurely engaging the tedious (and costly) roll-back procedure towards the previous release? Thus far, only little attention has been paid by researchers to these so-called {\textquoteleft}{\textquoteleft}botched releases{{\textquoteright}{\textquoteright}}, partly because of lack of release log data. This paper studies 345 releases of a large e-commerce web app over a period of 1.5 years, in which we identified 17 recurrent root causes of botched releases, classified into four major categories. We then build explanatory models to understand which root causes are the most important, and to explore the factors leading to botched releases.},
	isbn = {978-1-5090-1855-0},
	doi = {10.1109/SANER.2016.114},
	author = {Kerzazi, Noureddine and Adams, Bram}
}
@conference { ISI:000392265300025,
	title = {Who Can Help to Review This Piece of Code?},
	booktitle = {COLLABORATION IN A HYPERCONNECTED WORLD},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {480},
	year = {2016},
	note = {17th IFIP WG 5.5 Working Conference on Virtual Enterprises (PRO-VE), Porto, PORTUGAL, OCT 03-05, 2016},
	pages = {289-301},
	publisher = {IFIP WG 5 5 Co Operat Infrastructure Virtual Enterprises \& Elect Business; Soc Collaborat Networks; U Porto; INESCTEC; Univ Amsterdam; Nova Univ Lisbon; UNINOVA},
	organization = {IFIP WG 5 5 Co Operat Infrastructure Virtual Enterprises \& Elect Business; Soc Collaborat Networks; U Porto; INESCTEC; Univ Amsterdam; Nova Univ Lisbon; UNINOVA},
	abstract = {Successful software projects require collaboration between team members. Efficient collaboration relies on both technical and social linkages. In this paper, we investigate whether a socio-technical analysis can support software contributors in identifying experts helping to review their source code. We mined the histories of five open source projects (OSS) from GitHub and examined both technical and socio-technical interactions based on Social Network Analysis (SNA). Mapping communication network to files co-edition network shows the existence of collaboration patterns between core teams and peripherals in the studied OSS projects. Our main contribution is the construction and mapping of three sources of social networks, in which contributors interact by co-editing, commenting or reviewing. We were able to identify behavioral patterns between core teams and peripherals related to the activity of code review. Our findings have implications on improving collaboration between contributors within virtual OSS communities witch drive teams{\textquoteright} performance and software products quality.},
	isbn = {978-3-319-45390-3; 978-3-319-45389-7},
	issn = {1868-4238},
	doi = {10.1007/978-3-319-45390-3\_25},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {Afsarmanesh, H and CamarinhaMatos, LM and Soares, AL}
}
@conference { ISI:000382224200013,
	title = {Who Needs Release and DevOps Engineers, and Why?},
	booktitle = {INTERNATIONAL WORKSHOP ON CONTINUOUS SOFTWARE EVOLUTION AND DELIVERY, CSED 2016},
	year = {2016},
	note = {1st International Workshop on Continuous Software Evolution and Delivery (CSED), Austin, TX, MAY 14-15, 2016},
	pages = {77-83},
	publisher = {Assoc Comp Machinery; IEEE Comp Soc; IEEE Tech Council Software Engn; ACM Special Interest Grp Software Engn},
	organization = {Assoc Comp Machinery; IEEE Comp Soc; IEEE Tech Council Software Engn; ACM Special Interest Grp Software Engn},
	abstract = {The recent surge in interest in continuous delivery has opened up the job market for release and DevOps engineers. However, despite an increasing number of conferences and publications on continuous delivery, smaller companies and start-ups still have a hard time determining the core tasks their future release and DevOps engineers should be responsible for (and what the differences between those two roles are), while universities are not sure what essential techniques and skills they should teach to their students. This paper performs an empirical analysis of online job postings to determine and compare the main tasks of release and DevOps engineers, globally and across countries. Our qualitative analysis shows that automation is the most important activity across the three roles, as articulated in job posting description data, and that the release engineer role combines the top activities of the DevOps and more traditional build engineer roles. Finally, different countries have a moderate degree of similarity between their ads, although each country has its specific focus.},
	isbn = {978-1-4503-4157-8},
	doi = {10.1145/2896941.2896957},
	author = {Kerzazi, Noureddine and Adams, Bram}
}
@conference { ISI:000380409500017,
	title = {Conceptual Alignment Between SPEM-Based Processes and CMMI},
	booktitle = {2015 10TH INTERNATIONAL CONFERENCE ON INTELLIGENT SYSTEMS: THEORIES AND APPLICATIONS (SITA)},
	year = {2015},
	note = {10th International Conference on Intelligent Systems - Theories and Applications (SITA), ENSIAS, Rabat, MOROCCO, OCT 20-21, 2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {In the course of process improvement, software organizations attempt to concurrently implement practices that originate from different models, extracting the best from each. Issues of integration and compliance are raised due to missing conceptual view. This paper presents a new method for an explicit alignment between SPEM-based software process modeling and CMMI corpus of best practices. The alignment of process activities with CMMI goes beyond the maturity assessment; it sustains the conceptualization of introducing new software engineering practices at the process-level and open a new topic of combining conceptually parts of different process models. Our method extends the SPEM Meta-model by introducing new interface to CMMI Meta-data. This extension allows visualization of the practices{\textquoteright} intentions within the activity breakdown structure. In addition, it offers a conceptual assessment of process maturity level according to CMMI scales. The method has been fully implemented in a process modeling tool and applied in both academic and industrial contexts to justify improvement opportunities through meaningful dashboards.},
	isbn = {978-1-5090-0220-7},
	author = {Kerzazi, Noureddine}
}
@conference { ISI:000380409500022,
	title = {A Strategic Release Planning model from TPM point of view},
	booktitle = {2015 10TH INTERNATIONAL CONFERENCE ON INTELLIGENT SYSTEMS: THEORIES AND APPLICATIONS (SITA)},
	year = {2015},
	note = {10th International Conference on Intelligent Systems - Theories and Applications (SITA), ENSIAS, Rabat, MOROCCO, OCT 20-21, 2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {Release planning is a tedious task, especially within the context of Third Party Application Maintenance (TPM). Software engineering fields acknowledge multiple methods and techniques applied to solve problems of release planning. However, few of them propose a pragmatic and decision support dedicated to TPM managers. This research attempts to apply theory and methods Search-based software engineering (SBSE) area such as meta-heuristic techniques to solve complex release planning problems faced by TPM organizations. The aim of this paper is to introduce a strategic release planning model based on several TPM factors and constraints, allowing the TPM manager to carry out an effective roadmap and industrialize the planning process of software maintenance.},
	isbn = {978-1-5090-0220-7},
	author = {Naciri, Samia and Janati Idrissi, Mohammed Abdou and Kerzazi, Noureddine}
}
