Auflistung nach Autor:in "Gruschko, Boris"
1 - 2 von 2
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragA change metamodel for the evolution of MOF-based metamodels(Modellierung 2010, 2010) Burger, Erik; Gruschko, BorisThe evolution of software systems often produces incompatibilities with existing data and applications. To prevent incompatibilities, changes have to be well-planned, and developers should know the impact of changes on a software system. This consideration also applies to the field of model-driven development, where changes occur with the modification of the underlying metamodels. Models that are instantiated from an earlier metamodel version may not be valid instances of the new version of a metamodel. In contrast to other metamodeling standards like the Eclipse Modeling Framework (EMF), no classification of metamodel changes has been performed yet for the Meta Object Facility (MOF). The contribution of this paper is the evaluation of the impact of metamodel changes on models. For the formalisation of changes to MOF-based metamodels, a Change Metamodel is introduced to describe the transformation of one version of a metamodel to another. The changes are then classifed by their impact on the compatibility to existing model data. The classification is formalised using OCL constraints. The Change Metamodel and the change classifications presented in this paper lay the foundation for the implemention of a mechanism that allows metamodel editors to estimate the impact of metamodel changes semi-automatically.
- KonferenzbeitragChanges Classification in M2 Models(Software Engineering 2007 – Beiträge zu den Workshops – Fachtagung des GI-Fachbereichs Softwaretechnik, 2007) Gruschko, BorisAs Model Driven Software Development gains attention, its utilization become more feasible in large scale software projects. The metamodels (M2 models) are important artifacts of the MDD process. These models capture the modeler’s un- derstanding of the problem domain. However, the process of problem domain understanding is not necessarily completed, as the M2 models is being delivered to its consumers. Therefore, the changes of M2 models are inherent to the modeling process. Therefore, the M1 models can erode, when not backwards-compatible changes are being introduced to M2 models. The problem of M1 model erosion in face of M2 model changes becomes a definitive one, when MDD is applied in large scale development projects. We therefore propose a structured M1 model migration, driven by M2 model changes. In this paper we present the classification of M2 model changes, in regard to their impact on corresponding M1 models. To illustrate our considerations, we use the example of super type associations in context of the Eclipse Modeling Framework.