Java Reference
In-Depth Information
updating client models automatically or upon explicit invocation. Of course, this
implies that both versions of the metamodel are deployed using a corresponding
version change so that each can be loaded into the environment. Alternatively,
just the old .ecore could be deployed with the newer one, as long as the trans-
formation can locate both models.
For example, let's say that our Requirements model was refactored so that a
new abstract
ModelElement
class were introduced as a superclass for
Requirement
and
RequirementGroup
. With that, our
Model
class changed its
main containment reference from
groups : RequirementGroup
to
elements
: ModelElement
. Furthermore, we combined our
RequirementGroup
children : RequirementGroup
and
requirements : Requirement
con-
tainments into a single
children : ModelElement
relationship. Figures 6-1
and 6-2 are the two models for reference, beginning with the before version.
Figure 6-1
Requirements domain model
Search WWH ::
Custom Search