Semantic Model Driven Architecture Based Method for Enterprise Application Development

2011 ◽

pp. 315-339

Author(s):

László Gönczy ◽

Dániel Varró

Keyword(s):

Architectural Design ◽

Model Transformations ◽

Functional Requirements ◽

Application Development ◽

Tool Chain ◽

Model Driven ◽

Enterprise Application ◽

Functional Aspects ◽

Early Validation ◽

Service Oriented

As the use of SOA became a mainstream in enterprise application development, there is a growing need for designing non-functional aspects of service integration at the architectural level, instead of creating only technology specific assets (configuration descriptors). This architectural design supports flexibility and early validation of requirements. This chapter presents a model-driven method supporting the automated deployment of service configurations. This deployment technique is supported by an extensible tool chain where (i) service models are captured by a service-oriented extension of UML enabling to capture non-functional requirements, and (ii) configuration descriptors for the target deployment platform are derived by automated model transformations within the VIATRA2 framework.

Download Full-text

A Model Driven Architecture for Enterprise Application Integration

Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06) ◽

10.1109/hicss.2006.18 ◽

2006 ◽

Cited By ~ 1

Keyword(s):

Enterprise Application Integration ◽

Application Integration ◽

Model Driven Architecture ◽

Model Driven ◽

Enterprise Application

Download Full-text

Model Driven Architecture (MDA)

Advances in Computer and Electrical Engineering - Model Driven Architecture for Reverse Engineering Technologies ◽

10.4018/978-1-61520-649-0.ch002 ◽

2010 ◽

pp. 15-33 ◽

Cited By ~ 1

Author(s):

Liliana María Favre

Keyword(s):

Unified Modeling Language ◽

Enterprise Application Integration ◽

System Specification ◽

Model Driven Architecture ◽

Unified Modeling ◽

Model Driven ◽

Software Applications ◽

Enterprise Application ◽

Architectural Framework ◽

Requirement Specifications

The architecture of a system is a specification of software components, interrelationships, and rules for component interactions and evolution over time. In 2001 OMG, adopted an architecture standard, the Model Driven Architecture (MDA). MDA is an architectural framework for improving portability, interoperability and reusability through separation of concerns (MDA, 2003) (MDA, 2005). It is not itself a technology specification but it represents an evolving plan to achieve cohesive model-driven technology specifications. MDA is built on OMG standards including the Unified Modeling Language (UML), the XML Metadata Interchange (XMI) (XMI, 2007) and CORBA (CORBA, 1992) (CORBA, 2002) a major middleware standard. MDA is model-driven because it uses models to direct the complete lifecycle of a system. All artifacts such as requirement specifications, architecture descriptions, design descriptions and code, are regarded as models. MDA provides an approach for specifying a system independently of the platforms that it supports, specifying platforms, selecting a particular platform for the system, and transforming the system specification into one implementation for the selected particular platform. Why MDA? OMG has focused on the creation of open specifications to encourage application interoperability. It was defined to solve enterprise application integration. A middleware describes a piece of software that connects two or more software applications, allowing them to exchange data. To achieve this, it must be implemented for all different languages and platforms that need linking.

Download Full-text

MoDAr-WA: Tool Support to Automate an MDA Approach for MVC Web Application

Computers ◽

10.3390/computers8040089 ◽

2019 ◽

Vol 8 (4) ◽

pp. 89 ◽

Cited By ~ 1

Author(s):

Imane Essebaa ◽

Salima Chantit ◽

Mohammed Ramdani

Keyword(s):

Web Application ◽

Source Code ◽

Specific Model ◽

Model Transformations ◽

Tool Support ◽

Model Driven Architecture ◽

Application Development ◽

Model Driven ◽

Constraints Model ◽

Independent Model

Model-driven engineering (MDE) uses models during the application development process. Thus, the MDE is particularly based on model-driven architecture (MDA), which is one of the important variants of the Object Management Group (OMG). MDA aims to generate source code from abstract models through several model transformations between, and inside the different MDA levels: computation independent model (CIM), platform independent model (PIM), and platform specific model (PSM) before code. In this context, several methods and tools were proposed in the literature and in the industry that aim to automatically generate the source code from the MDA levels. However, researchers still meet many constraints—model specifications, transformation automation, and level traceability. In this paper, we present a tool support, the model-driven architecture for web application (MoDAr-WA), that implements our proposed approach, aiming to automate transformations from the highest MDA level (CIM) to the lowest one (code) to ensure traceability. This paper is a continuity of our previous works, where we automate transformation from the CIM level to the PIM level. For this aim, we present a set of meta-models, QVT and Acceleo transformations, as well as the tools used to develop our Eclipse plug-in, MoDAr-WA. In particular, we used QVT rules for transformations between models and Acceleo for generating code from models. Finally, we use MoDAr-WA to apply the proposed approach to the MusicStore system case study and compare the generated code from CIM to the original application code.

Download Full-text

Web Application Development Based on MDA Project-Driven Mode

Advanced Materials Research ◽

10.4028/www.scientific.net/amr.971-973.1862 ◽

2014 ◽

Vol 971-973 ◽

pp. 1862-1865

Author(s):

Hai Peng Shi

Keyword(s):

Web Application ◽

Model Driven Architecture ◽

Application Development ◽

Teaching Mode ◽

Model Driven ◽

Teaching Plan ◽

Quality Of Teaching ◽

Web Application Development

In the paper, the MDA (Model Driven Architecture) are brought into J2EE web application development based on project-driven mode and the teaching plan is proposed. First the current project-driven teaching mode in our institute is presented and the idea behind the MDA is introduced briefly, and then some suggestions on the J2EE MDA project-driven are given. Practice shows that the teaching mode can not only improve the efficiency of development and the quality of system, but also bring students the sense of achievement, and arouse their enthusiasm and initiatives; thereby the quality of teaching is greatly improved.

Download Full-text

Use of Business Models within Model Driven Architecture

Scientific Journal of Riga Technical University Computer Sciences ◽

10.2478/v10143-009-0010-1 ◽

2009 ◽

Vol 38 (38) ◽

pp. 119-130

Author(s):

Erika Asnina

Keyword(s):

Business Models ◽

Business Processes ◽

Use Cases ◽

Separation Of Concerns ◽

Model Driven Architecture ◽

Model Driven ◽

Development Processes ◽

Business Requirements ◽

Complex Computer ◽

Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

Download Full-text