Information Technology Reference
In-Depth Information
need to elaborate a set of trace types, which define the semantic of the relation-
ships between elements. In this section, we will introduce the trace metamodels
proposed in the MDD field along with our proposed metamodel for DW.
3.1 Model Driven Architecture Metamodels for Traceability
Our traceability approach is based on the trace framework proposed by the
OMG, which is included in the MDA framework [19].
Fig. 2.
Metamodel for traceability in MDA
The metamodel, presented in figure 2, is composed by a
transformation record
which represents the transformation that generated the traces. The transforma-
tion record contains the set of traces produced and can have associated metadata
as, for example, the parameters passed to the transformation when it was exe-
cuted. For each trace recorded, there is a set of model elements which are linked
by the previously-mentioned trace, varying from 0 to N elements. As in the pre-
vious case, the trace can have associated metadata as, for example, which was
the rule of the transformation created each trace.
According to this proposal there is a core metamodel for the ATLAS Model
Weaver (AMW) [6], used for linking elements from models. This core metamodel
constitutes the base for the traceability metamodel which we extend.
3.2 Proposed Metamodel
Our proposed metamodel for traceability extends AMW metamodel for trace-
ability, including the necessary semantic types for traceability in DW. The result
can be seen in figure 3.
In this metamodel, a
TraceModel
hasasetofmodels(
wovenModels
) linked
by the trace model. Each of these woven models has the list of references (
Ele-
mentRef
) which identify the elements linked by the traces. The trace model has
also a set of
TraceLinks
, which define the relationships between the elements in
the woven models. Each trace link has a set of
sourceElements
,whichwerethe
source of the automatic derivation, and a set of
targetElements
which were the
