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

• Metamodel Comparison: It identifies the metamodel extensions that must

be implemented in the UML profile.

• Integration Metamodel Transformation: A set of transformation rules that

automatically transform the Integration Metamodel into the UML profile
that implements the identified metamodel extensions.

Step 4. Generation of Model Transformation Rules. This last step provides the
interchange mechanisms to translate models across the different integrated
modeling languages. The interchange is based on a set of transformation
rules that are generated by using the mapping information obtained in the
UML profile generation [ 13] . These transformation rules can be implemented
with model-to-model transformation technologies such as ATL [ 17] or QVT
[ 31] .

3.2 A Generic Process to Link Goal-Oriented Requirement
Modeling and MDD Approaches

In this section, we explain the different steps of the proposed linking process. In
order to facilitate the understanding, we present the process using a brief linking
example that is based on the i ∗ and OO-Method approaches, which correspond to the
GORE and MDD counterparts, respectively. Figure 4 shows the i ∗ diagram related
to this example.
The proposed example represents the reception of work requests (work appli-
cations) from potential employees, which is part of a complete case study of a
photography agency administration system that was developed in the context of
the OO-Method industrial approach (presented in [ 26] ). In order to simplify the
example, only a subset of all the i ∗ and OO-method constructs were used.
Step 1: Definition of the Transformation Guidelines. The first step is to identify
those constructs of the GORE modeling approach that are relevant for the generation
of constructs of the MDD modeling approach. The identification of the relevant con-
structs is performed over the metamodels of the modeling languages involved. These
metamodels must be EMOF compliant [ 30] (according to the integration process
presented in Sect. 3.1). Then, the set of transformation guidelines that are needed

Candidate
Employee

Employer

Legend

Dependency Link

A Work
Request to
be Processed

dependee depender

Work
Opportunity

Actor
A

Actor
B Actor

Boundary

Internal Elements and Relationships

To Present
Work Request

Work
Request

To Process
Work Request

Ta s k Resource

Goal Means End

i ∗ example model

Fig. 4