Abstract
The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.
Highlights
Non-functional requirements (NFRs) problems are grouped into definition problems, classification problems, and representation problems
[12] advanced another interesting approach known as Concern-Oriented Reuse (CORE), a general-purpose software development that leverages the strength of Model-Driven Engineering (MDE), Component-Based Software Engineering (CBSE), Software Product Line (SPL), feature-oriented and aspectoriented software development, and goal modeling to promote reuse
We focus on variability of the phone data protection and user privacy enforcement mechanisms as requirements that expose functional quality attributes at the variation points
Summary
Non-functional requirements (NFRs) problems are grouped into definition problems, classification problems, and representation problems. As observed in[3], most approaches to quality attribute incorporation in software product line development introduce the variability at the design level (e.g., within sequences diagrams) instead of modeling the variability of the quality attributes earlier on in the development process, such as the requirements analysis level or at the architectural level Our approach addresses this gap by considering and integrating quality attributes at the domain requirements analysis and specification phase. This work, proposes an approach that will support the identification and integration of quality attributes with the functional features at respective variation point levels during the domain requirements analysis phase based on a higher-level abstraction of common features among variants.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering & Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
