METHOD OF BEHAVIORAL SOFTWARE MODELS SYNCHRONIZATION

A method of behavioral software models synchronization is represented in this paper. Implementing this method behavioral software models, which are changed after communication with customer, are synchronized with other software models that are represented as UML diagrams. Method of behavioral software artifacts synchronization makes the Model-Driven Development (MDD) approach more effective. For synchronization of different behavioral software models, transformation approach in the area of Model-Driven Architecture (MDA) is proposed. Synchronization operation is executed using analytical representation of initial and resulting models. Initial behavioral software model is represented by UML Use Case Diagram. Resulting behavioral software model is represented as UML Collaboration Diagram. Analytical representation of UML Use Case diagram allows considering data flows. For this representation set-theory tool operations are used. As a Collaboration Diagram usually contains more information in comparison with Use Case one, method defines two types of Use Case diagram fragments. From the beginning Use Case diagram fragments that can be transformed directly to resulting diagram constituents are considered. Then the rest of Use Case diagram fragments are processed to represents rules of placement Collaboration Diagram messages. These rules help to designate data flows, represented in Collaboration Diagram, more accuracy. Method, proposed in this article, can be used both separately and be a part of more complex transformation technics, methods and frameworks solving different tasks in MDA sphere. Also the example of proposed method realization for solving task of Vector hodograph of density lying function (VHDLF) is represented. A process of designing Collaboration Diagram, considering Use Case diagram and ontology knowledge analysis is represented. The constituents of Collaboration Diagram, which are designed using different sources, namely Use Case diagram, ontology knowledge and requirements specification are defined.