Supporting large scale model transformation reuse

Abstract

The growth of applications developed with the support of model transformations makes reuse a required practice, specially when applied to transformation assets (e.g. transformation chains, algorithms, and configuration files). In order to promote reuse one must consider the different implementations, communalities, and variants among these assets. In this domain, a couple techniques have been used as solutions to adapt reusable assets for specific needs. However, so far, no work has discussed their combined use in real software projects. In this paper, we present a new tool named WCT, which can be used to adapt transformation assets. Moreover, through lessons learned in industry, we address some reuse techniques devoted to adapt these assets.

Extending JUnit 4 with Java annotations and reflection to test variant model transformation assets

“…In order to exemplify transformations based on real scenario, reported in an industrial effort in tailoring transformation assets in [5], next section exemplifies some points that varied in the generation of source-code for Object Relational Mappings (ORM) in support for development of information systems. The relationship below "ORM" is a mandatory XOR.…”

“…Examples of source-code for JPA and XDoclet are presented in Figure 4 (A and C). Such examples can be generated with the support of two different model transformations, exemplified in [5] using modelto-code generations. In contribution, next section exemplifies the use of variant transformations.…”

“…With support of WCT, one can fragment a transformation into independent modules that are used in runtime or combined through generative techniques discussed in [4] [5]. These elements are also abstractions illustrated in Figure 3 (A) with model elements named "implSpecPoint" and "extSpecPoint".…”

“…In this sense, Figure 7 illustrates an integration test case for transformations of a TCDM discussed and exemplified in [5] that complements the TCDM illustrated in Figure 3 (A). This example brings many transformations representing all the Model Driven Architecture (MDA) recommended views [27], including Computation Independent Model (CIM); Platform Independent Model (PIM), Platform Specific Model (PSM) and Source-code.…”

“…In order to provide a specific solution, this paper presents an extended JUnit API to automate test cases for variant transformations, with similar performance to the regular API. We introduce this solution into a model transformation engine, namely WCT [5]. The validation of this work is a set of automated test cases that deals with a complex and real scenario in adapting large scale transformations, presenting some results in comparison with previous experiences in [4].…”