Information Technology Reference
In-Depth Information
Serialization groups the three variations for exporting
data, PlainText , Excel , and standard Java serialization.
These variants represent a coarse-grained variation, which
means that only by selecting one of the features in a
configuration, the generation of a product follows a general
pattern. In this case, for instance, if a product designer selects
the feature PlainText , a product exporting data to plain text
will be created.
The GUI feature, which is a group, groups the three
variations for creating the information view, Grid , Single ,
and Tree .This is also a coarse-grained variation. For instance,
if a product designer selects the feature Grid , a product with
a grid as information view will be created.
7.4.3. The constraint model
Playing the role of product line architects, we create
constraint models to restrict the bindings among model
elements and features; for example, to express that only
problem space models can be bound to our feature model,
or that maximum two Characteristic elements can be
bound to the feature FilteringData . We can also say that
constraint models restrict the fine-grained variations allowed
between product line members. Our constraints serve to
avoid inconsistencies during the configuration and derivation
processes.
Figure 7.8 presents our constraint model for this
example.Wedefineaconstraintbetweenthe Characteristic
metaconcept and the FilteringData feature,
constraint1 =[ Characteristic , FilteringData , [0..*],
true]. The constraint describes that during the configuration
of a product, product designers can bind undetermined
Characteristic elements; for example, the code , with the
feature FilteringData (see Figure 7.9). Then, each bound
element could be used as a filter in the final product.
Search WWH ::




Custom Search