Towards a Computer-Aided Problem-Oriented Variability Requirements Engineering Method

In theory, software product lines are planned in advance, using established engineering methods. However, there are cases where commonalities and variabilities between several systems are only discovered after they have been developed individually as single systems. In retrospect, this leads to the hindsight that these systems should have been developed as a software product line from the beginning to reduce costs and effort. To cope with the challenge of detecting variability early on, we propose the PREVISE method, covering domain and application engineering. Domain engineering is concerned with exploring the variability caused by entities in the environment of the software and the variability in functional and quality requirements. In application engineering, the configuration for a concrete product is selected, and subsequently, a requirement model for a concrete product is derived.

[1]  Maritta Heisel,et al.  A UML Profile for Requirements Analysis of Dependable Software , 2010, SAFECOMP.

[2]  Rami Bahsoon,et al.  Relating System Quality and Software Architecture , 2014, Relating System Quality and Software Architecture.

[3]  Bashar Nuseibeh,et al.  On the structure of problem variability : From feature diagrams to problem frames Conference or Workshop Item , 2018 .

[4]  Kristian Beckers,et al.  A Problem-Based Approach for Computer-Aided Privacy Threat Identification , 2012, APF.

[5]  Yijun Yu,et al.  Towards a Unified Framework for Contextual Variability in Requirements , 2009, 2009 Third International Workshop on Software Product Management.

[6]  Stephan Faßbender,et al.  Optimizing Functional and Quality Requirements According to Stakeholders' Goals , 2014, Relating System Quality and Software Architecture.

[7]  Maritta Heisel,et al.  A Method to Derive Software Architectures from Quality Requirements , 2011, 2011 18th Asia-Pacific Software Engineering Conference.

[8]  Maritta Heisel,et al.  Towards Systematic Integration of Quality Requirements into Software Architecture , 2011, ECSA.

[9]  Kyo Chul Kang,et al.  Problem Frames-Based Approach to Achieving Quality Attributes in Software Product Line Engineering , 2011, 2011 15th International Software Product Line Conference.

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

[11]  David Clark,et al.  Safety and Security Analysis of Object-Oriented Models , 2002, SAFECOMP.

[12]  Maritta Heisel,et al.  Deriving Quality-based Architecture Alternatives with Patterns , 2012, Software Engineering.

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

[14]  Richard Foley,et al.  An extension of problem frame notation for software product lines , 2005, 12th Asia-Pacific Software Engineering Conference (APSEC'05).

[15]  Stephan Faßbender,et al.  Problem-Based Requirements Interaction Analysis , 2014, REFSQ.

[16]  Mary Shaw,et al.  Software architecture: the next step for object technology (panel) , 1993, OOPSLA '93.

[17]  Helen M. Edwards,et al.  Problem frames: analyzing and structuring software development problems , 2002, Softw. Test. Verification Reliab..

[18]  Bashar Nuseibeh,et al.  Using Problem Descriptions to Represent Variabilities For Context-Aware Applications , 2007, VaMoS.