Dynamic Software Product Lines
By Svein O. Hallsteinsen, M. Hinchey, Sooyong Park, Klaus Schmid. Computer, 2008
440 citations recorded by the source corpus.
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.
Subfields: Artificial Intelligence, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/145a903de884f39c80a4dce078869d4e98c80110
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
In Information Systems
In Software
Citations in the corpus
- A survey on engineering approaches for self-adaptive systems (2015, methodology): “Hallsteinsen, Hinchey, and Schmid propose a dynamic SPL approach [53], which is used in [21] in combination with models@run.”