Information Technology Reference
In-Depth Information
Fig. 6
The OO-method metamodel for the linking example
The presented OO-Method metamodel only includes the essential metaclasses
for the definition of classes, attributes, services, associations, and a special
relationship that is called
agent link
. This last construct is related to the specifi-
cation of permissions that a class (of the modeled system) has to execute services
of another class. Another particular modeling aspect of the OO-Method class model
is the possibility of indicating the services that are capable of
create
or
destroy
instances of the class that owns them. This information is indicated by means of the
property
kind
, which is defined in the metaclass
Service
.
Once the EMOF metamodels are properly specified, the relevant
i
∗
construct
must be identified, and the guidelines to transform these constructs into the cor-
responding OO-Method class model constructs must also be defined. Table
1
shows the transformation guidelines involved in the example (the complete list of
Table
1
also shows the additional information that is required by the transfor-
mation guidelines, which may not be present in the
i
∗
metamodel. For instance,
an
i
∗
resource is transformed into a class or an attribute depending on whether the
resource corresponds to a
physical
or an
informational
entity.
Step 2: Definition of MDD Requirement Metamodel.
The second step of the
linking process corresponds to properly specifying the modeling information that
is required by the transformation guidelines in a format that can be processed by
model-to-model transformation technologies [
5]
. To do this, we define a new EMOF
metamodel with the information of the identified
i
∗
elements and the additional
information that is required. As a result, a specific requirement metamodel for the
involved MDD approach is obtained. Figure
7
shows the OO-Method requirement
Search WWH ::
Custom Search