Research of Operation Semantic and PI Transformation Based on UML Sequence Diagrams. Yao Wen Xia, Sai Dong Lv and Dong Xia Liu, 2017. Conclusion: This study presents a UML sequence diagram is decomposed into basic constituent elements and the combination of several combinations of fragments, the basic constituent elements are mapped to the corresponding components of PI-calculus, operational semantics is given a combination of fragments and then converted to PI calculus. So, from the UML sequence diagrams of XMI file, extract the key data, structure information, including the static structure and dynamic behavior, the assembly way, need to a few key XMI file labels for data mining. Refers to the "constant" parts: Basic composition elements of UML sequence diagrams, such as classes, objects, messages, objects and the relationship between part of "change" refers to that the combination of the basic composition elements assembled segment, such as the "loop", "break", "Alt", "par" and "opt'', etc. Results: The UML sequence diagrams have "The same" part, there are also a part of the "change". Materials and Methods: In this study, the UML sequence diagram is decomposed into the basic composition elements and the combination of several segments of combination, the basic composition elements are mapped to the corresponding components in the PI calculus and combination fragment is given operational semantics and then converted to PI calculus. the fragment can have only one thread executing it at once.Background: The UML sequence diagram is a metamodel, didnt have the precise formal semantics, system design and development personnel cannot be observed system dynamic performance and cant realize system automatic reasoning and proof: On the other hand, in a state diagram and sequence diagram in UML, different sides of the same system, semantic inconsistencies may occur, because do not have form semantics, UML diagrams so unable to detect different types of conflict between the semantics of the UML subgraph. Equivalent to an alt with only one trace.ĭefines that the calls within the fragment run in parallel.ĭefines that the calls within the fragment run in a loop.ĭefines that the calls within the fragment reside in a critical section, i.e. ĭefines condition to a single call - the call will execute only if the supplied condition is true. altĭivides fragment into groups and defines condition for each group - only the one whose condition is true will execute. The following table provides guidance on the most useful operators, and their corresponding descriptions. For instance, in order to define that a call will execute only if a certain condition is true – we delimit the call with a fragment and use the operator ‘Opt’ to specify the condition.
Interaction Operators (shown below) are used to characterize the fragment. The latter calls can be partitioned to groups (combined fragment) to show according to which condition each group will execute. With fragments we can delimit set of calls to show that they 1) execute only if a given condition is true 2) execute in a loop 3) run in parallel 4) reside within a critical section 5)etc. Using Interaction Frames (Combined Fragment)Īnother way of presenting control logic is using fragments (a.k.a interaction frames) together with Interaction Operators. The sequence bellow shows CarsManager that iterate though collection of Cars and execute a wash on each Car, which in turn delegate to the appropriate strategy according to the requested technique. Indeed, the activity diagram is more appropriate to model control logic that involves conditions, loop etc, but in practice, most developers prefer to stick with the sequence diagram to show how objects interact together with the control logic involved.Ī simple way of presenting conditions and loops is using simple notes. A common issue with sequence diagrams is how to show conditions and iterations.
0 kommentar(er)
