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

Listing 6.1 presents an example of an oAW workflow
file with parameters to generate Ecore models from UML
2 XMI files. In line 3, we define the location of the UML
2 model to be transformed. In line 4, we specify the target
location of the resulting Ecore model. Line 5 to line 8
describes some additional properties required to perform the
transformation.

1
2
3
4
5
6
7
8

<cartridge
file= " org/openarchitectureware/util/uml2ecore/uml2ecoreWorkflow.oaw "
uml2ModelFile= " ..UML2Models∩domainMetamodel.uml2 "
outputPath= " .. EcoreModels∩domainMetamodel. ecore "
nsUriPrefix= " http://domainModel "
includedPackages= " Data "
addNameAttribute= " false "
resourcePerToplevelPackage= " false " />

Listing 6.1. Example of an oAW workflow to generate
metamodels from UML 2 XMI files

6.4.2.2. The feature models creator

To create feature models, we provide the Feature Models
Creator , which is an Eclipse plug-in. We decided to create
our own Feature Models Creator instead of using commercial
tools such as pure :: variants [PUR 10] or open source tools
without support teams such as fmp [ANT 04]. Our Feature
Models Creator includes a facility for preliminary validation
of feature models. This plug-in validates that the lower bound
of cardinality of features is minor or equal to the upper
bound of cardinality of features, and solitary features have
cardinality between zero and one; that is, the cardinality
is [0..1] or [1..1] . To perform the validation of a feature
model, we modified the Eclipse contextual menu that is
related to files with extension .featuremetamodel , which is the
extension that the Feature Models Creator associates with
feature models.Thus,we provide the option to Validate Feature
Models Structure , and we are able to present messages to
inform the user if any inconsistency is found in a feature
model.