This is more likely an
option if the target environment and domain framework are frozen too. It is more
typical, however, that the project wants to upgrade to the newer language.Your task as
the language de?¬?ner is then to analyze in detail the possible side effects: how other
data is modi?¬?ed too. It may be that removal of a concept has consequences and may
remove more model elements than intended. For example, removing an object type
may cause removal of some relationships too.
When after changing a metamodel, it is necessary to test the changes with real
model data. After releasing the new version of the language, it is good practice to
notify modelers of where the change has happened. This allows them to ?¬?nd the
models that may need to be updated. Usually, the update can??™t be fully automated as
the change needed in the model depends on the context, which the model creators
know. Depending on the tool, the noti?¬?cation can be made available using model
browsers or running a generator that reports on all the models where the change could
be made. Depending on the change, it can also be the case that no further noti?¬?cation is
needed: when the developers change the models, they will be updated gradually to the
new metamodel.
While considering the possible changes you can also identify which changes need
the most time.
Pages:
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488