Evidence from Risk Management in Software Product Lines development: A Cross-Case Analysis

Software Product Line Engineering (SPLE) is a paradigm in software development that enables rapid development of new applications, by means of systematically reusing assets. To take effect and deliver the promised benefits, SPLE demands for substantial upfront investments, and manageable processes. Such a scenario leads to the need of a rigorous risk management, to be employed with the aim of decreasing the impact of problems that may occur during the projects' development, thus improving the use of resources. This work presents an analysis of two case studies of Risk Management practices in software product line projects, carried out in academic and industry settings. In order to synthesize evidence and increase validity of the results, the outcomes were compared by means of a cross-case analysis, in which we analyzed the identified risks, their assessment and the activities used to mitigate them. The results were mapped to highlight the insights in both studies.

[1]  Linda M. Northrop.  SEI's Software Product Line Tenets , 2002, IEEE Softw..

[2]  K. Eisenhardt.  Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[3]  Klaus Schmid.  An assessment approach to analyzing benefits and risks of product lines , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[4]  Gabrielle Durepos,et al.  Encyclopedia of case study research , 2010 .

[5]  A. Strauss,et al.  The Discovery of Grounded Theory , 1967 .

[6]  Janice Singer,et al.  Guide to Advanced Empirical Software Engineering , 2007 .

[7]  Silvio Romero de Lemos Meira,et al.  Risk management in software product lines: An industrial case study , 2012, 2012 International Conference on Software and System Process (ICSSP).

[8]  Klaus Pohl,et al.  Software Product Line Engineering - Foundations, Principles, and Techniques , 2005 .

[9]  Klaus Pohl,et al.  Software Product Line Engineering , 2005 .

[10]  C. Brodsky.  The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .

[11]  Daniela Cruzes,et al.  Research synthesis in software engineering: A tertiary study , 2011, Inf. Softw. Technol..

[12]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[13]  Joakim Pernstål,et al.  A multiple case study investigating the interaction between manufacturing and development organizations in automotive software engineering , 2008, ESEM '08.

[14]  Wanda J. Orlikowski,et al.  CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..

[15]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[16]  Colin Robson,et al.  Real World Research: A Resource for Social Scientists and Practitioner-Researchers , 1993 .

[17]  Alexander Brem,et al.  Case Studies as Teaching Tools , 2009 .

[18]  Laura Lehtola,et al.  The Focus Group Method as an Empirical Tool in Software Engineering , 2008, Guide to Advanced Empirical Software Engineering.

[19]  K. Seers.  Qualitative data analysis , 2011, Evidence Based Nursing.

[20]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[21]  Mel Ó Cinnéide,et al.  Experiences with Software Product Line Development in Risk Management Software , 2011, 2011 15th International Software Product Line Conference.

[22]  Peter Kaiser,et al.  An industrial case study of implementing software risk management , 2001, ESEC/FSE-9.