Model-Driven Engineering - Model-Driven and Software Product Line Engineering - page 94

<component class= " oaw.xtend.XtendComponent " >

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

<metaModel class= " oaw.type.emf.EmfMetaModel " >
<metaModelFile value= " classMetamodel. ecore " />
</metamodel>

<metaModel class= " oaw.type.emf.EmfMetaModel " >
<metaModelFile value= " erMetamodel. ecore " />
</metaModel>

<invoke value= " my:: path :: class2ER(sourceModel) " />
<outputSlot value= " transformedErModel " />
<value= " my:: Advices ::myAdvice " />

</component>

Listing 3.13. Example of a workflow configuration including advices

3.7. Benefits and challenges for SPLE

As seen in Chapter 2, SPLE is a paradigm that focuses
on artifact re-use and variability management. It introduces
a complex software process with potentially numerous and
heterogeneous artifacts. It also requires some specific tasks
like product configuration and should put more emphasis
on traceability management. MDE appears as a promising
technique for SPLE since it provides uniformity and
abstraction for software artifacts and processes. The ability
to build complex transformations is promising to automate
domain and application engineering. However, there are some
challenges.

How can domain-specific models help to separate concerns
or viewpoints involved in product line development? How do
we address domain evolution changes? How can MDE support
the process of building product line members from separated
models and variability models? For instance, how do we build
complete Web applications from independent data models,
navigation models, or presentation models? How can models