|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Software product line engineering is mostly about the systematic management of commonality and variability between product line members. The effectiveness of this approach thus very much depends on how well variability within the family of similar products is implemented and managed. Variability often has widespread impact, crosscutting not only multiple parts of individual artifacts but also multiple artifacts in multiple stages of the product line lifecycle. This demonstration presents an approach that facilitates variability implementation, management, and tracing by integrating aspect-oriented and model-driven software development. We demonstrate means for effectively dealing with variability on model, model transformation, and code generation level. The concepts are illustrated with a case study of a home automation system. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Keywords:
Collaborative Colleagues:
|
|||||||||||||||||||||||||||||||||||||||||||||||||