Model transformations are touted to play a key role in Model Driven DevelopmentTM. Although well-established standards for creating metamodels such as the Meta-Object Facility exist, there is currently no mature foundation for specifying transformations among models. We propose a framework for the classification of several existing and proposed model transformation approaches. The classification framework is given as a feature model that makes explicit the different design choices for model transformations. Based on our analysis of model transformation approaches, we propose a few major categories in which most approaches fit.

/pdf/feature-based-survey-of-model-transformation-approaches-2hq9yv60ag.pdf

Feature-based survey of model transformation approaches

As with other software development artifacts, model transformations are not bug-free and so must be systematically verified. Their nature, however, means that transformations require specialist verification techniques. This paper brings together current research on model transformation verification by classifying existing approaches along two dimensions. Firstly, we present a coarse-grained classification based on the technical details of the approach (e.g., testing, theorem proving, model checking). Secondly, we present a finer-grained classification which categorizes approaches according to criteria such as level of formality, transformation language, properties verified. The purpose of the survey is to bring together research in model transformation verification to act as a resource for the community. Furthermore, based on the survey, we identify a number of trends in current and past research on model transformation verification.

A survey of approaches for verifying model transformations

Model-Driven Engineering promotes the use of models to conduct the different phases of the software development. In this way, models are transformed between different languages and notations until code is generated for the final application. Hence, the construction of correct Model-to-Model (M2M) transformations becomes a crucial aspect in this approach.

Even though many languages and tools have been proposed to build and execute M2M transformations, there is scarce support to specify correctness requirements for such transformations in an implementation-independent way, i.e., irrespective of the actual transformation language used.

In this paper we fill this gap by proposing a declarative language for the specification of visual contracts, enabling the verification of transformations defined with any transformation language. The verification is performed by compiling the contracts into QVT to detect disconformities of transformation results with respect to the contracts. As a proof of concept, we also report on a graphical modeling environment for the specification of contracts, and on its use for the verification of transformations in several case studies.

/pdf/automated-verification-of-model-transformations-based-on-1bwpga33jf.pdf

Automated verification of model transformations based on visual contracts

A major challenge of the OMG Model-Driven Architecture (MDA) initiative is to be able to define and execute transformations of models. Such transformations may be defined in several ways and with various motivations. Our motivation is to specify model transformations independently of any transformation technology. To achieve this goal, we propose to define transformation contracts. We argue that model transformation contracts are an essential basis for the MDA, they can be used for specification, validation and test of transformations. This paper focuses on the specification of model transformation contracts. We investigate the way to define them using standard UML and OCL features. In addition to presenting the approach and some experimental results, this paper discusses the relevance and limits of standard OCL to define transformation contracts.

/pdf/ocl-for-the-specification-of-model-transformation-contracts-3nnmrz85z4.pdf

OCL for the Specification of Model Transformation Contracts

Model transformations play a critical role in Model Driven Engineering, and thus rigorous techniques for testing model transformations are needed. This paper identifies and discusses important issues that must be tackled to define sound and practical techniques for testing transformations.

/pdf/model-transformation-testing-challenges-34pe63vv5w.pdf

Model Transformation Testing Challenges

A major challenge of the OMG Model-Driven Architecture (MDA) initiative is to be able to define and execute transformations of models. Such transformations may be defined in several ways and with various motivations. Our motivation is to specify model transformations independently of any transformation technology. To achieve this goal, we propose to define transformation contracts. We argue that model transformation contracts are an essential basis for the MDA, they can be used for specification, validation and test of transformations. This paper focuses on model transformation contract specification. We investigate the way to define them using standard UML and OCL features. In addition to presenting the approach and some experimental results, this paper discusses some limits of standard OCL to define transformation contracts as well as some hints to bypass these limitations.

/pdf/model-transformation-contracts-and-their-definition-in-uml-4e38nbs1jq.pdf

Model Transformation Contracts and their Definition in UML and OCL

Les architectures logicielles sont centrales vis-a-vis des processus logiciels de construction des applications. Les langages de description d'architectures (ADLs) representent la solution la plus adaptee pour definir de telles architectures. Toutefois, les concepts de ces ADLs sont en regle generale figes et leurs utilisations ne repond pas necessairement aux differentes preoccupations des processus logiciels. De plus, leur aspect syntaxique ne facilite pas la cooperation des differents acteurs de processus logiciels. Notre proposition, CODeX, fournit un cadre de travail pour meta-modeliser des ADLs. Ces meta-modeles permettent de definir les concepts lies aux architectures necessaires a un processus logiciel. Dans le but de structurer les ADLs ainsi definis et de permettre la collaboration des differents acteurs d'un processus logiciel, les meta-modeles sont definis en mettant en œuvre la separation des preoccupations architecturales d'un processus logiciel. Cette separation definit l'organisation des differents concepts d'un ADL. Un outillage complement de ce cadre de travail permet de produire automatiquement, sur la base du meta-modele d'un ADL, l'environnement associe pour la manipulation des architectures logicielles. Ce dernier est architecture autour d'une representation reifiee des architectures logicielles. Cette representation suit la separation des preoccupations definie dans le meta-modele et permet d'offrir a chaque acteur d'un processus logiciel une vue dediee sur l'architecture d'une application.

https://tel.archives-ouvertes.fr/tel-00007381/document

Séparation des préoccupations et méta-modélisation pour environnements de manipulation d'architectures logicielles à base de composants

The adoption of IMS-LD as a standard conceptual model for pedagogical scenarios description will allow increasing interoperability in online learning. Since IMS-LD modeling activity does not count among the practices of teachers, its imperative to provide a methodology to see them through this task. IMS-LD authors proposed one in the Best Practices Guide but unfortunately existing LD tools were not designed to support this or any other methodology. We propose a generic support for methodologies through a formal framework (Incremental Modeling Process) and provide an implementation (ModX module) using IMSLD best practices as an example.

https://www.computer.org/csdl/pds/api/csdl/proceedings/download-article/12OmNz61dEd/pdf

Supporting Generic Methodologies to Assist IMS-LD Modeling

Ambient computing is one of the more significant recent advances in computer-human interactions. With the ambient intelligence paradigm, computers become embedded in our natural surroundings. As they are context sensitive and adaptable, they better provide smart services to humans. But ambient computing requires communication between several heterogeneous components that are not supposed to communicate each other. This paper describes how we use a workflow to facilitate the design of multichannel interfaces for ambient computing. Our results show that different devices (such as Wiimote, multi-touch screen, telephone, etc.) can be managed in order to activate real things (such as lamp, fan, robot, webcam, etc.). A smart digital home case study illustrates a possible implementation of our approach and shows how it allows redesigning easily some parts of the ambient system just by modifying the workflow.

http://www.lifl.fr/~rouillar/publi/2010_Rouillard_Tarby_LePallec_Marvie_ACHI2010.pdf

Raphaël Marvie

Papers

OCL for the Specification of Model Transformation Contracts

Model Transformation Contracts and their Definition in UML and OCL

Séparation des préoccupations et méta-modélisation pour environnements de manipulation d'architectures logicielles à base de composants

Supporting Generic Methodologies to Assist IMS-LD Modeling

Facilitating the Design of Multi-channel Interfaces for Ambient Computing