Information Technology Reference
In-Depth Information
feature configurations, but also bindings from binding models.
Thus, for example, if any
Window
element is bound to
the feature
Automatic Windows
in a binding model, the
base sequence to transform domain models into facilities
models must be modified. This modification implies replacing
the rule
domainWindowsToFacilitiesWindows
by the rule
particularWindowsToAutomaticWindows
. This rule must
transform only the
Domain metamodel::Window
elements,
which are bound to the
Automatic Windows
feature, into
FacilitiesMetamodel:Automatic
window elements. For
instance,fromthebindingmodelpresentedinFigure5.1,given
that the
mainRoomW2
is the only window bound to the feature
Automatic Windows
, this is the only window that must be
transformed into an automatic window.
Condition
Join point Advice
Exists at least one binding
B
1
=[E
1
,F
1
]
that satisfies the constraint
C
1
=[M
1
,F
1
,A,D]
Rule A
Rule A'(
E
1
)
Feature Two Unselected and
exists at least one binding
B
2
=[E
2
,F
2
]
that satisfies the constraint
C
2
=[M
2
,F
2
,A,D]
Rule B
Rule B'(
E
2
)
Table 5.1.
Examples of fine-grained conditions on feature configurations
which imply to adapt a baseline (transformation rules') scheduling
Table 5.1 presents examples of conditions on binding models
that we can capture in our extended decision models. These
conditions imply the modification of a baseline scheduling.
In the first column, we present examples of conditions; in
the second column, we present the name of the base rule
in the baseline scheduling to be intercepted (join point); in
the third column, we present the name of the specific rule
(advice) to be executed if the condition appears in a binding
model. We express conditions in terms of bindings that satisfy
constraints. Thus, row one in Table 5.1 expresses that if at
least one binding
B
1
=[E
1
,F
1
]
that satisfies the constraint
C
1
=[M
1
,F
1
,A,D]
in a binding model exists,
Rule A
must be
Search WWH ::
Custom Search