Details
Original language | English |
---|---|
Title of host publication | SPLC '11: Proceedings of the 15th International Software Product Line Conference |
Volume | 2 |
Publication status | Published - Aug 2011 |
Externally published | Yes |
Event | 15th International Software Product Line Conference, SPLC'11 - Munich, Germany Duration: 21 Aug 2011 → 26 Aug 2011 |
Abstract
Deriving a product from a software product line may require various build tasks, such as model transformations, source code generation, preprocessing, compiling, as well as linking and packaging the compiled sources. Usually implemented using simple scripting languages, such as Apache ant or GNU make, build systems tend to become monolithic entities, which are intricate to adapt and maintain. This makes developing the build system for a multi-product-line, which is composed of several sub-product-lines and maybe other configurable components, particularly challenging. Several, previously independent build systems- possibly implemented using different build tools (ant, make, etc.)-need to be integrated. In this paper, we approach this by using models to describe the involved build tasks (including their input and output parameters) as well as their composition. An interpreter evaluates the models and executes the tasks in the composed order with the configured parameters to produce the final product. Our approach enables the interaction of build systems implemented with different tools with only little development effort, whereas the build order and parameter flow is made explicit in the models. We have started to apply our tooling to model the build system of two multi-product-lines, where it reveals sufficient expressiveness and clarifies the build system interaction.
Keywords
- Build system integration, Software product line
ASJC Scopus subject areas
- Computer Science(all)
- Software
- Computer Science(all)
- Human-Computer Interaction
- Computer Science(all)
- Computer Vision and Pattern Recognition
- Computer Science(all)
- Computer Networks and Communications
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
SPLC '11: Proceedings of the 15th International Software Product Line Conference. Vol. 2 2011.
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - An Infrastructure for Composing Build Systems of Software Product Lines
AU - Elsner, Christoph
AU - Lohmann, Daniel
AU - Schröder-Preikschat, Wolfgang
PY - 2011/8
Y1 - 2011/8
N2 - Deriving a product from a software product line may require various build tasks, such as model transformations, source code generation, preprocessing, compiling, as well as linking and packaging the compiled sources. Usually implemented using simple scripting languages, such as Apache ant or GNU make, build systems tend to become monolithic entities, which are intricate to adapt and maintain. This makes developing the build system for a multi-product-line, which is composed of several sub-product-lines and maybe other configurable components, particularly challenging. Several, previously independent build systems- possibly implemented using different build tools (ant, make, etc.)-need to be integrated. In this paper, we approach this by using models to describe the involved build tasks (including their input and output parameters) as well as their composition. An interpreter evaluates the models and executes the tasks in the composed order with the configured parameters to produce the final product. Our approach enables the interaction of build systems implemented with different tools with only little development effort, whereas the build order and parameter flow is made explicit in the models. We have started to apply our tooling to model the build system of two multi-product-lines, where it reveals sufficient expressiveness and clarifies the build system interaction.
AB - Deriving a product from a software product line may require various build tasks, such as model transformations, source code generation, preprocessing, compiling, as well as linking and packaging the compiled sources. Usually implemented using simple scripting languages, such as Apache ant or GNU make, build systems tend to become monolithic entities, which are intricate to adapt and maintain. This makes developing the build system for a multi-product-line, which is composed of several sub-product-lines and maybe other configurable components, particularly challenging. Several, previously independent build systems- possibly implemented using different build tools (ant, make, etc.)-need to be integrated. In this paper, we approach this by using models to describe the involved build tasks (including their input and output parameters) as well as their composition. An interpreter evaluates the models and executes the tasks in the composed order with the configured parameters to produce the final product. Our approach enables the interaction of build systems implemented with different tools with only little development effort, whereas the build order and parameter flow is made explicit in the models. We have started to apply our tooling to model the build system of two multi-product-lines, where it reveals sufficient expressiveness and clarifies the build system interaction.
KW - Build system integration
KW - Software product line
UR - http://www.scopus.com/inward/record.url?scp=80052666622&partnerID=8YFLogxK
U2 - 10.1145/2019136.2019157
DO - 10.1145/2019136.2019157
M3 - Conference contribution
AN - SCOPUS:80052666622
SN - 9781450307895
VL - 2
BT - SPLC '11: Proceedings of the 15th International Software Product Line Conference
T2 - 15th International Software Product Line Conference, SPLC'11
Y2 - 21 August 2011 through 26 August 2011
ER -