Linking Goal-Oriented Requirements and Model-Driven Development - Intentional Perspectives on Information Systems Engineering - page 258

to obtain the corresponding MDD constructs must be defined from the identified
GORE constructs.
For the specification of the involved metamodels, we propose using the Eclipse
UML2 tool [ 6] since it provides automatic generation of EMF metamodels from the
defined UML2 metamodels. EMF is the Eclipse Modeling Framework that is based
on the EMOF specification. Also, the generated EMF metamodels are tagged with
additional information to automatically obtain model editors that have interpreters
for the defined OCL rules and that support UML profile extensions.
In the i ∗ context, there is not a standardized i ∗ metamodel, and, in general terms,
the existent metamodel proposals (such as the one presented in the i ∗ wiki [ 16] or
in the articles [ 3, 23] ) are not EMOF compliant. However, for the linking example
presented here, we can use these proposals as reference for the definition of an
appropriate EMOF-based i ∗ metamodel.
Figure 5 shows the i ∗ metamodel defined for the example. In this metamodel,
the i ∗ constructs considered are: actors (class Actor ); dependency resources (class
DResource ); internal goals and tasks (classes IGoal and ITask , respectively); and
dependency links (class Dependency ). It is important to note that this metamodel is
only a subset of a complete i ∗ metamodel. Some of the differences are that tasks ,
goals , and soft goals can also participate in a dependency link. Therefore, in a com-
plete i ∗ metamodel, these constructs must be represented as specializations of the
class Dependency (the same as DResource ). The resources , goals , and soft goals
must also be represented as internal elements (specializations of Internal Element )
in a complete i ∗ metamodel.
The OO-Method metamodel used for the proposed example (see Fig. 6) is also a
subset of the complete OO-Method metamodel.
Fig. 5 The i ∗ metamodel for the example model