Abstract
A feature model can represent commonalities and variabilities in software product lines, but it does not describe how these features are achieved through system functionality and how these functionalities work together to achieve the expected system behavior. Moreover, feature models lack foundations to reason about the relationships among different requirements. Thus, it makes it difficult to justify why a specific feature configuration is required. In this paper, we propose to use the aspectual i approach to capture common and variable features in software product lines requirements. In doing so, we aim at addressing the issues pointed out previously and facilitating the selection among configuration alternatives to fulfill customer requirements.
Original language | English |
---|---|
Title of host publication | SEKE |
Pages | 472-477 |
Number of pages | 6 |
Publication status | Published - 1 Jan 2008 |
Event | SEKE - Duration: 1 Jan 2008 → … |
Conference
Conference | SEKE |
---|---|
Period | 1/01/08 → … |
Keywords
- System behaviors
- System functionality
- Customer requirements
- Feature configuration
- Feature modeling
- Goal-oriented approach
- Modeling features
- Software Product Line