IEEE Transactions on Software Engineering
Aspectual Support for Specifying Requirements in Software Product Lines
EARLYASPECTS '07 Proceedings of the Early Aspects at ICSE: Workshops in Aspect-Oriented Requirements Engineering and Architecture Design
Towards automated consistency checks of product line requirements specifications
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Rigorous engineering of product-line requirements: A case study in failure management
Information and Software Technology
Visualizing Product Line Domain Variability by Aspect-Oriented Modeling
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
Concept analysis for product line requirements
Proceedings of the 8th ACM international conference on Aspect-oriented software development
Managing requirements specifications for product lines - An approach and industry case study
Journal of Systems and Software
Information and Software Technology
Towards a method for rigorous development of generic requirements patterns
Rigorous Development of Complex Fault-Tolerant Systems
Information and Software Technology
| Hi-index | 0.00 |
Abstract: Software product-line engineering can provide significant gains in quality and productivity through systematic reuse of software's conceptual structures. For embedded safety- or mission-critical systems, much of the development effort goes into understanding, specifying, and validating the requirements. If developers can reuse rather than re-do requirements for families of similar systems, we can improve productivity while significantly reducing the opportunity for requirements errors. This paper describes a systematic approach to developing a Product-line Requirements Specification (PRS) for such systems. The PRS explicitly represents the family's common requirements as well as the allowed variations that distinguish family members. When completed, the PRS definition also supports generation of well-formed Software Requirements Specifications (SRS) for members of the product line. We describe a process for developing a PRS starting from an analysis of a program family's commonalities and variabilities. The approach is illustrated with examples from a case study of a real family of systems, the Rockwell Collins Commercial Flight Control System product-line.