Information Technology Reference
In-Depth Information
Thus, based on a binding model, we can indicate that a
Specific transformation rule must be woven with a Base
transformation rule when bindings that satisfy the constraint
denoted by a FineCondition element exist. For instance,
we can indicate that a specific transformation rule must be
woven with a base transformation rule when the feature Air
Conditioning appears bound to a Window element.
5.3.2. Creating executable model transformation
workflows from decision models and constraint models
As presented earlier, we transform our decision models into
oAW workflows, which include the required instructions
to execute model transformations in different stages
(external composition), and modify a baseline scheduling
of a set of transformation rules (internal composition). For
transforming our decision models into oAW workflows taking
into account constraint models and binding models, we
modified the model-to-text transformation we introduced
before in section 4.6.2. This model-to-text transformation
allows us to generate executable oAW from decision
models. The oAW generated script contains a querying
mechanism, which looks for bindings that satisfy particular
constraints. Listing 5.3 presents a part of a generated oAW
workflow. This workflow specifies that the transformation rule
domainWindowsToFacilitiesWindows is intercepted (line
2-3 and line 9) and the transformation rule particular
WindowsToAutomaticWindows is executed (line 4-5)
if bindings that satisfy the constraint created between
the Automatic Windows feature and the Window
metaconcept (line 1) exist. We created the oAW component,
which allows us to query binding models looking for bindings
that satisfy a particular constraint. The line 1 from Listing 5.3
shows a call to our oAW component. The component queries
a binding model, which has been previously loaded in the
execution context of an oAW workflow. The model-to-text
Search WWH ::




Custom Search