Requirements Identification and Representation in Software Product Line

Software Product Line (SPL) core assets development is an effective approach in software reuse in which core assets can be shared among the members of the product line with an explicit treatment of variability. Considering reuse early in development phase can promise the increase in reuse and understanding reuse at a later development phase. This paper concentrates on identifying and representing variability at requirement level. The proposed approach differs slightly from other approaches where identification of the variant requirements is done with commonality and variability analysis and using two important requirements model, feature and use case model. Relation between both requirements model is through matrix table. This paper illustrates the application of this approach using the library systems product line example.

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

[2]  Martin L. Griss,et al.  Integrating feature modeling with the RSEB , 1998, Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203).

[3]  Keunhyuk Yeom,et al.  An approach to developing domain requirements as a core asset based on commonality and variability analysis in a product line , 2005, IEEE Transactions on Software Engineering.

[4]  Sholom Cohen,et al.  Object-oriented technology and domain analysis , 1998, Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203).

[5]  Hermann Kaindl,et al.  Using parameters and discriminants for product line requirements , 2008, Syst. Eng..

[6]  Mark A. Clements,et al.  A Computationally Compact Divergence Measure for Speech Processing , 1991, IEEE Trans. Pattern Anal. Mach. Intell..

[7]  John D. McGregor,et al.  Initiating software product lines , 2002, IEEE Software.

[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]  Kim Lauenroth,et al.  Why is it not Sufficient to Model Requirements Variability with Feature Models? 1 , 2004 .

[10]  Soo Dong Kim,et al.  A framework for evaluating reusability of core asset in product line engineering , 2007, Inf. Softw. Technol..

[11]  Peter Kilpatrick,et al.  Weaving behavior into feature models for embedded system families , 2006 .

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

[13]  Jürgen Börstler,et al.  Managing requirements specifications for product lines - An approach and industry case study , 2009, J. Syst. Softw..

[14]  Sooyong Park,et al.  A method and tool support for variant requirements analysis: goal and scenario based approach , 2004, 11th Asia-Pacific Software Engineering Conference.

[15]  Hassan Gomaa.  Designing Software Product Lines with UML 2.0: From Use Cases to Pattern-Based Software Architectures , 2006, ICSR.

[16]  Soo Dong Kim,et al.  A systematic method to instantiate core assets in product line engineering , 2004, 11th Asia-Pacific Software Engineering Conference.

[17]  Jürgen Börstler,et al.  Marrying Features and Use Cases for Product Line Requirements Modeling of Embedded Systems , 2004 .

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

[19]  Ricardo J. Machado,et al.  Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines , 2007 .

[20]  Jaejoon Lee,et al.  Concepts and Guidelines of Feature Modeling for Product Line Software Engineering , 2002, ICSR.

[21]  Iris Groher,et al.  Transitioning to a software product family approach - challenges and best practices , 2006, 10th International Software Product Line Conference (SPLC'06).

[22]  Akkihebbal L. Ananda,et al.  Handling Variant Requirements in Software Architectures for Product Families , 1998, ESPRIT ARES Workshop.