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
6 - Product line implementation with ECaesarJ
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
The implementation of a product line consists of a set of reusable components, called core assets, which are composed and configured in different ways to build different concrete products. The goal of a product line to support multiple products introduces additional complexity both to its assets and to the development process. The assets are more complicated because they must deal with variations of the concrete products. The development process is more complicated because it must deal not only with evolution of the common assets, but also with independent evolution of products and instantiation of new products.
In order to reduce the complexity of the implementation of a product line and to facilitate independent evolution, it is desirable to modularise the core features of a product line and the specific features of individual products. Considering features as units of variation in a product line, our goal is to support feature-oriented decomposition of software, in which each feature is implemented in a separate module.
- Type
- Chapter
- Information
- Aspect-Oriented, Model-Driven Software Product LinesThe AMPLE Way, pp. 161 - 196Publisher: Cambridge University PressPrint publication year: 2011