Further Reading - Model-Driven and Software Product Line Engineering - page 230

model-to-text transformations create source code and re-use
pieces of code to build final products.
For the implementation of this approach, the authors
use the oAW framework, including its AOP mechanism (see
section 3.6.4). Thus, decision models are created as oAW
workflows, textual descriptors, to support the product
derivation process. In these descriptors, the authors indicate
the model transformations that must be executed and the
required execution ordering according to selected features.
For modifying the execution ordering coping with feature
configurations, the authors have created a new oAW
component. This component allows for querying a feature
configuration at model transformation execution time, and
weaving an oAW aspect if a particular feature appears in the
configuration (selected or unselected).
1
2 <feature isSelected= " featureExample " >
3 <transformationAspect adviceTarget= " baseModelTransformation " >
4 <extensionAdvice value= " transformationAdvice " />
5 </transformationAspect>
6 </feature>
7
8 <transform id= " baseModelTransformation " >
9 <invoke value= " transformationRuleBase(domainModel) " />
10 <outputSlot value= " architectureModel " />
11 </transform>
Listing 8.2. Example of a workflow using the Voelter
and Groher's component
Listing 8.2 presents an example of an oAW workflow
by using the created component. The baseModel
Transformation from line 6 transforms a domain model
into an architectural model. For this, the first rule to be
executed is transformationRuleBase(domainModel)
(line 9). The normal call graph of this rule is modified if the
featureExample is selected. This is specified in line 2. If
the feature appears selected in a feature configuration, the
transformationAdvice is executed,thus modifying the base