System Modeling in UML with Two-Hemisphere Model Driven Approach

Abstract

-System modeling in an object-oriented manner at the initial stage of software development can be considered as a comprehensive knowledge presentation, which enables the developer practice problem domain (instead of code) to reuse and to share responsibilities between system objects at the high enough level of system abstraction. Unified Modeling Language (UML) is an industrial standard for software specification, modeling and software development in object-oriented manner. UML is not a methodology for how to model a system and to develop a software, but just a notational conventions for "drawing" of model elements. And developers have to identify model elements from problem domain based on some guidelines or their own intuition. It can arouse and frequently arise situations, where system model is not adequate to problem domain and has information loss, duplication and discrepancy. The paper offers to use two-hemisphere model driven approach for system modeling at the problem domain level to avoid problems of manual or intuitive system modeling, and illustrates how two-hemisphere model can be translated into software model expressed in UML by using rules for graph transformations. The problem domain of assigning the pupils of the driving school has been adopted for the illustration case study.

Comparison of the Two-Hemisphere Model-Driven Approach to Other Methods for Model-Driven Software Development

“…In 2008 a prototype of a tool is developed [21]. In 2010, the author in [22] conceptually describes transformation from the twohemisphere model to the UML sequence diagram, focusing on the time aspect of methods' call. During this time transformation for the generation of the UML class diagram is refined regarding different types of class relationships [22].…”

Object Interaction as a Central Component of Object-oriented System Analysis

“…And processes of process modelserve as a basis to define corresponding messages requiring to execute certain operation (to perform the process). The follow-ing approach and all the transitions are defined in details in [8], [9].…”

“…Class diagrams are investigated quite well in different researches. Author of the paper also paid attention to this and published the results in [5], [6], [7], [8], [9]. According to modeling of system's dynamic, exactly problems of its definition are the reason why MDA goals are not achieved yet [10].…”

“…The research object of the paper is UML sequence diagram. The goal of this paper is to investigate a strategy of definition of main elements of object interaction and to find an ability to base this definition on the elements of two-hemisphere model, which is already used for definition of object classes and structure of its collaboration in author's previous papers [7], [8], [9].…”

Dependencies among Architectural Views Got from Software Requirements Based on a Formal Model

“…The wide-known applications of the UML are together with software development lifecycles [25], use case driven methods [21], MDA [9], pattern based development [20], component based development [22], and conceptual modeling [26]. The current state of the art of these approaches includes those that are well known in software development industry (like in [18]), formalize the development process and problem domain, and are used in conjunction with software development tools (like in [27]).…”