Model Driven Architecture Tool Research Articles

An integrated framework for automated simulation of SysML models using DEVS

System models are constructed to design, study, and understand complex systems. According to the systems modeling language (SysML) that is a standard for model-based system engineering, all engineering activities should be performed using a common model. To validate complex system models defined in SysML, simulation is usually employed. There are numerous efforts to simulate SysML models using different simulation methods and tools. However, the efficient support of automated generation of executable simulation code is still an issue tangled by the research community. This paper introduces DEVSys, an integrated framework for utilizing existing SysML models and automatically producing executable discrete event simulation code, according to model driven architecture (MDA) concepts. Although this approach is not simulation-specific, discrete event system specification (DEVS) was employed, due to the similarities between SysML and DEVS, mainly in system structure description, and the mature, yet ongoing research on expressing executable DEVS models in a simulator-neutral manner. DEVSys framework elements include (a) a SysML profile for DEVS, enabling integration of simulation capabilities into SysML models, (b) a meta-model for DEVS, allowing the utilization of MDA concepts and tools, (c) a transformation of SysML models to DEVS models, using a standard model transformation language as query/view/transform (QVT), and (d) the generation of DEVS executable code for a DEVS simulation environment with an extensible markup language (XML) interface. The definition and implementation of DEVSys elements, as well as the process for its application are demonstrated and discussed, with the aid of a simple working example.

Data Warehouse Scripts Generation Through MDA Cartridge

Increasing market competitiveness has led entrepreneurs to require more and more information from Information Technology areas to allow for efficient decision-making. Two alternatives to solving this problem are allied in this work: use of Model Driven Architecture (MDA) and Data Warehousing (DW). This research developed and tested a MDA cartridge. It creates scripts for automatic generation and loads DW based databases on the Online Transaction Processing Model (OLTP) through a MDA tool. With the use of this approach any change in the model would be a corresponding change in the scripts without manual rework.

A MDA Approach for avigational and User Perspectives


 
 
 The study presented in this paper focuses on a navigational and user perspectives analysis of Web applications, highlighting some of their critical points for modeling. To consider these critical points, we propose a notational definition focused on a general metamodel, consisting of three specific metamodels: the Navigational Tree, the Node, and Roles. The metamodels have been implemented with a specific MDA (Model Driven Architecture) tool called AndroMDA, to generate applications for PHP language. Both, the general metamodel and its implementation have been analyzed by means of a proof of concept. Finally, some interesting results as well as the contribution of the proposed metamodel in comparison with other methodological proposals are discussed.
 
 

On Foundation for Certification of Model Driven Architecture (MDA) Tools: Defining a Specification

A modern approach to software development inclu- des a wide variety of processes, which are used to regulate and manage the entire development life cycle. One of th e main aspects to be considered during the preparation stage of so ftware development is the selection of the right tools. No wadays when software systems become more and more complex, an inappropriate selection of the tools may cause proj ect not to succeed at all. That is why the main challenge of th e industry is still aimed on the simplification, optimization, an d automation of software development process. One of the ways to deal with an increasing complexity, as well as not to dig into t he details of the source code, is to use modeling. A model-driven approach, mainly represented by OMG's Model Driven Architecture as the most advanced and popular one, purports to be the next evolutional milestone for the whole software industry. In fact, most of the tools currently available on the market are claimed as complaint, though have never been checked or analyzed for that compliance. Therefore, there should be a certificat ion program defined to figure out the main features of each too l in accordance with OMG standards. The original article proposes a foundation for certification of MDA tools. In particular, this includes the specification of the most common features and optio ns defined to clarify the accordance level of each tool from vari ous perspectives.

MDA (Model-Driven Architecture) as a Software Industrialization Pattern: An Approach for a Pragmatic Software Factories

In this paper we show that the MDA can be considered as a software industrialization pattern (or a software factory). Nearly all industries today are haunted with how to reduce costs, improve quality, faster time-to-market and to maximize profits. These challenges are particularly relevant to the software industry, because it still lags behind other technology sectors as regards industrialization and the timely delivery of software products. Most software are still of poor quality, always finished after deadlines (most don’t finish at all), and are very labour intensive. Here, we discuss the MDA as an approach that may help solving at the same time both problems of industrialization and ever-changing software infrastructures. We propose a MDA Engine based on a real case study in an IT services company. It is a proposal for a framework to create custom MDA tools, based on XMI, XSLT and the Visitor Pattern.

Evaluation of software development through an MDA tool: a case study

Model Driven Architecture (MDA) was born as a standard of Model Driven Development (MDD) to increment the productivity in the software industry. Actually, there exist different models based tools to get an acceptable degree of automation in the applications generation. Many of those tools allow users to build software with high productivity in their respective domains. According their authors, the very challenge of MDA approach and tools is to put emphasis in a satisfactory degree of productivity and, at the same time, increasing others important software qualities such as portability, interoperability, reusability and maintainability. This paper intends to verify the effectiveness of such benefits analyzing the development of a real application using a MDA tool compared with a traditional approach. For analysis purpose, a series of metrics that can help to evaluate the different aspects related to the benefits of MDA was adopted.

MDA기반 학사관리 프로세스 유효성 분석

새로운 패러다임의 시스템 개발 접근 방법은 OMG(Object Management Group)에서 MDA(Model Driven Architecture)로 표준화하고 있다. MDA의 핵심 기술은 모델 중심의 시스템 구현을 위한 기술 구조를 정의하는 것으로 시스템의 설계 및 명세에 대한 구현 기술을 플랫폼 독립적 모델(PIM : Platform Independent Model)로 설계한 후, 구현 환경에 적합한 플랫폼 종속적 모델(PSM : Platform Specific Model)로 설계하여 구현환경에 맞는 언어로 변환하는 기술이다. MDA의 핵심인 MOF(Meta-Object Facility), UML, XMI(XML Metadata Interchange), CWM(Common Warehouse Metamodel) 표준 등이 포함된다. MDA 지원 자동화 툴들은 위의 정보들을 갖고 변환 작업을 수행한 후 실행 가능한 시스템으로 생산해 내는 것이다.[1] 본 논문에서는 MDA기반 접근 방법을 적용하여 학사관리 시스템을 설계 및 구현하고, MDA기반 접근 방법에 대한 모델링의 중요성을 강조하였다. 또한 소프트웨어를 효율적으로 개발하는 방법을 제시하여 플랫폼 독립적 모델(PIM)로 작성하고, 플랫폼 종속적 모델(PSM)을 J2EE 플랫폼 기반의 EJB(Enterprise Java Beans)로 변환하는 과정 등을 제시하였다. MDA를 지원하는 자동화 툴 및 편집기(Together Architect 2006 for Eclipse, Edit plus 2)와 데이터베이스 모델링 툴(ER/WIN 4.1)을 사용하여 시스템 설계 및 구현을 하였으며, 전통적 개발 프로세스와 MDA 기반 개발 프로세스에 대한 유효성 분석 결과를 제시하였다. The system development approach method of the new paradigm, as being standardizing MDA(Model Driven Architecture) in OMG(Object Management Group), the core technique of MDA definite technique structure for system materialization focusing on Model, is to build the design and the statement for system in PIM(Platform Independent Model), Materialization technique, and to build PSM(Platform Specific Model) adapt to materialization environment, and then to be the technique transforming into language Platform suitable to materialization environment. It includes MOF(Meta-Object Facility), UML, XMI(XML Metadata Interchange), CWM(Common Warehouse Metamodel), the core of MDA. Though these operations MDA support automatic tools product the practicable system after carrying out transform operation with the above information. In this thesis, it will be approached how to design and materialize the Bachelor management system based on MDA and the importance of modeling should be emphasized by applying to the approach method based on MDA. It should be suggested how to develop software efficiently, written it out in PIM, and suggested the process transforming PSM into EJB by J2EE Platform. The system is designed and implemented using automatic tool, edit machine(Together Architect 2006 for Eclipse, Edit plus2) supporting MDA and Database Modeling tool(ER/WIN 4.1). In conclusion, it should be suggested the efficiency analysis result for development process of traditional and based on MDA.

Exploring a model-driven architecture (MDA) approach to health care information systems development

Objective To explore the potential of the model-driven architecture (MDA) in health care information systems development. Methods An MDA is conceptualized and developed for a health clinic system to track patient information. A prototype of the MDA is implemented using an advanced MDA tool. The UML provides the underlying modeling support in the form of the class diagram. The PIM to PSM transformation rules are applied to generate the prototype application from the model. Results The result of the research is a complete MDA methodology to developing health care information systems. Additional insights gained include development of transformation rules and documentation of the challenges in the application of MDA to health care. Design guidelines for future MDA applications are described. The model has the potential for generalizability. The overall approach supports limited interoperability and portability. Conclusion The research demonstrates the applicability of the MDA approach to health care information systems development. When properly implemented, it has the potential to overcome the challenges of platform (vendor) dependency, lack of open standards, interoperability, portability, scalability, and the high cost of implementation.