Managing Variability in Software Product Lines

Software Product Lines are large systems intended for reuse in concrete products. As such these large systems provide reusable architecture and implementation that the individual products have in common. The differences between the product are left open. We refer to these open spots as variability points. In this article we provide a conceptual framework of terminology for the concept of variability and we discuss how variability can be managed in Software Product Lines.

[1]  Peyman Oreizy,et al.  Self-Adaptive Software: An Architecture-based Approach , 1999 .

[2]  Jan Bosch,et al.  Product-line architectures in industry: a case study , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[3]  Jan Bosch,et al.  Evolution in software product lines: two cases , 1999, J. Softw. Maintenance Res. Pract..

[4]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[5]  Jan Bosch,et al.  Characterizing Evolution in Product Line Architectures , 1999, ICSE 1999.

[6]  Brian Foote,et al.  Designing Reusable Classes , 2001 .

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

[8]  Nader Nada,et al.  An empirical study of a software reuse reference model , 2000, Inf. Softw. Technol..

[9]  J. C. Wortmann,et al.  Development and Evolution of Software Architectures for Product Families , 1998, Lecture Notes in Computer Science.

[10]  Don S. Batory,et al.  The design and implementation of hierarchical software systems with reusable components , 1992, TSEM.

[11]  Martin L. Griss,et al.  Implementing Product-Line Features with Component Reuse , 2000, ICSR.

[12]  David C. Rine,et al.  Investments in reusable software. A study of software reuse investment success factors , 1998, J. Syst. Softw..

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

[14]  Clemens A. Szyperski,et al.  Component software - beyond object-oriented programming , 2002 .

[15]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[16]  J. Paul Gibson.  Feature Requirements Models: Understanding Interactions , 1997, FIW.

[17]  Martin L. Griss,et al.  Integrating Feature Modeling with the RSEB Proceedings of Fifth International Conference on Software Reuse, Victoria, B.C., 1998 , 1998 .

[18]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[19]  Jan Bosch,et al.  Evolution in software product lines: Two cases , 1999 .

[20]  Ivar Jacobson,et al.  Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).

[21]  Peter van den Hamer,et al.  An Integral Hierarchy and Diversity Model for Describing Product Family Architecture , 1998, ESPRIT ARES Workshop.