Model Driven Architecture Research Articles

The Model Transformation for Getting a UML Class Diagram from a Topological Functioning 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.

An SOA-Based System Modeling Methodology

Many information systems employ the integrity technique to implement a service-oriented architecture (SOA). Service contracts are defined by the service-level agreement or service portfolio, and a new application will require on-demand services provided by existing systems. No previous research has considered the features of system services required for the execution of a dynamic strategy, which cannot be fulfilled by existing system services. In contrast, an SOA can support the execution of an enterprise's strategy in an environment with dynamic changes. This paper presents a proposed methodology based on business strategies to help construct a service-oriented information system, and a model-driven architecture that was used to verify this methodology.

TRANSFORMATION FOR DESIGNING DISTRIBUTED INTERNET INFORMATION SYSTEMS UNDER MODEL DRIVEN ARCHITECTURE

This article deals with the specification and transformation of distributed systems under Model Driven Architecture (MDA). It reviews basic concepts and benefits of MDA approach, its relations with traditional software development and suggests an alternative method for specification of distributed internet information systems using unified modeling language (UML) notation and transformation of these specifications into program code. Transforma-tion method enables to ease work of the system analyst when creating large and complex information systems. It allows separating full system specification into different parts and converting functions of these parts into platform dependent program code. This article also refers to a synthesis of object interaction diagrams of distributed systems mentioned before.

Comparison of Two Model Driven Architecture Approaches for Automating Business Processes, Moskitt Framework and Bizagi Process Management Suite

The Model Driven Architecture (MDA) approach to develop information systems is a model-oriented approach since it focusses on the business logic (the “what”) rather than on the specific implementation technology (the “how”). Models are the authentic protagonist of information systems development. They represent the information system developed while the implementation in a certain technology is obtained through model transformation. The business process that will be automated in both frameworks is the user access management flow that employees follow in order to gain access into systems. The same business process will be modeled in two different formalisms, UML and BPMN, as per the capabilities supported from each framework. Starting from the model the automation steps in order to have an information system which can be executed and which automates the respective process will be clarified. A comparison study in each step of the process automation for both frameworks is presented. The advantages and disadvantages of each of the approaches will be considered and also evidence which approach is more suitable in specific cases. DOI: 10.5901/mjss.2015.v6n2p615

A Natural Language Requirements Engineering Approach for MDA

A software system for any information system can be developed following a model driven paradigm, in particular MDA (Model Driven Architecture). In this way, models that represent the organizational work are used to produce models that represent the information system. Current software development methods are starting to provide guidelines for the construction of conceptual models, taking as input requirements models. In MDA the CIM (Computation Independent Model) can be used to define the business process model. Though a complete automatic construction of the CIM is not possible, we have proposed in other papers the integration of some natural language requirements models and we have defined a strategy to derive a CIM from these models. In this paper, we present an improved version of our ATL transformation that implements a strategy to obtain a UML class diagram representing a preliminary CIM from requirements models allowing traceability between the source and the target models.

ABORDAGEM DIRIGIDA AO DOMÍNIO APLICADO NA ARQUITETURA DE SISTEMAS WEB

This research proposes to specify a model based on MDA (Model Driven Architecture) for the development of Web systems. To achieve this goal, we carried out the study procedures and techniques using the MDA, agile methodologies and DDD - Domain Driven Development. This model aims optimize the software development reducing impacts, like daley’s and high costs, for the project.

Capturing simulation tool and application domain knowledge for automating simulation model creation

Model-driven architecture (MDA) is a contemporary strategy for software development using three distinct kinds of models: (1) models expressing the problem to be solved in the semantics of its domain; (2) models of the solution space in terms of hardware and software elements; and (3) models that map from the domain space to the solution space. We explore an adaptation of the MDA strategy to meet some key application challenges in creating simulation models to support system design and operating decisions. For a given simulation tool, our approach requires a single transformation model that is applicable for any domain for which the simulation tool is appropriate. For a given application domain, our approach allows an iterative development of the domain semantics. Our approach empowers the domain stakeholders with engineering tools for defining the problem to be solved and formally integrating that definition with the simulation solver. Finally, our approach captures knowledge about how to translate from the problem domain to the simulation tool so that knowledge can be taught, reused, and refined.

An MDA Method for Automatic Transformation of Models from CIM to PIM

The Model Driven Architecture (MDA) approach introduces a clear separation of the business logic from the implementation logic that's less stable. It uses the models that are more perennial than codes. It puts the models at the centre of the development of software and of the information systems. The MDA approach consists at, firstly, developing the CIM Model, secondly, obtaining the PIM model from the CIM, and finally generating the PSM model from the PIM which facilitates the generation of code for a chosen technical platform. In the literature, several works have summarized the MDA approach to the passage from PIM to PSM then from the PSM to code. Yet, very little work has contributed in the axis of the CIM to PIM transformation, and their approaches generally propose a CIM model which does not cover the different specifications of the Object Management Group (OMG) and/or the CIM to PIM transformation that they define is in the most cases manual or semi-automatic. Thus, our proposal aims at providing a solution to the problem of constructing CIM and its automatic transformation at the PIM using the QVT transformation rules. The approach proposes to represent CIM by two models: The business process model reflecting both the static and the behavioral views of the system, and the functional requirement model defined by the use case model reflecting the functional view of the system. The transformation of the CIM allows us to generate the PIM level represented by two models: The domain classes model which gives a structural view of the system at this level, and a model that describes the behavior of the system to each use case.

Foundational MDA Patterns for Service-Oriented Computing .

As the foundation of EDI, B2C and B2B, distributed comput- ing is a key enabler for today's enterprises and will become even more important with the advent of cloud computing on the one hand and an ever more agile work organization on the other hand. Whilst the rapid evolution of distributed computing technologies in the last three decades has delivered a rich set of platforms and paradigms for building robust enterprise systems, it has also left a legacy of unresolved problems includ- ing fundamental inconsistencies between the concepts of the two leading distributed computing paradigms, i.e., distributed object computing and service-oriented architecture. Equally important, there is a growing need to lower the complexities and barriers involved in developing client appli- cations, which range from large scale business applications and business processes to laptop programs and small apps on mobile devices. In this article, we present a unified conceptual framework for service-oriented computing based on the proven MDA (Model Driven Architecture) ter- minology stack. With the conceptual framework we consolidate, and give semantics to, core concepts of service-oriented computing and provide a set of foundational model transformation patterns that map between the presented concepts and further clarify practical service-oriented comput- ing scenarios. Finally, we show how the developed framework perfectly fits to the OSM (Orthographical Software Modeling) approach.

A NATURAL LANGUAGE REQUIREMENTS ENGINEERING APPROACH FOR MDA

A software system for any information system can be developed following a model driven paradigm, in particular MDA (Model Driven Architecture). In this way, models that represent the organizational work are used to produce models that represent the information system. Current software development methods are starting to provide guidelines for the construction of conceptual models, taking as input requirements models. In MDA the CIM (Computation Independent Model) can be used to define the business process model. Though a complete automatic construction of the CIM is not possible, we have proposed in other papers the integration of some natural language requirements models and we have defined a strategy to derive a CIM from these models. In this paper, we present an improved version of our ATL transformation that implements a strategy to obtain a UML class diagram representing a preliminary CIM from requirements models allowing traceability between the source and the target models.

Towards a Monitoring Framework for the Automatic Integration of the Access Control Policies for Web Services

Cloud computing is an emerging model of business computing that can be used to maintain configurable resources such as processors, networks, storage, operating systems, databases, and servers. Service oriented Architecture (SoA) is one of most successful paradigms deployed over the Cloud; is a layered architecture to organize software resources as services and to facilitate their deployment, discovery, and combination to produce new services. The coordination of innovations carried out between these services is a key challenge of SoA, as any failings in such services could result in a lack of availability, which may violate Service Level Agreements, leading to financial penalties or customer dissatisfaction. A service known as the Protocol service can be introduced and integrated within a system to coordinate innovations. This service may then be linked with a service called the Access Control Policies (AC_Policies) service, which identifies permissions of invocation of the Protocol service. Next, a real-time Business Activity Monitoring (BAM ) dashboard is automatically generated to supervise the process of assigning the Access Control Policies, along with the status of the executions of Web services. This approach is achieved by harnessing the capability of the Model-Driven Architecture (MDA) to facilitate the automatic generation of services. As a proof of concept, this approach is implemented as a plugin.

Constructing a Web System Presentation Layer Framework Based on MDA

MDA(Model Driven Architecture)[1] is model-centric software development methodology. Comparing to traditional code-centric method, MDA is closer to real applications, and it owns a higher level of abstraction. It has become an effective way to produce large scale software in heterogeneous environment, and it is widely used to develop web-based complex information systems [2]. Our paper applies MDA approach to design web system representation layer framework with instances, and extend UML model by MOF(Meta-Object Facility). We’ve also defined transform rules and realized the conversion from UML model to Web model. Our framework helps minimize the application code, reduces the dependence of the Servlet API, provides extensible interface, thus improve the efficiency of system development and maintenance.

Automated transformations from UML behavior models to contracts

In model driven architecture (MDA), system requirements are first captured by UML (unified modeling language) use cases with sequence diagrams to describe their intended use and implemented by classes of objected-oriented languages in the subsequent design stages. It is important that the dynamic behavior specified by the sequence diagrams is in full compliance with the implementation classes. This paper proposes an automatic approach and tool support for generating class contracts, which define a precondition and a postcondition for each operation of the class. The former serves as a guard to ensure invocations of the operations respect the semantics introduced by the sequence diagrams, and the latter places the system in a legal state to facilitate the succeeding operation calls. The contracts can be easily mapped to code of an object-oriented language such as Java. Thus, the approach helps to bridge the gap between the requirements and design stages of system development process. We use our model transformation tool to first generate a UML protocol state machine from the sequence diagrams, and then derive the contracts for a controller class. The transformations take into account the concurrency and critical constructs of the respective UML diagrams.

Introduction to the Integrated Domain Modeling Toolset

Abstract This paper describes the Integrated Domain Modeling approach and introduces the supporting toolset as a solution to the complex domain-modeling task. This approach integrates artificial intelligence (AI) and system analysis by exploiting ontology, natural language processing (NLP), use cases and model-driven architecture (MDA) for knowledge engineering and domain modeling. The IDM toolset provides the opportunity to automatically generate the initial AS-IS model from the formally defined domain knowledge. In this paper, we describe in detail the scope, architecture and implementation of the toolset.

Relationships between UML Sequence Diagrams and the Topological Functioning Model for Backward Transformation

Abstract The software system needs to be analyzed and designed before the program code is written. A Computation Independent Model (CIM) and a Platform Independent Model/ Platform Specific Model (PIM/PSM) from Model-Driven Architecture (MDA) will be partially considered in this paper. A Topological Functioning Model (TFM) will be considered as a formal CIM, and UML sequence diagrams - as a behavioral PIM/PSM of the software system. The paper presents a short overview of the TFM and sequence diagrams with their constructs, as well as the example of transformation from the sequence diagrams to the TFM.

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.

Bizagi Process Management Suite as an Application of the Model Driven Architecture Approach for Developing Information Systems

Bizagi business process management is a suite for software development and process automation that implements the Model Driven Architecture (MDA) principles. The capabilities of the suite will be presented through a real case information system developed that represents a business process in a modern corporation; the user access management flow that employees follow in order to gain access into systems. The MDA approach to develop information systems is considered as the biggest shift since the move from Assembler to the first high level programming languages. At the heart of the MDA approach are models which represent the information system developed while the implementation in a certain technology is obtained through model transformation. Following the MDA paradigm, in Bizagi the starting point is the model of the business process. The model is enriched throughout the steps of process automation in order to produce an information system which can be immediately executed. As result an information system which automates the business process is obtained without the need to write any code. Bizagi business process management suite fully implements the MDA approach and principles in building process applications. DOI: 10.5901/ajis.2014.v3n6p475

Využití konceptu MDA ve vývoji strukturální oblasti prezentační vrstvy

This paper presents an approach for developing the presentation layer of software applications. The approach is based on the concept of the Model Driven Architecture (MDA) and uses a UML – based model of graphical user interfaces, which is created according to rules defined in a meta – model. The meta – model is not oriented to a particular platform, thus all designed models can be created independently of the programming language and widget library. This platform independent UML based model can be transformed into source – code for an arbitrary programming language and can be used in a software development process.The meta – model of our approach is an extension of the common UML and provides support for modeling the presentation layer. The meta – model thus fills a gap that exists in modeling three – laye­red software applications, beside the application and the data layer. By providing this possibility for modeling the presentation layer, we can crucially impact current approaches to the development of three layered software applications. All model artifacts contain essential information about the gra­phi­cal user interface and can be used for a code generation. Since the UML is widely used by analysts, they can produce models which de-facto represent source code and thus they reduce the workload for programmers, who create source code by some traditional approaches. Our model – based approach also strictly separates the appearance and the structure of graphical user – interfaces and both of them are developed separately, which brings higher modularity of software.In this paper, we demonstrate our development approach by focusing on the structure of graphical user interfaces. Our approach is influenced by the concept of Model Driven Architecture and we deal with all related issues, such as meta – model, user models, model transformations and source – code generation. For evaluating our approach, we designed and developed a software framework, we integrated it into a generic modeling tool, and used approach principles during the development of a module of an information system.

English

Containers transportation involves various intermediate supply-chain actors. These containers are subject to myriad risks that can occur at any moment. In addition, the absence of a specialized stakeholder for securing containers flow and the lack of communication among actors impedes identifying responsibilities when an adverse event arises. For this purpose, we advocate the use of traceability system to enhance containers transportation security. This objective is achieved through enhancing systems interoperability to collect necessary information for identifying risks. Thus, we opted for urbanizing a traceability system to meet the new requirements related to risk management. In this paper, we propose the use of web-services to overcome the problems related to the heterogeneity of systems used by supply-chain stakeholders. Thus, we proposed a development process based on model driven architecture (MDA) to automate the code generation of these web-services. Moreover, we used the concept of intelligent product (IP) to propose an intelligent container able to communicate with external systems and to manage information related to its traceability. This solution is validated by a real case study. Key words: Intelligent product (IP), model driven architecture (MDA), service oriented architecture (SOA), business process (BP), traceability.

Model-Driven Transformation for GWT with Approach by Modeling: from UML Model to MVP Web Applications

The continuing evolution of business needs and technology makes Web applications more demanding in terms of development, usability and interactivity of their user interfaces. To cope with this complexity, several frameworks have emerged and a new type of Web applications called RIA (Rich Internet Applications) has recently appeared providing richer and more efficient graphical components similar to desktop applications. Given this diversity of solutions, the generation of a code based on UML models has become important. This paper presents the application of the MDA (Model Driven Architecture) to generate, from the UML model, the Code following the MVP pattern (Model-View-Presenter) for a RIA using the standard MOF 2.0 QVT (Meta-Object Facility 2.0 Query-View-Transformation) as a transformation language. We adopt GWT (Google web Toolkit) for creating a target meta-model to generate an entire GWT-based web application. The transformation rules defined in this paper can generate, from the class diagram, an XML file containing the Views, the Models, and the Presenter. This file can be used to generate the necessary code of a RIA.