Two-Hemisphere Model Driven Approach: Engineering Based Software Development

Abstract

Several model driven approaches are currently used and developed, namely, generic model driven approaches, agile model driven approaches, business process model driven approaches, etc. This paper proposes the model driven approach, which is based on a two-hemisphere model. The twohemisphere model integrates application and problem domain issues. The model utilizes automatic model transformations, but in the same time allows room for input of tacit knowledge. It is a practice-oriented approach which ties together methods of business process modeling, object oriented, and model transformation approaches in order to support cognitive needs of requirements holders and object oriented software developers, and provide framework for explicit and transparent representation of mutually related business and software development knowledge. It utilizes tacit knowledge of stakeholders (including software designers), but in the same time reflects this knowledge in explicit and automatically reconfigurable models that form the basis for automatic code generation.

System Modeling in UML with Two-Hemisphere Model Driven Approach

“…Whereas UML sequence is stated as a one of ambiguous UML diagrams [9], with the implicit and informal semantic that designers can give to basic sequence diagram as a result of this conflict [10] - [12]. Two-hemisphere model [2] contains information about business processes and concepts and has already been used for representation of object interaction with UML communication diagram in [6], where only static view of the system is investigated and an ordering of message sending and receiving is missed. Now the author tries also to find dependency between elements of twohemisphere model and elements of UML sequence diagram, especially in its timing aspect.…”

“…The two-hemisphere model driven approach [2] may be considered as a version of business process model driven approach. The approach addresses the following issues currently relevant in software development:…”

“…Two-hemisphere model driven (2HMD) approach [2] proposes the application of business process modeling and concept modeling to represent systems in the platform independent manner and describes how to transform business process models into UML models. For the first time the strategy was proposed in [18], where the general framework for object-oriented software development was presented and the idea of the usage of two interrelated models for software system development was stated and discussed.…”

“…1), which reflects functional perspectives of the problem and application domains, is optional, however, it must reflect business processes and information flows [2]. And information flows have to be typed by corresponding concepts in the concept model (graph G2 in Fig.…”

“…The author illustrates the process presenting firstly a two-hemisphere model [2] for a business domain and then investigates construction of diagrams of Unified Modeling Language (UML) [3], which is a standard for object-oriented modeling of the system [4].…”