Managing requirements specifications for product lines - An approach and industry case study

Software product line development has emerged as a leading approach for software reuse. This paper describes an approach to manage natural-language requirements specifications in a software product line context. Variability in such product line specifications is modeled and managed using a feature model. The proposed approach has been introduced in the Swedish defense industry. We present a multiple-case study covering two different product lines with in total eight product instances. These were compared to experiences from previous projects in the organization employing clone-and-own reuse. We conclude that the proposed product line approach performs better than clone-and-own reuse of requirements specifications in this particular industrial context.

[1]  KitchenhamBarbara,et al.  Case Studies for Method and Tool Evaluation , 1995 .

[2]  Stuart R. Faulk.  Product-line requirements specification (PRS): an approach and case study , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[3]  Jürgen Börstler,et al.  The PLUSS toolkit?: extending telelogic DOORS and IBM-rational rose to support product line use case modeling , 2005, ASE '05.

[4]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

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

[6]  Hermann Kaindl,et al.  Representing Requirements on Generic Software in an Application Family Model , 2000, ICSR.

[7]  Frank Houdek,et al.  Towards systematic recycling of systems requirements , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[8]  Hermann Kaindl,et al.  Reusing single system requirements from application family requirements , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[9]  Andreas Hein,et al.  Modeling and Using Product Line Variability in Automotive Systems , 2002, IEEE Softw..

[10]  Jürgen Börstler,et al.  Software product line modeling made practical , 2006, CACM.

[11]  Patrick Donohoe,et al.  Product Line Analysis: A Practical Introduction , 2001 .

[12]  Klaus Pohl,et al.  Modelling requirements variability across product lines , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

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

[14]  Frank van der Linden,et al.  Software Product Families in Europe: The Esaps & Café Projects , 2002, IEEE Softw..

[15]  Klaus Schmid,et al.  Requirements management for product lines: extending professional tools , 2006 .

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

[17]  Kim Lauenroth,et al.  Why is it not Sufficient to Model Requirements Variability with Feature Models? 1 , 2004 .

[18]  John A. McDermid,et al.  Ten steps towards systematic requirements reuse , 2008, Requirements Engineering.

[19]  Stan Jarzabek,et al.  Modelling Variant User Requirements in Domain Engineering for Reuse , 1998, EJC.

[20]  Jürgen Börstler,et al.  Use Cases for Systems Engineering - An Approach and Empirical Evaluation , 2008, Syst. Eng..

[21]  Jürgen Börstler,et al.  Use Cases for Systems Engineering—An Approach and Empirical Evaluation , 2008 .

[22]  Jacob L. Cybulski,et al.  Requirements Classification and Reuse: Crossing Domain Boundaries , 2000, ICSR.

[23]  J. G. Adair,et al.  The Hawthorne effect: A reconsideration of the methodological artifact. , 1984 .

[24]  A. Kornhauser.  The Human Problems of an Industrial Civilization. , 1934 .

[25]  W. Lam,et al.  A case-;study of requirements reuse through product families , 1998, Ann. Softw. Eng..

[26]  Frank van der Linden,et al.  Software product lines in action , 2007 .

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

[28]  Charles W. Krueger,et al.  Incremental return on incremental investment: Engenio's transition to software product line practice , 2006, OOPSLA '06.

[29]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[30]  Krzysztof Czarnecki,et al.  Generative programming - methods, tools and applications , 2000 .

[31]  Jürgen Börstler,et al.  An Empirical Evaluation of the PLUSS Toolkit , 2006 .

[32]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[33]  Barbara Paech,et al.  Systematic requirements recycling through abstraction and traceability , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[34]  Matthew B. Miles,et al.  Qualitative Data Analysis: An Expanded Sourcebook , 1994 .

[35]  David M. Weiss,et al.  Software Product-Line Engineering: A Family-Based Software Development Process , 1999 .

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

[37]  Jürgen Börstler,et al.  The PLUSS Approach - Domain Modeling with Features, Use Cases and Use Case Realizations , 2005, SPLC.

[38]  Klaus Schmid,et al.  Requirements management for product lines: extending professional tools , 2006, 10th International Software Product Line Conference (SPLC'06).

[39]  B. Kitchenham,et al.  Case Studies for Method and Tool Evaluation , 1995, IEEE Softw..

[40]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction, Second Edition , 2000 .

[41]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[42]  Pierre-Yves Schobbens,et al.  Feature Diagrams: A Survey and a Formal Semantics , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).