Authors:
Slimane Hammoudi
1
;
Wajih Alouini
2
and
Denivaldo Lopes
3
Affiliations:
1
Ecole Supèrieure d’Electronique de l’Ouest (ESEO), France
;
2
ISIG, Institut Supérieur d’Informatique et de Gestion, University of Kairouan, Tunisia
;
3
Federal University of Maranhão (UFMA), CCET – DEE, Brazil
Keyword(s):
Model Driven Architecture, Transformation Language, Mapping Metamodel, Matching Metamodel, Semi-Automatic Transformation, Transformation Architecture and Transformation Methodology.
Related
Ontology
Subjects/Areas/Topics:
Enterprise Information Systems
;
Information Systems Analysis and Specification
;
Methodologies, Processes and Platforms
;
Model-Driven Software Development
;
Modeling Formalisms, Languages and Notations
;
Modeling of Distributed Systems
;
Software Engineering
;
Systems Engineering
Abstract:
Recently, Model Driven Engineering (MDE) approaches have been proposed for supporting the development, maintenance and evolution of software systems. Model driven architecture (MDA) from OMG (Object Management Group), “Software Factories” from Microsoft and the Eclipse Modelling Framework (EMF) from IBM are among the most representative MDE approaches. Nowadays, it is well recognized that model transformations are at the heart of these approaches and represent as a consequence one of the most important operations in MDE. However, despite the multitude of model transformation languages proposals emerging from university and industry, these transformations are often created manually. In this paper we propose in the first part an extended architecture that aims to semi-automate the process of transformation in the context of MDA. This architecture introduces mapping and matching as first class entities in the transformation process, represented by models and metamodels. In the second pa
rt, our architecture is enforced by a methodology which details the different steps leading to a semi-automatic transformation process. Finally, a classification of these different steps according to two main criteria is presented: how the steps are achieved (manual/automatic), and who is responsible for their achievement (expert, designer or software).
(More)