Model Driven Architecture Methodology Research Articles

E-Learning Platform Development using A Model Driven Methodology Approach

These days, new advances and stages are developing and evolving continually, which suggests a high exertion for creating of complex frameworks, for example, E-learning stage. This circumstance produces distinctive issues identified with compactness, reusability, versatility, incorporation and interoperability. The Object Management Group (OMG) proposes the Model Driven Architecture (MDA), which enhances mobility of uses by permitting the same model to be acknowledged on various stages. Such MDA characterizes a structural engineering focused around platform independent models (PIM) and platform specific models (PSM). The part approach means to outline and create frameworks from pre-assembled segments, predesigned and pretested, to be reused in different applications, which would encourage application's support and development, would advance flexibility and configurability with a specific end goal to create new peculiarities. In this work we introduce LMSGENERATOR, a multi-target Learning administration framework generator with a model-driven procedure focused around MDA methodology coupled with part approach. Taking into account generative programming, from client determinations (abstract models) and the fancied advances, programming blocks will be created and amassed to deliver a complete arrangement adjusted to zone and clients' necessities. This paper concentrates on the change guidelines actualized in the LMSGENERATOR centers .Also; it introduces a careful investigation to delineate this proposal.

Incremental Synchronization of Organizational Models, Requirements Models and Object-oriented Software Design Models

Abstract The model synchronization between analysis and design artifacts in most cases is still a manual and error-prone process. With the arising of Model-Driven Architecture methodology, automatic transformation between models is mostly possible and can be defined using graph transformation language. Hence models, their corresponding meta-models and model transformation code now become first-class artifacts in software development. Existing model-driven software design derivation approaches usually lack support of bidirectional incremental synchronization between source and target models. Moreover, proposing the full automatic software design derivation, most approaches require some kind of specification on design decision either in a source model or in a transformation definition. The specification in a source model creates a problem of mixture of several concerns in one artifact. The specification in a transformation definition creates a problem of overcomplicated transformations using the languages that were not designed for modeling purpose, making these definitions very hard to comprehend and reuse. This paper argues that artifacts of organizational models, requirements models and software design contain related information that is specified by different means and can be synchronized using incremental bidirectional approach. However, other information that is specific for each artifact should be specified manually in each of the corresponding models.

End to End Development Engineering

Raising software abstraction and re-use levels are key success factors for producing quality software products. Model-driven architecture (MDA) is an OMG initiative following this trend by mapping a conceptual model of application specified in platform independent model (PIM), to one or more platform specific models (PSM) automatically. Because there is little previous work tackling the development problem from specification through to implementation, this paper proposes End to End Development engineering (E2EDE) method using MDA methodology. E2EDE is intended to fill the mapping gap between PIM and PSM in MDA. The notion of variability is utilized from software product line and used to model design decisions in PSM. PIM is equipped with Nonfunctional requirements which borrowed from Design pattern to inform design decisions; thereby guiding the mapping process. In addition we have developed a strategic PSM for messaging systems can be configured to produce different applications such as the helpdesk system which is used as a case study.

Research on Dynamic Reconfigurable Manufacturing Process Framework Based on MDA

With the characteristic analysis of manufacturing process in various manufacture enterprises, Model Driven Architecture methodology is applied to construct dynamic reconfigurable manufacturing process model, which can solve the problems of portability, information integration, and interoperability effectively. A dynamic reconfigurable modeling process framework based on model driven Architecture is introduced for manufacture enterprises in this paper. It separates the manufacturing system functionality specification from its implementation on any specific technology platform, and makes the system reconfigurate the manufacturing progress through the transformation of models and transmission of information. At last, the integrated system was applied to a discreet manufacturing process and the application result proves that the system is practical and effective.

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.