Book contents
- Frontmatter
- Contents
- Part I Software product line engineering challenges
- Part II Variability analysis and modelling
- Part III Variability implementation and traceability
- 6 Product line implementation with ECaesarJ
- 7 Model-driven engineering support for product line engineering
- 8 Managing information flow in the SPL development processes
- 9 Using design rationale to improve SPL traceability
- Part IV Product-driven vs. solution-driven software product line engineering
- Part V Future trends
- Epilogue
- References
- Index
9 - Using design rationale to improve SPL traceability
from Part III - Variability implementation and traceability
Published online by Cambridge University Press: 07 September 2011
- Frontmatter
- Contents
- Part I Software product line engineering challenges
- Part II Variability analysis and modelling
- Part III Variability implementation and traceability
- 6 Product line implementation with ECaesarJ
- 7 Model-driven engineering support for product line engineering
- 8 Managing information flow in the SPL development processes
- 9 Using design rationale to improve SPL traceability
- Part IV Product-driven vs. solution-driven software product line engineering
- Part V Future trends
- Epilogue
- References
- Index
Summary
Introduction
Traceability practices should help stakeholders with the understanding, capturing, tracking and verification of software artefacts and their relationships. A proper realisation of traceability is a necessary system characteristic, as it supports software management, software evolution, verification and validation. It is fundamental for the definition of the results of many kinds of analysis of software models, such as change impact analysis, variability analysis and separation of concerns analysis.
In software product line engineering (SPLE), traceability is a key practice. It is necessary to support variability management and to keep the goals and the structure of the product line definition consistent, updated and valuable. Traceability information is rarely considered in an isolated way. It is captured, updated and analysed from multiple perspectives, such as domain engineering and application engineering.
- Type
- Chapter
- Information
- Aspect-Oriented, Model-Driven Software Product LinesThe AMPLE Way, pp. 263 - 284Publisher: Cambridge University PressPrint publication year: 2011