A variability management process for software product lines
CASCON '05 Proceedings of the 2005 conference of the Centre for Advanced Studies on Collaborative research
Recovering architectural assumptions
Journal of Systems and Software
Generating web applications from process models
ICWE '06 Workshop proceedings of the sixth international conference on Web engineering
Product lines for digital information products
Information Systems
Classifying variability modeling techniques
Information and Software Technology
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
Rationale-based variability management in product line requirements engineering
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Towards automatic derivation of a product performance model from a UML software product line model
WOSP '08 Proceedings of the 7th international workshop on Software and performance
Raising family is a good practice
FOSD '10 Proceedings of the 2nd International Workshop on Feature-Oriented Software Development
Proceedings of the 4th India Software Engineering Conference
Modeling dynamic virtualized resource landscapes
Proceedings of the 8th international ACM SIGSOFT conference on Quality of Software Architectures
Towards business application product lines
MODELS'12 Proceedings of the 15th international conference on Model Driven Engineering Languages and Systems
| Hi-index | 0.00 |
The product line approach provides a systematic approach for software reuse. A challenge with modeling adaptive and evolvable software product lines is how to model variability. This paper describes four different approaches to modeling variability, modeling variability using parameterization, modeling variability using information hiding, modeling variability using inheritance, and modeling variability using variation points. The Variation Point Model (VPM) is used to demonstrate the fourth approach. VPM allows a reuser or application engineer to extend components at pre-specified variation points. For this to be possible, a variation point must be modeled such that the reuser has enough knowledge to build a variant.