Reusable model transformations

Abstract

Model transformations written for an input metamodel may often apply to other metamodels that share similar concepts. For example, a transformation written to refactor Java models can be applicable to refactoring UML class diagrams as both languages share concepts such as classes, methods, attributes, inheritance. Deriving motivation from this example, we present an approach to make model transformations reusable such that they function correctly across several similar metamodels. Our approach relies on these principal steps: (1) We analyze a transformation to obtain an effective subset of used concepts. We prune the input metamodel of the transformation to obtain an effective input metamodel containing the effective subset. The effective input metamodel represents the true input domain of transformation. (2) We adapt a target input metamodel by weaving it with aspects such as properties derived from the effective input metamodel to ultimately make it a subtype of the effective input metamodel. The subtype property ensures that the transformation can process models conforming to the target input metamodel without any change in the transformation itself. We validate our approach by adapting well-known refactoring transformations (Encapsulate Field, Move Method, and Pull Up Method) written for an in-house domain-specific modelling language (DSML) to three different industry standard metamodels (Java, MOF, and UML).

Towards the flexible reuse of model transformations: A formal approach based on graph transformation

“…Instead of instantiating the template rules, a different way to achieve transformation reuse is to modify the concrete meta-model to make it "compatible" (a subtype) with the concept [18,33]. In this second approach -meta-model adaptation -the elements that appear in the concept but not in the meta-model are added to the meta-model as derived elements that are calculated from queries on meta-model elements.…”

Reverse Engineering of Model Transformations for Reusability

“…The former include reuse mechanisms for single rules, like rule inheritance [11], and for whole transformations, like superimposition [19] and phases [14]. Regarding type-independent approaches, there are fine-grained techniques like parameterized rules [8,10,17], and coarse-grained ones aimed at reusing complete transformations [16]. Among these proposals, only [16] supports the reuse of transformations for arbitrary meta-models, as in our case.…”

“…Regarding type-independent approaches, there are fine-grained techniques like parameterized rules [8,10,17], and coarse-grained ones aimed at reusing complete transformations [16]. Among these proposals, only [16] supports the reuse of transformations for arbitrary meta-models, as in our case. For this purpose, the authors extract the effective meta-model of the transformation as-is, and adapt the meta-model where the transformation is to be reused by making it a subtype of the effective meta-model.…”

Generic Model Transformations: Write Once, Reuse Everywhere

“…For instance, in [15], reuse is achieved by adapting the meta-models to which an existing transformation is to be applied. The aim of adapting the meta-model is to make it a subtype of the expected input meta-model of the transformation [16], so that the transformation can be applied without changing it.…”