Details zur Publikation
@article {HallsteinsenHinchey+08,
author={Svein Hallsteinsen and Mike Hinchey and Soyong Park and Klaus Schmid},
title={Dynamic Software Product Lines},
journal={IEEE Computer},
number={4},
volume={41},
year={2008},
pages={93-95},
doi={10.1109/MC.2008.123},
abstract={The Software Engineering Institute (SEI) defines an SPL as a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission. A fundamental principle of SPLs is variability management, which involves separating the product line into three parts - common components, parts common to some but not all products, and individual products with their own specific requirements - and managing these throughout development. Using SPLs seeks to maximize reusable variation and eliminate wasteful generic development of components used only once. Although traditional SPL engineering recognizes that variation points are bound at different stages of development, and possibly also at runtime, it typically binds variation points before delivery of the software. In contrast, DSPL engineers typically aren't concerned with pre-runtime variation points. However, they recognize that in practice mixed approaches might be viable, where some variation points related to the environment's static properties are bound before runtime and others related to the dynamic properties are bound at runtime.}
}