Abstract
Purchase PDF (878 K)
E-mail Article
Add to my Quick Links
Cited By in Scopus (0)
Purchase PDF (759 K)
doi:10.1016/j.datak.2006.06.009 
Copyright © 2006 Elsevier B.V. All rights reserved.
Managing requirements conflicts in software product lines: A goal and scenario based approach
Received 20 June 2006;
References and further reading may be available for this article. To view references and further reading you must purchase this article.
Abstract
The product line approach is recognized as a successful approach to reuse in software development. However, in many cases, it has resulted in interactions between requirements and/or features. Interaction detection, especially conflict detection between requirements has become more challenging. Thus, detecting conflicts between requirements is essential for successful product line development. Formal methods have been proposed to address this problem, however, they are hard to understand by non-experts and are limited to restricted domains. In addition, there is no overall process that covers all the steps for managing conflicts. We propose an approach for systematically identifying and managing requirements conflicts, which is based on requirements partition in natural language and supported by a tool. To demonstrate its feasibility, the proposed approach has been applied to the home integration system (HIS) domain and the results are discussed.
Keywords: Requirements conflicts; Software product line; Goal and scenario authoring; Requirements partitioning; Syntactic and semantic requirements conflict detection
Article Outline
- 1. Introduction
- 2. Related research
- 3. Definitions
- 4. Managing conflicts based on requirements partition
- 4.1. Requirements authoring phase
- 4.2. Requirements partitioning phase
- 4.3. Requirements conflicts detection phase
- 4.3.1. Syntactic conflict detection
- 4.3.2. Semantic conflict detection
- 4.4. Requirements conflicts management phase
- 5. Case study
- 5.1. Problem domain
- 5.2. RECOMA architecture
- 5.2.1. Presentation layer
- 5.2.2. Application layer
- 5.2.3. Data layer
- 5.3. Application to HIS
- 5.3.1. Requirements authoring
- 5.3.2. Requirements partition
- 5.3.3. Requirements conflicts detection
- 5.3.4. Requirements conflicts management
- 5.4. Results of examples
- 6. Conclusion
- Acknowledgements
- References
- Vitae
