Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
2005, … Research, Management and …
The information transformation problem of model driven software development (MDSD) processes is gaining increasing attentions. In this paper, we present an indepth analysis of the major causes leading to the ambiguities of existing transformation. A metamodel based approach is then proposed to address these causes. A mechanism to generate transformation rules is devised based on a classification of the UML metamodel elements to be used in subsequent transformation processes. Some other critical issues relating to the generated transformation system are also discussed.
2005
Abstract Software model transformation is a key issue in modern software engineering. Currently, new approaches, methods and techniques are being researched built intensively on expressive and efficient transformation systems. There is a demand for researching the theoretical and practical foundations of these transformation systems.
Information & Software Technology, 2019
In the Model Driven Development (MDD) approach, model transformations are responsible for the semiautomation of software development process converting models between different abstraction levels. The development of model transformations involves a complexity inherent to the transformation domain, in addition to the complexity of software development in general. Therefore, the construction of model transformations requires software engineering feature such as processes and languages to facilitate its development and maintenance. Objective: This paper presents a framework to develop unidirectional relational model transformation using the MDD approach itself, which integrates: (i) a software development process suitable for the model transformation domain (ii) a Domain specific language for transformation modeling (iii) a transformation chain, to (semi) automate the proposed process, and (iv) a development environment to support it. Methods: The proposal systematizes the development of model transformation, following the MDD principles. An iterative and incremental process guides transformation development from requirement specification to transformation codification. The proposal has been evaluated through a case study and a controlled experiment. Results: The framework enables model transformation specification at a high abstraction level and (semi) automatically transforms it into models at a low abstraction level until the transformation code. The results of the case study showed that people with different levels of knowledge of MDD, or without experience in transformation languages, were able to develop transformations through the framework and generated executable code. Conclusions: The framework integrates the essential elements involved in the development of model transformation and enables the abstraction of technological details. The results of the case study and controlled experiment showed the feasibility of the proposal and its use in dealing with the complexity involved in model transformation development.
methods, 2002
MDA (Model Driven Architecture) attempts to solve some common problems of current software architectures to reduce the complexity of software development: i) separation of technology dependent concepts from the independent concepts, ii) automate the software development process, and iii) separation of domain, technology and technological concerns to avoid the confusions because of the combination of different types of concepts. MDA introduces two basic solutions to solve these problems: i) description of specialized modeling languages and ii) model transformations and mappings. Currently, the first concept (description of specialized modeling language) has been widely studied and there are general solutions and standards (Profiles [5] and MOF [12]). But the second solution has not been well studied yet and practical solutions depend on specific script languages, and the standards that include some kind of mapping proposal make an informal description of the mappings. We are going to introduce some solutions to express complex transformations where the source and target modeling structures are not limited to simple modeling elements.
Programming technologies have improved continuously during the last decades, but from an Information Systems perspective, some well-known problems associated to the design and implementation of an Information Systems persists. Object-Oriented Methods, Formal Specification Languages, Component-Based Software Production... This is just a very short list of technologies proposed to solve a very old and, at the same time, very wellknown problem: how to produce software of quality. Programming has been the key task during the last 40 years, and the results have not been successful yet. This work will explore the need of facing a sound software production process from a different perspective: the non-programming perspective, where by nonprogramming we mainly mean modeling. Instead of talking about Extreme Programming, we will introduce a Extreme Non-Programming (Extreme Modeling-Oriented) approach. We will base our ideas on the intensive work done during the last years, oriented to the objective of generating code from a higher-level system specification, normally represented as a Conceptual Schema. Nowadays, though, the hip around MDA has given a new push to these strategies. New methods propose sound model transformations which cover all the different steps of a sound software production process from an Information Systems Engineering point of view. This must include Organizational Modeling, Requirements Engineering, Conceptual Modeling and Model-Based Code Generation techniques. In this context, it seems that the time of Model Transformation Technologies is finally here…
International Conference on Software …, 2006
Model Driven Engineering (MDE) tackles the elusive problem of system development by promoting the usage of models as the primary artifact to be constructed and maintained [1]. MDE shifts software devel-opment from a code-centric activity to a model centric activity. Accomplishing this ...
2020
Model Driven Development is an approach that makes use of models instead of code in software development. At its core, there is a transformation chain responsible for the (semi) automation of the development process converting models into models until code. The development of transformations has been a challenge as there is an inherent complexity of the transformation domain in addition to the complexity of the software being constructed using these transformations. In order to assist this development as well as improve transformation quality, it is important to adopt software engineering facilities such as processes, languages and other techniques. This paper presents a systematic literature review of strategies currently proposed to develop model transformations. We aim to investigate development processes or any other strategies used to guide transformation development, the phases of software development life cycle considered, modeling languages adopted for specification and also...
2015
Model Driven Engineering (MDE) is gaining popularity as an alternative to the code-centric software development approach. Model Transformation (MT) is one of the main components of MDE. MT can be visualized as a program with models as inputs. Model evaluation and processing is automated by a Model Transformation tool. In this paper, we walk through the terminologies involved in MT and elaborate the benefits of MT with practical usage scenarios. The paper highlights the most recent challenges faced in the process to make model transformation more sophisticated. The intent of the paper is to portray a complete picture of model transformation in a way to relate the practical implementations with respect to the theoretical aspects of MT. The paper concludes by putting lights on some of the current trends in the field and the areas in model transformation where significant contribution is the needed.
se.cs.depaul.edu
Model Driven Engineering(MDE) is a model-centric software development approach aims at improving the quality and productivity of software development processes. While some progresses in MDE have been made, there are still many obstacles in realizing the full ...
2010
Abstract. Model transformation is a key activity in Model-Driven Engineering (MDE). Transformations map between models, in different languages and/or at different levels of abstraction. Model transformation introduces challenges for specification, verification and validation. Normally, MDE development requires planning which includes metamodel and transformation design and a customized testing.
2008
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 part, 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).
Proceedings of the 27th International Conference on Software Engineering and Knowledge Engineering, 2015
Transformations are key artifacts in the MDD (Model Driven Development) approach: a software development project can be defined through a transformation chain converting source models into target models until code, enabling development process automation. Transformations can be complex and demand software processes, languages and techniques to improve their development in order to increase reuse, portability, correctness, and so on. In this context we propose a framework to develop model transformations using MDD. This paper presents a Model Transformation Profile (MTP) defined as the domain specific language of the framework.
IEEE/ASME Journal of Microelectromechanical Systems - J MICROELECTROMECHANICAL SYST, 2003
In a Model Driven Architecture (MDA) software development process, models are repeatedly transformed to other models in order to finally achieve a set of models with enough details to implement a system. Generally, there are multiple ways to transform one model into another model. Alternative target models differ in their quality properties and the selection of a particular model is determined on the basis of specific requirements. Software engineers must be able to identify, compare and select the appropriate transformations within the given set of requirements. The current transformation languages used for describing and executing model transformations only provide means to specify the transformations but do not help to identify and select from the alternative transformations. In this paper we propose a process and a set of techniques for constructing a transformation space for a given transformation problem. The process uses a source model, its meta-model and the meta-model of th...
Information and Software Technology, 2013
Context. Model transformations play a key role in any software development proposal based on Model-Driven Engineering principles. However, despite the inherent complexity of developing model transformations, little attention has been paid to the application of MDE principles to the development of model transformations. Objective. In order to: a) address the inherent complexity of model transformations development and b) alleviate the problem of the diversity of the languages that are available for model transformation, this paper proposes applying MDE principles to the development of model transformations. In particular, we have adopted the idea of handling model transformations as transformation models in order to be able to model, transform and generate model transformations. Method. The proposal follows an MDA-based approach that entails the modeling of model transformations at different abstraction levels and the connection of these models by means of model transformations. It has been empirically validated by conducting a set of case studies following a systematic research methodology. Results. The proposal was supported by the introduction of MeTAGeM, a methodological and technical framework for the model-driven development of model transformations that bundles a set of Domain-Specific Languages for modeling model transformations with a set of model transformations to bridge these languages and (semi-)automate model transformations development.
International Journal of Information System Modeling and Design, 2017
Model-driven engineering (MDE) is a paradigm based on the intensive use of models throughout the life cycle of an application, where model transformation plays an important role. Various model transformation approaches have been proposed, but developers are still faced with the complexity of model transformation specifications. Most of these approaches are based on the specification of transformation rules with a concrete syntax at a low level where the developer must master the transformation language. The question at this level is how to generate a model transformation specification that must be at a very abstract level, independent of any transformation language. This article aims to propose an approach to generate an abstract representation of transformation rules and these are used to produce a source code written in a chosen transformation language. The transformation rules are calculated semi-automatically by using a matching technique on elements of source and target metamod...
This article proposes a taxonomy of model transformation, based on the discussions of a working group on model transformation of the Dagstuhl seminar on Language Engineering for Model-Driven Software Development. This taxonomy can be used, among others, to help developers in deciding which model transformation language or tool is best suited to carry out a particular model transformation activity.
2015
Introduction In recent years many organizations have begun to consider MDA as an approach to design and implement enterprise applications. The central idea of MDA is to separate the platform independent design from the platform specific implementation of applications delaying as much as possible the dependence on specific technologies [1]. The MDA uses models as first class entities, enabling the definition and automatic execution of transformations between models and from models to code. The creation of meta-models for specifying modeling languages is a basic task in MDA. Models in MDA are the key artifacts in all phases of development and are mostly expressed with Unified Modeling Language (UML). Also the specification of transformations between models, are called model-to-model (M2M) transformations, and from model to code, are called model-to-text (M2T) transformations. The main advantage of this approach of software development is that MDA tools enable these transformations to ...
2004
The Model Driven Architecture necessitates not only the application of software engineering disciplines to the specification of modeling languages (language-ware) but also to design inter and intra-language model transformations (transformation-ware). Although many model transformation approaches exist, their focus is almost exclusively put on functional correctness and intuitive description language while the importance of engineering issues such as reusability, maintainability, performance or compactness are neglected. To tackle these problems following the MDA philosophy, we argue in the paper that model transformations should also be regarded as models (i.e., as data). More specifically, we demonstrate (i) how generic transformations can provide a very compact description of certain transformation problems and (ii) how meta-transformations can be designed that yield efficient transformations as their output model.
2007
DEVELOPING MODEL TRANSFORMATION TOOLS USING THE UML METAMODEL: CHALLENGES AND SOLUTIONS Aritra Bandyopadhyay, Sudipto Ghosh Department of Computer Science Colorado State University Fort Collins, Colorado 80523 baritra,ghosh¡ @cs.colostate. edu ABSTRACT Model transformation tools often work at the metamodel level by manipulating instances of metamodel constructs.
2004
This report summarises the results of the discussions of a working group on model transformation of the Dagstuhl Seminar on Language Engineering for Model-Driven Software Development. The main contribution is a taxonomy of model transformation. This taxonomy can be used to help developers in deciding which model transformation approach is best suited to deal with a particular problem.
Journal of Software Engineering and Applications, 2010
Model Driven Engineering (MDE) is a model-centric software development approach aims at improving the quality and productivity of software development processes. While some progresses in MDE have been made, there are still many challenges in realizing the full benefits of model driven engineering. These challenges include incompleteness in existing modeling notations, inadequate in tools support, and the lack of effective model transformation mechanism. This paper provides a solution to build a template-based model transformation framework using a simplified metamode called Hierarchical Relational Metamodel (HRM). This framework supports MDE while providing the benefits of readability and rigorousness of meta-model definitions and transformation definitions.
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.