Oksana Nikiforova

Development of the Tool for Generation of UML Class Diagram from Two-Hemisphere Model

Nowadays, the research on the Model Driven Architecture is still in progress. One of the existing problems in this area is transformation between models of the Model Driven Architecture. This paper discusses the transformation from Platform Independent Model, received from Computation Independent Model, to the one, ready for generation of Platform Specific Model. To implement this transformation, two-hemisphere model driven approach to system modeling is chosen. The class diagram in UML notation is defined as transformation result. The paper discusses the transformation into class diagram, and the possibility of automation of such transformation. In order to research automation possibilities, custom tool is designed and implemented. This tool allows generating elements of class diagram based on provided transformations. It is applied on three examples of initial model, represented in different notations and different problem areas. These experiments proof that examined transformations are independent from problem domain and notation which expresses initial knowledge.

Open work of two-hemisphere model transformation definition into UML class diagram in the context of MDA

Model Driven Architecture (MDA) is based on models and distinguish between a system functionality specification and this specification realization on a given technological platform. MDA consists of four models: CIM (Computation Independent Model), PIM (Platform Independent Model), PSM (Platform Specific Model) and code model, all these are parts of the MDA transformation line: CIM→PIM→PSM→code. A PIM model has to be created using a language which is able to describe a system from various points of view, system behavior, systems business objects, system actors, system use cases and so on. Current paper discusses the application of two-hemisphere model for construction of UML class diagram as a part of PIM. Several solutions for determination of elements of class diagram from two-hemisphere model are currently researched and described in the paper. As well as application of the transformations by example of insurance problem domain are presented in the paper.

Foundations on Generation of Relationships Between Classes Based on Initial Business Knowledge

This chapter focuses on the development of the main component of platform independent model (PIM) of Model Driven Architecture, e.g., class diagram defined in Unified Modeling Language (UML), which has necessary details for transformation into platform specific model (PSM). It is important to formulate core principles of development of well-structured class diagram at a conceptual level, using knowledge of the problem domain, which consists of two interrelated models of system aspects – business processes and concept presentation. Definition of relationships of classes is important for PSM generation; therefore, the research on how it could be defined is performed. The hypothesis that it is possible to derive a class structure from initial business information is adduced. Information about the problem domain is presented in the form of two-hemisphere model that describes two interrelated parts of the most important aspects of a system, namely business process and concept models. These models serve as a source model for class diagram receiving. Capacity for the class diagram generation, based on the two-hemisphere model, is represented by a collection of graph transformations and illustrated with examples, where definition of different kinds of relationships (namely aggregation, dependency, generalization) is displayed.

Adapting Software Development Process towards the Model Driven Architecture

Model driven architecture (MDA) is increasingly gaining the attention of both research communities and industry. MDA is a model-oriented software development paradigm, which can be applied to any software development methodology. MDA gives no guidelines in terms of the processes such as activities and phases, roles and responsibilities that are involved in the software development process. When an organization considers applying MDA-based software development process, it will face the lack of methodological guidelines. The aim of this paper is to customize typical heavyweight software development methodology (based on most widely used methodologies - rational unified process and Microsoft solutions framework) according to the MDA software development framework.

Discussing the Difference between Model Driven Architecture and Model Driven Development in the Context of Supporting Tools

The most current trends in the evolution of software development process are closely related with the increasing complexity of software systems. This motivates software engineers and system developers to find an alternative solution for software system design and development. In this case, the manner offered by OMG’s initiative, the Model Driven Architecture namely, represents a model-driven approach to software development. It also considers the further evolution of CASE tools, bringing their functionality to the next level. This paper investigates the variety of the CASE tools developed under an impact of MDA growing progress. The differences between Model Driven Architecture and Model Driven Development in the context of automatic capabilities for software development are also discussed in the paper. The example of possibility to define a set of tools proposed as a tool chain for development of software systems under the framework of MDA, the projection of two-hemisphere approach for object-oriented software development into authors’ developed component model of MDA is offered in the paper.

Application of BPMN instead of GRAPES for two-hemisphere model driven approach

Models and model transformations are defined as primary artifacts in OMGs Model Driven Architecture (MDA). The main idea of MDA is to sepa- rate the formal representation of the system, preserving the highest possible level of abstraction in the form of system model, as well as to transform this model to the level required for system implementation. Two-hemisphere model represents the problem domain from the business perspective. It uses two inter- related system models—a business process model and a concept model, expressed in GRAPES notation. The main emphasis of this research is concerned with applying the OMGs notation to represent the business hemisphere in Business Process Modeling Notation (BPMN). This paper comprises the general issues of the research, difference between the notations, as well as the results on generated set of elements of UML class diagram.

Several facilities of class diagram generation from two-hemisphere model in the framework of MDA

In Object Management Group model driven architecture models are the primary artifacts during software development, which are presented at the different levels of abstraction from programming details. Class diagram is the most often used model for visual representation of static aspects of software system, but still the formal generation of class diagram from problem domain is under investigation. The paper describes principles of development of class diagram at the conceptual level by using problem domain knowledge presented in the form of two-hemisphere model. Problem domain is presented as two interrelated models of the most important aspects of a system, namely, business process and concept models. Abilities of class diagram generation from two-hemisphere model are presented as a collection of graph transformations and are demonstrated by practical example for abstract problem domain.

UML Sequence Diagram

Abstract Modeling of the object interaction is one of the core tasks during system analysis and design, because it gives developer an ability to define responsibilities of class objects and to sketch general architecture of software components. In this task an ability of automatic generation of the UML sequence diagram becomes one of the most important activities. The twohemisphere model contains enough information to define operations to perform by classes and therefore is investigated in this paper in the context of the UML sequence diagram generation.

Two-hemisphere driven approach: application for knowledge modeling

Two-hemisphere model driven (2HMD) approach assumes modeling and use of procedural and conceptual knowledge on an equal and related basis. This differentiates 2HMD approach from pure procedural, pure conceptual, and object oriented approaches. The approach may be applied in the context of modeling of a particular business domain as well as in the context of modeling the knowledge about the domain. In educational domain there are twofold application possibilities of 2HMD approach; firstly, in terms of modeling of knowledge to be taught and, secondly, in terms of modeling of educational process aimed at providing a particular knowledge reflected by the two-hemisphere model. Modeling of educational process by 2HMD approach gives an opportunity to transparently analyze and compare knowledge to be provided and knowledge actually provided by courses belonging to a particular study program, and, thus, to identify and fill the gaps between desirable and actual knowledge content

Enabling Problem Domain Knowledge Transformation during Object Oriented Software Development

Nowadays one the most desirable characteristics of software development process is a high speed of development. However, in many cases the speed of software development is hindered by problems of knowledge acquisition and transformation. Sometimes software developers focus on their tacit knowledge and do not use proper knowledge acquisition and representation techniques for problem domain and requirements description. In that case developers take a known risk to fail with a final product, yet they hasten the process of software development. However, such a risk shall be avoided in large, complex, and expensive software projects.