Model Transformation of Platform Specific Model to Vanilla Model A Proposed Platform Independent Model for Declarative User Interface.

2018 ◽  
Vol 6 (11) ◽  
pp. 622-627
Author(s):  
Smita Agarwal ◽  
Alok Aggarwal ◽  
S. Dixit ◽  
Adarsh Kumart
2013 ◽  
Vol 670 ◽  
pp. 208-215
Author(s):  
Ying Che ◽  
G. Wang ◽  
M. Lv ◽  
B.Y. Ren

The model transformation from Computation Independent Model (CIM) to Platform Independent Model (PIM) level is one of the crucial and difficult points in the implementation process of model-driven Enterprise Resource Planning (ERP) system. For achieving the semantic conforming transformation between these two abstract modeling levels in Model Driven Architecture (MDA), a model transformation method based on ontology technology was proposed, which was a semi-automatic and general method. Firstly, the existing problems of model transformation from CIM level to PIM level in current studies were analyzed. Then, a model transformation framework based on ontology was built, the basic concepts relating to ontology were defined, and the whole architecture was described. After that, the transformation method was researched from two parts, the discovering of mapping rules and the occurrence of model transformation, which included the discovering technology of mapping rules based on similarity and the working principles of model transformation generator. Finally, a model transformation example was provided for validating the practicability and feasibility of proposed theories.


Author(s):  
Francisco José Domínguez-Mayo ◽  
María José Escalona ◽  
Manuel Mejías ◽  
Isabel Ramos ◽  
Luis Fernández

Diverse development web methodologies currently exist in the field of Model-Driven Web Engineering (MDWE), each of which covers different Levels of Abstraction on Model-Driven Architecture (MDA): Computation Independent Model (CIM), Platform Independent Model (PIM), Platform Specific Model (PSM), and Code. Given the high number of methodologies available, it has become necessary to define objective evaluation tools to enable development teams to improve their methodological environment and help designers of web methodologies design new effective and efficient tools, processes and techniques. Since proposals are constantly evolving, the need may arise not only to evaluate the quality but also to find out how it can be improved. This paper presents an approach named QuEF (Quality Evaluation Framework) oriented towards evaluating, through objectives measures, the quality of information technology infrastructure, mainly in MDWE methodology environments.


Author(s):  
Yashwant Singh ◽  
Manu Sood

The Model-Driven Architecture approach to software development uses transformation models for transforming Platform-Independent Models (PIM) into Platform-Specific Models (PSM) as its core software development strategy. The Model-Driven Architecture (MDA) approach and corresponding standards of the software development based on models have been initiated by the Object Management Group. In this chapter, the authors analyze the basic models of MDA (i.e., Computational Independent Model [CIM], PIM, and PSM) using a suitable example and formalize the model transformations for transforming PIM into PSM. These transformations have been illustrated through the generation of a Relational Model, an Enterprise Java Bean (EJB) Model, and a Web Model from PIM for the example under consideration, using UML profile, and keeping in mind the property of reusability of models in MDA transformations. The focus has been on the specification and formalization of rules needed to get the Relational PSM, EJB PSM, and Web PSM from PIM. A transformation tool, whose functionality of transformation of PIM into Relational PSM, EJB PSM, and Web PSM, is illustrated in this chapter.


Author(s):  
Liliana María Favre

The model-driven architecture (MDA) is an approach to model-centric software development. The concepts of models, metamodels, and model transformations are at the core of MDA. Model-driven development (MDD) distinguishes different kinds of models: the computation-independent model (CIM), the platform-independent model (PIM), and the platform-specific model (PSM). Model transformation is the process of converting one model into another model of the same system, preserving some kind of equivalence relation between them. One of the key concepts behind MDD is that models generated during software developments are represented using common metamodeling techniques. In this chapter, we analyze an integration of MDA metamodeling techniques with knowledge developed by the community of formal methods. We describe a rigorous framework that comprises the NEREUS metamodeling notation (open to many other formal languages), a system of transformation rules to bridge the gap between UML/OCL and NEREUS, the definition of MDA-based reusable components, and model/metamodeling transformations. In particular, we show how to integrate NEREUS with algebraic languages using the Common Algebraic Specification Language (CASL). NEREUS focuses on interoperability of formal languages in MDD.


Author(s):  
Samia Nasiri ◽  
Yassine Rhazali ◽  
Mohammed Lahmer

Model-driven architecture (MDA) is an alternative approach of software engineering that allows an automatic transformation from business process model to code model. In MDA there are two transformation kinds: transformation from computing independent model (CIM) to platform independent model (PIM) and transformation from PIM to platform specific model (PSM). In this chapter, the authors based on CIM to PIM transformation. This transformation is done by developing a platform that generates class diagram, presented in XMI file, from specifications that are presented in user stories, which are written in natural language (English). They used a natural language processing (NLP) tool named “Stanford Core NLP” for extracting of the object-oriented design elements. The approach was validated by focusing on two case studies: firstly, comparing the results with the results other researchers; and secondly, comparing the results with the results obtained manually. The benefits of the approach are aligned with agile methods goals.


Author(s):  
Liliana Favre

The model-driven architecture (MDA) is an approach to model-centric software development. The concepts of models, metamodels, and model transformations are at the core of MDA. Model-driven development (MDD) distinguishes different kinds of models: the computation-independent model (CIM), the platform-independent model (PIM), and the platform-specific model (PSM). Model transformation is the process of converting one model into another model of the same system, preserving some kind of equivalence relation between them. One of the key concepts behind MDD is that models generated during software developments are represented using common metamodeling techniques. In this chapter, we analyze an integration of MDA metamodeling techniques with knowledge developed by the community of formal methods. We describe a rigorous framework that comprises the NEREUS metamodeling notation (open to many other formal languages), a system of transformation rules to bridge the gap between UML/OCL and NEREUS, the definition of MDA-based reusable components, and model/metamodeling transformations. In particular, we show how to integrate NEREUS withalgebraic languages using the Common Algebraic Specification Language (CASL). NEREUS focuses on interoperability of formal languages in MDD.


Author(s):  
Liliana María Favre ◽  
Claudia Teresa Pereira ◽  
Liliana Inés Martinez

The model driven architecture (MDA) is an initiative proposed by the object management group (OMG), which is emerging as a technical framework to improve productivity, portability, interoperability, and maintenance (MDA, 2003). MDA promotes the use of models and modelto- model transformations for developing software systems. All artifacts, such as requirement specifications, architecture descriptions, design descriptions, and code are regarded as models. MDA distinguishes four main kinds of models: computation independent model (CIM), platform independent model (PIM), platform specific models (PSM), and implementation specific model (ISM).


2013 ◽  
Vol 850-851 ◽  
pp. 728-732
Author(s):  
Hao Wu ◽  
Qing Yi Hua

A model-based user interface automatic generation development method was presented to adapt for user interface development requirement under SaaS environment. This method deployed abstract interface model, transformation model, specific interface model and final interface in different abstract level at running time. So, the server-end could distribute the user interface to the client-end by one time a widow or page. By a case study, this method can satisfy the demands of user interface under SaaS environment, and it is so simple to study and use.


2020 ◽  
Vol 2020 ◽  
pp. 1-14
Author(s):  
Ngo Van Hien ◽  
Van-Thuan Truong ◽  
Ngoc-Tam Bui

This paper introduces a model-driven control realization, which is based on the systems engineering concepts of the model-driven architecture (MDA)/model-based systems engineering (MBSE) approach combined with the real-time UML/SysML, extended/unscented Kalman filter (EKF/UKF) algorithms, and hybrid automata, in order to conveniently deploy controllers of autonomous underwater vehicles (AUVs). This model also creates a real-time communication pattern, which can permit the designed components to be customizable and reusable in new application developments of different AUV types. The paper brings out stepwise adapted AUV dynamics for control that are then combined with the specialization of MDA/MBSE features as follows: the computation independent model (CIM) is defined by the specification of the use-case model together with hybrid automata to gather the requirement analysis for control; the platform-independent model (PIM) is then designed by specializing the real-time UML/SysML’s features including main control capsules that depict structures and behaviors of controllers in detail; and the detailed PIM is subsequently converted into the platform-specific model (PSM) by object-oriented platforms to rapidly implement the AUV controller. Based on this proposed model, a horizontal planar trajectory-tracking controller was deployed and tested that permits a miniature AUV possessing a torpedo shape to reach and follow the desired horizontal planar trajectory.


Sign in / Sign up

Export Citation Format

Share Document