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

E1 E3 E7 E8 E9

MDD
Metamodel

Mapping
Information

Integration
Metamodel

Transformation
Guidelines

UML Profile

input

input

input output

output output

output

Step 1
Transformation
Guidelines Definition

Step 2
MDD Requirement
Metamodel Definition

Step 3
Validation Rules
Definition

Step 4
Integration Approach
Application

output input input

output

input

E2 E4 E5 E6

MDD Req .
Metamodel

Requirement
Metamodel

Transformation
Rules

OCL Rules

Fig. 8 General schema of the proposed linking process

metamodel extensions for the GORE metamodel and the needed model interchange
information. Figure 8 shows the resultant linking schema with the different input
and output elements that are related to each step (numbered from E1 to E9).
Figure 8 shows that Step 4 of the process generates the corresponding Integration
Metamodel and UML Profile, as well as, mapping information (among the meta-
models involved) for the automatic interchange of models.
Figure 9 shows how each one of the input and output elements considered in
the linking process are used to link the i ∗ framework and the OO-Method MDD
approach. This figure also shows the generation of traceability information [ 15, 44] ,
which is necessary to maintain the relationships between the software specifica-
tion (described in the MDD model) and the requirement specification (described in
the MDD requirement model). The generation of this traceability information must
be implemented together with the transformation rules for the MDD requirement
model.
Figure 10 shows the Integration Metamodel obtained for the example. This
metamodel is generated from the OO-method requirement metamodel by applying
the systematic approach presented in [ 10, 14] . This systematic approach is based
on taking the OO-Method requirement metamodel (the source metamodel) and per-
forming a set of redefinitions over it to align this source metamodel to the structure
of the i ∗ metamodel (target metamodel). This redefinition allows the automatic
identification of the extensions that are required to introduce the modeling needs of

E6 E3 i* -OOm

Transformation
Guidelines

Validation
OCL Rules

integrates implementationOf

E9 E2 E7 i* -OOmReq

Integration
Metamodel

E8 i* - OOm

mapping
Information

E5 E4

OOm Req. Model -
OOm Class Model
Transformation Rules

E1

i*
Metamodel

i* - OOm
UML Profile

OOm Req .
Metamodel

OOm Class
Metamodel

input input

generates

instanceOf

instanceOf

instanceOf

uses I*

Extended
Model

i*
Model

OOm Req .
Model

OOm Req .
Model

Models
Interchange

Traceability OOm Class

Model

Transformation

Fig. 9 Linking proposal elements applied to i ∗ and OO-method