AOP's Modeling Research and Model Transformation with ATL in MDA

2011 ◽  
Vol 291-294 ◽  
pp. 97-100
Author(s):  
Jing Jun Zhang ◽  
Fei Wei ◽  
Hui Li
Keyword(s):  
Model Transformation ◽  
Model Driven Architecture ◽  
Aspect Oriented Programming ◽  
Model Driven ◽  
Transformation Language ◽  
Model Conversion

With Aspect Oriented Programming(AOP) technology, Model Driven Architecture(MDA) and ATLAS Transformation Language(ATL), this paper proposes a PIM framework of based on OOP and a PIM framework of based on AOP, also proposes a idea with ATL accept model conversion signals to model transformation.

Quality of Service and Extra-Functional Properties for Web Services

2013 ◽  
pp. 35-64
Author(s):  
Guadalupe Ortiz ◽  
Behzad Bordbar
Keyword(s):  
Quality Of Service ◽  
Web Services ◽  
Functional Properties ◽  
Model Transformation ◽  
Model Driven Architecture ◽  
Aspect Oriented Programming ◽  
Maintenance Costs ◽  
Model Driven

The presented approach draws on two main software techniques: Model-Driven Architecture, and aspect-oriented programming. The method involves modeling of the Quality of Service and Extra-functional properties in a platform-independent fashion. Then applying model transformation, the platform-independent models are transformed into platform-specific models, and finally into code. The code for Quality of Service and Extra-functional properties are integrated into the system relying on aspect-oriented techniques in a decoupled manner. The presented approach is evaluated with the help of a case study to establish that the approach results in increasing the system’s modularity and thus reducing implementation and maintenance costs.

A Description and Transformation Approach for Model Driven Architecture

2013 ◽  
Vol 756-759 ◽  
pp. 2168-2172
Author(s):  
Lei Wang
Keyword(s):  
Web Application ◽  
Model Transformation ◽  
Model Driven Architecture ◽  
Target Model ◽  
Model Driven ◽  
Mapping Rules ◽  
Transformation Approach

By referring to the widely used web application frameworks on JavaEE, a description and transformation approach is proposed to resolve the problems of the transformation from platform independent models to platform specific models. To achieve model transformation, mapping rules can be defined according to the structure of the target model. Specific technologies of target application domains have less influence on the use of this approach. The experiment shows that the approach captures the essence, process and requirements of model-driven architecture, and thus can be used widely as a new guidance for model transformation.

scholarly journals Modeling Principles of the Sequence Diagram and its Application in MDA Software Paradigm

2012 ◽  
Vol 6-7 ◽  
pp. 15-19
Author(s):  
De Ren Yang ◽  
Min Liu ◽  
Zhao Hua Gu
Keyword(s):  
Software Design ◽  
Model Transformation ◽  
Object Oriented ◽  
Object Oriented Programming ◽  
Sequence Diagram ◽  
Software Modeling ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Design Object ◽  
Modeling Principles

The sequence diagram can be used to design object-oriented software; however, its modeling principles are lack of research. In this paper, its application in software design was studied, and its inherent linkage with object-oriented programming was discussed, and the interactive mechanism among its elements was explored. The modeling principles for it were proposed; and its application in Model Driven Architecture (MDA) software paradigm was analyzed; and finally the model represented with it, especially the transformation and traceability of models in MDA software paradigm were analyzed. This research is useful to optimize software modeling and to automate model transformation in MDA software paradigm.

A Contribution to the Specification of Model Transformations with Metamodel Matching Approach

2017 ◽  
Vol 8 (3) ◽  
pp. 1-23 ◽  
Author(s):  
Karima Berramla ◽  
El Abbassia Deba ◽  
Abou El Hassen Benyamina ◽  
Djilali Benhamamouch
Keyword(s):  
Model Transformation ◽  
Model Transformations ◽  
Abstract Representation ◽  
Model Driven ◽  
Transformation Rules ◽  
Transformation Language ◽  
Matching Technique ◽  
Concrete Syntax ◽  
Abstract Level ◽  
Use Of Models

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 metamodels. This idea is illustrated by different transformation examples.

scholarly journals The Model Transformation for Getting a UML Class Diagram from a Topological Functioning Model

2015 ◽  
Vol 17 (1) ◽  
pp. 88-96
Author(s):  
Arturs Solomencevs
Keyword(s):  
Model Transformation ◽  
Class Diagram ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Uml Class Diagram ◽  
Independent Model

Abstract The approach called Topological Functioning Modeling for Model Driven Architecture (TFM4MDA) uses a Topological Functioning Model (TFM) as a formal Computation Independent Model (CIM) within the Model Driven Architecture (MDA). The object of this research is the construction of a UML class diagram on the Platform Independent Model (PIM) level in conformity with the TFM. Nowadays this transformation is executed manually. Manual creation of models is time-consuming and there is a risk of making mistakes. These drawbacks increase expenses and reduce efficiency of TFM4MDA approach. That is why automation of transformation is useful. The paper presents an algorithm for the transformation which is written in a pseudocode and can be implemented as a tool.

scholarly journals Contrasting dedicated model transformation languages versus general purpose languages: a historical perspective on ATL versus Java based on complexity and size

2021 ◽  
Author(s):  
Stefan Höppner ◽  
Timo Kehrer ◽  
Matthias Tichy
Keyword(s):  
Model Transformation ◽  
Historical Perspective ◽  
General Purpose ◽  
Model Transformations ◽  
Future Research ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Transformation Language ◽  
Key Concepts ◽  
Code Changes

AbstractModel transformations are among the key concepts of model-driven engineering (MDE), and dedicated model transformation languages (MTLs) emerged with the popularity of the MDE pssaradigm about 15 to 20 years ago. MTLs claim to increase the ease of development of model transformations by abstracting from recurring transformation aspects and hiding complex semantics behind a simple and intuitive syntax. Nonetheless, MTLs are rarely adopted in practice, there is still no empirical evidence for the claim of easier development, and the argument of abstraction deserves a fresh look in the light of modern general purpose languages (GPLs) which have undergone a significant evolution in the last two decades. In this paper, we report about a study in which we compare the complexity and size of model transformations written in three different languages, namely (i) the Atlas Transformation Language (ATL), (ii) Java SE5 (2004–2009), and (iii) Java SE14 (2020); the Java transformations are derived from an ATL specification using a translation schema we developed for our study. In a nutshell, we found that some of the new features in Java SE14 compared to Java SE5 help to significantly reduce the complexity of transformations written in Java by as much as 45%. At the same time, however, the relative amount of complexity that stems from aspects that ATL can hide from the developer, which is about 40% of the total complexity, stays about the same. Furthermore we discovered that while transformation code in Java SE14 requires up to 25% less lines of code, the number of words written in both versions stays about the same. And while the written number of words stays about the same their distribution throughout the code changes significantly. Based on these results, we discuss the concrete advancements in newer Java versions. We also discuss to which extent new language advancements justify writing transformations in a general purpose language rather than a dedicated transformation language. We further indicate potential avenues for future research on the comparison of MTLs and GPLs in a model transformation context.

Model-Driven Architecture and IT Governance Ontology

2012 ◽  
Vol 3 (4) ◽  
pp. 1-6
Author(s):  
Carsten Mueller
Keyword(s):  
Information Technology ◽  
Model Transformation ◽  
It Governance ◽  
Semantic Mapping ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Technology Governance ◽  
Enabling Technologies ◽  
Information Technology Governance

In this article a research vision which links the disciplines Model-Driven Architecture and IT Governance is presented. Model transformation and semantic mapping are enabling technologies for new, advanced solutions to address IT (Information Technology) Governance interoperability. In a prototype the generation of a model is shown based on an IT Governance domain.

The Study of A Management Information System Based on AOP and MDA

2011 ◽  
Vol 268-270 ◽  
pp. 1601-1606
Author(s):  
Jing Jun Zhang ◽  
Fei Wei ◽  
Hui Li
Keyword(s):  
Information System ◽  
Management Information System ◽  
Class Diagram ◽  
Management Information ◽  
Model Driven Architecture ◽  
Aspect Oriented Programming ◽  
Activity Diagram ◽  
Crosscutting Concerns ◽  
Model Driven ◽  
Crosscutting Concern

This paper introduces Model Driven Architecture(MDA) and Aspect Oriented Programming(AOP), based on train online ticketing system, it describes various modules of the activity diagram and class diagram of this system. Through the activity diagram, it knows that which is crosscutting concerns, and then modeling for the crosscutting concern. This paper is improving the traditional MDA modeling with AOP technology.

Sign in / Sign up

Export Citation Format

Share Document