Abstract
Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects” to increase modularity, reusability, maintainability and ease of evolution. In this paper, we apply an as-pect-oriented use case modeling approach to product line system modeling. A use case specification captures stake-holders concerns as interactions between a system and its actors. We adapt our previous work with the introduction of a “variability” relationship for the expression of variabilities. This relationship is used to model variable and common behaviours across a family of products as use cases. A variability composition mechanism enables building of executa-ble behaviour models for each member of a product line family by integrating common elements with the applicable variable elements.
Highlights
The importance of a Software Product Line (SPL) emerged from the field of software reuse when developers realized that reusing development artefacts such as requirements, designs, and components across different members of a product family significantly reduces cost, effort and time
Effectiveness of a software product line does not solely depend on reuse capability and on how commonalities and variabilities of a product line are managed and modeled from the requirements phase to the implementation phase
We presented an approach for use case based modeling of software product line systems
Summary
The importance of a Software Product Line (SPL) emerged from the field of software reuse when developers realized that reusing development artefacts such as requirements, designs, and components across different members of a product family significantly reduces cost, effort and time. Gomma [4], introduced UML stereotypes “kernel”, “alternatives” and “optional” to distinguish common and variable use case specifications in software product lines. We introduced an “aspect” relation for crosscutting requirements and derived a composition mechanism for the generation of a global behaviour. We apply this aspect-oriented use case modeling approach to product line systems specification. A number of recent works have demonstrated that applying Aspect-Oriented Software Development (AOSD) to SPL provides an improved mechanism to encapsulate and model variabilities and commonalities throughout the entire software lifecycle [9−11]. An aspect composition mechanism enables building of executable behaviour models for each member of a product line family by integrating common elements with the applicable variable elements.
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 callDisclaimer: 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.
