Dynamic Software Product Lines

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 th...

Full description

Saved in:
Bibliographic Details
Published in:Computer (Long Beach, Calif.) Calif.), 2008-04, Vol.41 (4), p.93-95
Main Authors: Hallsteinsen, S., Hinchey, M., Sooyong Park, Schmid, K.
Format: Article
Language:English
Subjects:
Adaptability
Aerodynamics
application engineering
Application software
Applied sciences
Assembly
Computer programs
Computer science
control theory
systems
Computer systems and distributed systems. User interface
Computers
Costs
domain engineering
Dynamical systems
Dynamics
Economies of scale
Exact sciences and technology
Manufacturing automation
Markets
Paints
product line engineering
Production facilities
Recognition
Run time (computers)
Segments
Software
Software engineering
software technologies
Technological innovation
variability management
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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.
ISSN:0018-9162
1558-0814
DOI:10.1109/MC.2008.123