Académique Documents
Professionnel Documents
Culture Documents
It is possible to organize sequence diagrams into control flow to indicate how they fit together. Interaction diagram combining the power of sequence diagrams and activity diagram together. It can be used to describe an overview of a complex system by embedding of Object Notes of Activity Diagram, inline interaction or InteractionOcurrences inside a control flow structure. Interaction Overview Diagram provides high level structuring mechanism for sequence diagrams. As Interaction Overview Diagram is a special kind of Activity Diagram, you can use the control flow constructs such as decision, merge, fork, join and as well as the looping nodes, as the way you use it in an activity diagram. A typical example for using Interaction Overview Diagram is to model how the different scenarios of a use case are realized together.
Inline Interaction
An Interaction Overview Diagram of any kind may appear inline as an ActivityInvocation. The inline Interaction diagrams may be either anonymous (as here) or named.
InteractionOccurrence
ActivityInvocation in the form of InteractionOccurrence. You may choose to abstract the view of an InteractionOccurrence into a separate sub-diagram (sequence diagram) with the name of the Interaction referred by the occurrence.
Frame
The notation shows a rectangular frame around the diagram with a name in a compartment in the upper left corner.
Figure 3 - Frame
these interactions occur. Let me use a flattening sequence diagram to represent a semantically equivalent interaction overview diagram for illuminating the concepts.
Page 2 of 4
Each of the InteractionOccurrences can be represented by a detailed sub-diagram (sequence diagram). As shown in the above Figure, you can combine the interactions in different ways to create new scenarios. As you may be aware that sequence diagram can normally represent one scenario, so typically, we need to use one sequence diagram for the normal scenario and several sequence diagrams for the alternative scenarios. Now, with the new Interaction Overview Diagrams, you can use a control flow structure to reference the base use case and the <<include>> (normal scenario), and the <<extend>> use cases (alternative scenarios) all together.
Page 3 of 4
initiation
Page 4 of 4