HomeHomeHomeArchiteturMiddlewareMDSDBeratungCoachingTrainig
header
homemailbacksearchimpressum

go back go up Conferences :: Using Domain-Specific Languages for Product Line E...

dotted Line
dotted Line
menu not Selected Home
dotted Line
menu not Selected Services
dotted Line
menu not Selected Experience
dotted Line
menu not Selected New DSL Book
dotted Line
menu selected Conferences
   menu not Selected Presentations
   menu not Selected Tutorials
   menu not Selected Keynotes/Invited
   menu not Selected Workshops
   menu not Selected Panels
dotted Line
menu not Selected Publications
dotted Line
menu not Selected Vorlesungen
dotted Line
menu not Selected Site
dotted Line
dotted Line

magic Pixel banner 0

magic Pixel banner 1

magic Pixel banner 2

magic Pixel banner 3

magic Pixel banner 4
magic Pixel

Using Domain-Specific Languages for Product Line Engineering

Domain specific languages, together with code generation or interpreters (a.k.a. model-driven development), are becoming more and more important. Since there is a certain overhead involved in building languages and processors, this approach is especially useful in environments where a spe-cific set of languages and generators can be reused many times. Product lines are such an environment. Consequently, the use of domain specific languages (DSLs) for Software Product Line Engi-neering (SPLE) is becoming more relevant. However, exploiting DSLs in the context of product lines involves more than just defining and using languages. This tutorial explains the differences as well as commonalities between model-driven development (MDD) and SPLE and shows how the two approaches can be combined. In this tutorial we will first recap/introduce feature modeling and model-driven development. We then build a simple textual DSL and a code generator based on Eclipse openArchitectureWare (oAW). Based on this language we’ll discuss the kinds of variability expressible via DSLs versus those expressible via feature modeling, leading to a discussion about ways to combine the two. In the next demo slot we’ll do just that: we’ll annotate a model with feature dependencies. When generating code, the elements whose features are not selected will be removed, and hence no code will be generated. Finally we’ll discuss and demo the integration feature dependencies into code generators to con-figure the kind of code generated from the model.

[tutorial]
25.08.2009
../data/presentations/MDD-PLE_SPLC-PRINT.pdf Download... Abstract... Abstract...
Using Domain-Specific Languages for Product Line Engineering
Conference: SPLC 2009 SPLC 2009