A Systems Approach to Product Line Requirements Reuse

Product line engineering has become the main method for achieving systematic software reuse. Embracing requirements in a product line's asset base enhances the effectiveness of reuse as engineers can work on the abstractions closer to the domain's initial concepts. Conventional proactive approaches to product line engineering cause excessive overhead when codifying the assets. In this paper, we propose a systems-oriented approach to extracting functional requirements profiles. The validated extraction constructs are amenable to semantic case analysis and orthogonal variability modeling, so as to uncover the variation structure and constraints. To evaluate our approach, we present an experiment to quantify the extraction overhead and effectiveness and a case study to assess our approach's usefulness. The results show that our automatic support offers an order-of-magnitude saving over the manual extraction effort without significantly compromising quality and that our approach receives a positive adoption rate by systems engineers.

[1]  Gan Wang,et al.  Reuse in Systems Engineering , 2010, IEEE Systems Journal.

[2]  Nan Niu,et al.  Concept analysis for product line requirements , 2009, AOSD '09.

[3]  A. Stone,et al.  An Ontological Approach to Quantifying the Functional Flexibility of Embedded Systems , 2011, IEEE Systems Journal.

[4]  Nan Niu,et al.  Extracting and Modeling Product Line Functional Requirements , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[5]  Gail E. Kaiser,et al.  An Information Retrieval Approach For Automatically Constructing Software Libraries , 1991, IEEE Trans. Software Eng..

[6]  Isabel John.  Integrating Legacy Documentation Assets into a Product Line , 2001, PFE.

[7]  C. Krueger,et al.  Eliminating the adoption barrier , 2002, IEEE Software.

[8]  Nan Niu,et al.  A case study of exploiting enterprise resource planning requirements , 2011, Enterp. Inf. Syst..

[9]  Frank Leymann,et al.  Horizontal and vertical combination of multi-tenancy patterns in service-oriented applications , 2011, Enterp. Inf. Syst..

[10]  Marten van Sinderen,et al.  Extending enterprise architecture modelling with business goals and requirements , 2011, Enterp. Inf. Syst..

[11]  Christian Steger,et al.  Searching Extended IP-XACT Components for SoC Design Based on Requirements Similarity , 2011, IEEE Systems Journal.

[12]  Michael A. Corsello.  System-of-Systems Architectural Considerations for Complex Environments and Evolving Requirements , 2008, IEEE Systems Journal.

[13]  Ravi Shankar,et al.  Mechanisms for Requirements Driven Component Selection and Design Automation , 2010, IEEE Systems Journal.

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

[15]  François Guillaume,et al.  Processes to Integrate Design With Downstream Applications Through Product Shapes Adaptation , 2009, IEEE Systems Journal.

[16]  Jihong Liu,et al.  An efficient and flexible web services-based multidisciplinary design optimisation framework for complex engineering systems , 2012, Enterp. Inf. Syst..

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

[18]  John D. McGregor,et al.  Calculating ROI for software product lines , 2004, IEEE Software.

[19]  Nan Niu,et al.  So, You Think You Know Others' Goals? A Repertory Grid Study , 2007, IEEE Software.

[20]  Daniel DeLaurentis,et al.  Exploring the Dimensions of Systems of Innovation Analysis: A System of Systems Framework , 2011, IEEE Systems Journal.

[21]  Klaus Krippendorff,et al.  Content Analysis: An Introduction to Its Methodology , 1980 .

[22]  Dingwei Wang,et al.  Resilience and Friability of Transportation Networks: Evaluation, Analysis and Optimization , 2011, IEEE Systems Journal.

[23]  Azad M. Madni,et al.  Relational Attribute Integrated Matching Analysis (RAIMA): A Framework for the Design of Self-Adaptive Egocentric Social Networks , 2011, IEEE Systems Journal.

[24]  David M. Weiss,et al.  Software Product Line Engineering , 2005, SEKE.

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

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

[27]  E. Rogers,et al.  Diffusion of innovations , 1964, Encyclopedia of Sport Management.

[28]  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.

[29]  Dick A. C. Quartel,et al.  Application and project portfolio valuation using enterprise architecture and business requirements modelling , 2012, Enterp. Inf. Syst..

[30]  Christine Nadel,et al.  Case Study Research Design And Methods , 2016 .

[31]  Nan Niu,et al.  An experimental investigation of reusable requirements retrieval , 2010, 2010 IEEE International Conference on Information Reuse & Integration.

[32]  Klaus Pohl,et al.  Communicating the variability of a software-product family to customers , 2004, Informatik Forschung und Entwicklung.

[33]  Luisa Mich,et al.  Market research for requirements analysis using linguistic tools , 2004, Requirements Engineering.

[34]  J. Toomasian.  The Case for the Case , 2016, Perfusion.

[35]  Nan Niu,et al.  Analysis of Early Aspects in Requirements Goal Models: A Concept-Driven Approach , 2007, LNCS Trans. Aspect Oriented Softw. Dev..

[36]  J. Ivey.  Focus groups. , 2011, Pediatric nursing.

[37]  Michael McGill,et al.  Introduction to Modern Information Retrieval , 1983 .

[38]  Yijun Yu,et al.  On Goal-based Variability Acquisition and Analysis , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).