Modeling Principles of the Sequence Diagram and its Application in MDA Software Paradigm

Abstract. The sequence diagram can be used to design object-oriented software; however, its modeling principles are lack of research. In this paper, its application in software design was studied, and its inherent linkage with object-oriented programming was discussed, and the interactive mechanism among its elements was explored. The modeling principles for it were proposed; and its application in Model Driven Architecture (MDA) software paradigm was analyzed; and finally the model represented with it, especially the transformation and traceability of models in MDA software paradigm were analyzed. This research is useful to optimize software modeling and to automate model transformation in MDA software paradigm

Modeling Principles of the Sequence Diagram and its Application in MDA Software Paradigm

Abstract. The sequence diagram can be used to design object-oriented software; however, its modeling principles are lack of research. In this paper, its application in software design was studied, and its inherent linkage with object-oriented programming was discussed, and the interactive mechanism among its elements was explored. The modeling principles for it were proposed; and its application in Model Driven Architecture (MDA) software paradigm was analyzed; and finally the model represented with it, especially the transformation and traceability of models in MDA software paradigm were analyzed. This research is useful to optimize software modeling and to automate model transformation in MDA software paradigm

Model driven architecture for modeling of logical security based on RBAC approach

This paper presents an approach of role-based access control (RBAC) for information systems with the use of MDA (Model Driven Architecture). The main purpose is to join the concepts of MDA approach with the concepts of access control models, in particular with the concepts of access control based on roles and on usage concept. To reach this objectives the appropriate solution was created to model the extended RBAC model and URBAC model with the use of concepts and tools of software engineering, in particular MDA methodology and UML (Unified Modeling Language). The presented approach was developed for role engineering in the aspects of logical security of information systems

The Future of Modeling in Material Handling Systems

Today, when we talk about “modeling” in the context of material handling systems, invariably we are referring to a mathematical or computational model for analyzing some aspect of the system, such as its throughput rate, response time, cost of ownership, required storage capacity, etc. Creating these kinds of models requires considerable knowledge in at least two domains the material handling system domain, and the analysis methodology domain—and considerable skill in the “art of modeling” in order to express the former in the terms of the latter. The results can be somewhat ad hoc—e.g., two different modelers are likely to create two somewhat different simulation models of exactly the same material handling system. In the past, the situation in software development was very similar, with individual programming experts idiosyncratically driving software development. Over the past twenty years, however, computer scientists and software engineers have created a radically different approach to the process of software “modeling” called Model Driven Architecture, or MDA, that is used to create software for standard applications. The thesis of this paper is that MDA can be adapted to the kind of modeling done to support design and operational decision making in material handling systems. The paper describes MDA technologies in the context of material handling system modeling, and explains how adapting this approach to our context will transform the way we do research and the way material handling systems are analyzed and designed in practice

A model driven approach for software systems reliability

The reliability assurance of software systems from design to deployment level through transformation techniques and model driven approach, is described. Once the reliability mechanisms provided by current component-based development architectures (CBDA) are designed in a platform-independent way, platform-based design and implementation models must be extended. Current CBDAs, such as Enterprise Java Beans, address a considerable range of features to support system reliability. The evaluation aims to test maturity of the approach, its applicability, and the effectiveness of reliability models. The techniques such as process algebras are generally considered time consuming, in regard to software development

MDA-based ATL transformation to generate MVC 2 web models

Development and maintenance of Web application is still a complex and error-prone process. We need integrated techniques and tool support for automated generation of Web systems and a ready prescription for easy maintenance. The MDA approach proposes an architecture taking into account the development and maintenance of large and complex software. In this paper, we apply MDA approach for generating PSM from UML design to MVC 2Web implementation. That is why we have developed two meta-models handling UML class diagrams and MVC 2 Web applications, then we have to set up transformation rules. These last are expressed in ATL language. To specify the transformation rules (especially CRUD methods) we used a UML profiles. To clearly illustrate the result generated by this transformation, we converted the XMI file generated in an EMF (Eclipse Modeling Framework) model.Comment: International Journal of Computer Science & Information Technology-201

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis