![]() ![]() On the other hand, the symbols in the BPMN compress the information. In the UML activity diagram, every symbol represents one concrete and atomic information. It is caused by the complexity of the BPMN symbols. Although both models describe the same thing and use similar symbols, the models differ fundamentally. Although both models are very similar, the transformation from the BPMN to the UML-AD is not as straightforward as it seems. This is the example of the XMI representation of an UML-AD initial node (describes the same as the example of start event node in chapter 4.1): If both ways of the diagram representation are compared, it is obvious that creating an XMI profile for the BPMN similar as the XMI profile for the UML- AD, will be very useful. Since the description is based on the usage of the UML namespace, the model description is very straightforward and easy to read. This is based on their definition in the namespace. The XMI file of a UML activity diagram contains only the description of the nodes in the diagram and the way they are connected. 2.1.2 for used UML version)used to describe symbols contained in the diagram. The XMI representation of the UML-AD is defined by the OMG as a part of the UML standard (current definition can be found in ), therefore the XMI file dedicated to transport the UML diagram uses the namespace: where the version represents the number of a current UML version (e.g. Therefore, it is good reason why to improve this XMI notation in the future. On the other hand, the BPMN XMI file is illegible for humans and, moreover, the slot elements sometimes contain redundant information (the information was defined earlier or it is not necessary to define). This fact helps to create transformation rules. Following XML snippet represents basic start event node: This representation has the advantage that the connection between the symbols is mostly obvious. Attribute xmi:type refers to the UML-AD symbol which is extended and xmi:extension element and its subelements are used to define the features typical for the BPMN by referring to the profile stored in the document. Every symbol in the BPMN has a corresponding element in XMI which defines its type and attributes. In this way a new profile is defined, which is a part of the BPMN XMI document and serves as a declarative reference. This extension is made by adding new elements and attributes to the UML-AD representation. The BPMN model is described by extending UML-AD XMI representation. The BPMN representation is based on similarities between BPMN and UML-AD. Therefore, we decide to use the representation which is used in Altova UModel, so BPMN diagrams will be easy to visualize and XMI easy to generate. The BPMN has no standardized XMI representation. ![]() ![]() Therefore, the graphical layout is not universally transportable and in the transformation we will handle the diagram transfer only. The description of the graphical part is typically hidden in an XMI element extension which is defined as a container for the tool-specific data. Unfor- tunately, the description of the graphical representation of a model is not defined in the XMI standard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |