No abstract

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. KeywordsModel driven architecture, platform independent model, model transformations, two-hemisphere model, UML class diagram INTRODUCTIONOne of the latest researches goals in software engineering is to find a software development process, which would provide fast and qualitative software development. Most of currently proposed methodologies and approaches try to make the development process easier and still more qualitative. For achievement of this goal the role of explicit models becomes more and more important.

No abstract

No abstract

Obtaining of elements of UML class diagram from initial information about problem domain The Model Driven Architecture (MDA) is frequently used approach to software development. Basic conception of MDA is splitting of software development by levels of abstraction, where every level is presented with separate model - Computation Independent, Platform Independent, Platform Specific Models and code. The construction of central component of Platform Independent Model - system static structure in form of Unified Modeling Language (UML) class diagram is discussed in the paper. A set of approaches proposes the way for construction of UML class diagram. Different researchers try to find the possibility to obtain elements of class diagram in the formal way. This paper describes the method of obtaining of elements of class diagram from initial knowledge about the problem domain, which is described with interrelated business process and concept model. The proposed method defines main elements of class diagram, such as class name, class attribute, class operation, relationships among classes. Formal definition of these elements allows to avoid mistakes in the software analysis and design stage. It is very important to obtain correct model on this stage, as the design model is a base of future software.