Tools Support - Model-Driven and Software Product Line Engineering - page 172

does not allow, however, product line architects to create the
structural properties associated with constraints. Therefore,
the structural properties must be written directly on the Check
files.

1
2
3
4
5
6
7
8
9
10
11

context Binding ERROR l o c () +
" There are less than 1 Door element bound " +
" to the feature Lock Door Control”:

(this.metaConcept = ' Door ' &&
this.feature. parentFeature.name = ' Lock Door Control '
&& (( Configuration)this.eContainer ). binding−>
select(b | b.name=this.name && this.metaConcept= ' Door '
&& this.feature. parentFeature.name= ' Lock Door Control ' ).
size >=1);

Listing 6.2. Example of a check file generated
by the constraint models creator

Listing 6.3 presents an example of a Check expression for
a structural property. This is related to a constraint between
the Component , metaconcept, and the feature Periodic . The
structural property defines that only a Component element
that is bound to the feature On Invocation can be bound
to the feature Periodic . As part of our future work, we will
allow product line architects to create the structural properties
associated with constraints directly on the Constraint Models
Creator.

1
2
3
4
5
6
7
8
9
10

context Binding ERROR l o c () +
" The Component " + this.elementName + " must be " +
" also bound to the ∗On Invocation∗ feature " :

(this.metaConcept = ' Component ' &&
this.feature.name = ' Periodic '
&& ((Configuration)this.eContainer ). binding−>
select(b | b.name=this.name && this.feature.name=
' On Invocation ' ).size =1);

Listing 6.3. Example of a check expression for a structural property