Risk management in software product lines: An industrial case study

Software Product Lines (SPL) adoption can affect several aspects of an organization and it involves significant investment and risk. This way, SPL risk management is a crucial activity of SPL adoption. This study aims to identify SPL risks during the scoping and requirement disciplines to provide information to better understand risk management in SPL. In order to achieve the previous stated goal, a case study research was applied in an industrial project in the medical information management domain. Using the captured risks, a classification scheme was built and risk mitigation strategies were identified. We spent five months, totaling 79 hours, performing risk management (RM) in the scoping discipline and twelve months, totaling 148 hours, performing RM on the requirements discipline. We identified 32 risks during the scoping discipline and 20 risks during the requirements discipline, 14 risks occurred in both disciplines. Some identified risks are not particular to SPL development, however, they have their impact increased due to the SPL characteristic. All the study results and lessons learned are useful for all project managers and researchers who are considering the introduction of SPL risk management in industry or academia.

[1]  Per Runeson,et al.  Integrating agile software development into stage-gate managed product development , 2006, Empirical Software Engineering.

[2]  Martin Becker,et al.  Establishing a Software Product Line in an Immature Domain , 2002, SPLC.

[3]  Claudio Riva,et al.  Experiences with software product family evolution , 2003, Sixth International Workshop on Principles of Software Evolution, 2003. Proceedings..

[4]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[5]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[6]  Silvio Romero de Lemos Meira,et al.  An Experimental Study on Requirements Engineering for Software Product Lines , 2009, 2009 35th Euromicro Conference on Software Engineering and Advanced Applications.

[7]  Klaus Schmid A comprehensive product line scoping approach and its validation , 2002, ICSE '02.

[8]  Janice Singer,et al.  Studying Software Engineers: Data Collection Techniques for Software Field Studies , 2005, Empirical Software Engineering.

[9]  Silvio Romero de Lemos Meira,et al.  A Regression Testing Approach for Software Product Lines Architectures , 2010, 2010 Fourth Brazilian Symposium on Software Components, Architectures and Reuse.

[10]  Andreas Birk,et al.  Challenges for Requirements Engineering and Management in Software Product Line Development , 2007, REFSQ.

[11]  Barbara Paech,et al.  Working conference on requirements engineering: foundation for software quality (REFSQ'07) , 2007, SOEN.

[12]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[13]  Silvio Romero de Lemos Meira,et al.  The importance of documentation, design and reuse in risk management for SPL , 2010, SIGDOC '10.

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

[15]  Silvio Romero de Lemos Meira,et al.  Extending the RiPLE-DE process with quality attribute variability realization , 2011, QoSA-ISARCS '11.

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

[17]  Silvio Romero de Lemos Meira,et al.  An Agile Scoping Process for Software Product Lines , 2011, SEKE.

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