NODE TYPE | NOTATION | REFERENCE |
Frame | ![]() |
The notation shows a rectangular frame around the diagram with a name in a compartment in the upper left corner. See "Interaction (from BasicInteraction, Fragments)". |
Lifeline | ![]() |
See "Lifeline (from BasicInteractions, Fragments)" |
ExecutionOccurrence | ![]() |
See "CombinedFragment (from
Fragments)" . See also "Lifeline
(from BasicInteractions, Fragments)" and "ExecutionOccurrence (from
BasicInteractions)" |
InteractionOccurrence | ![]() |
See "InteractionOccurrence (from Fragments)". |
CombinedFragment | ![]() |
See "CombinedFragment (from Fragments)" |
StateInvariant / Continuations | ![]() |
See "Continuation
(from Fragments)" and "StateInvariant (from
BasicInteractions)" |
Coregion | ![]() |
See explanation under parallel in "CombinedFragment (from Fragments)" |
Stop | ![]() |
See Figure 333 |
Duration Constraint Duration Observation |
![]() |
See Figure 347 |
Time Constraint Time Observation |
![]() |
See Figure 347 |
NODE TYPE | NOTATION | REFERENCE |
Message | ![]() |
Messages come in different variants depending on what kind of Message they convey. Here we show an asynchronous message, a call and a reply. These are all complete messages. See "Message (fromBasicInteractions)" . |
Lost Message | ![]() |
Lost messages are messages with known sender, but the reception of the message does not happen. See "Message (from BasicInteractions)" |
Found Message | ![]() |
Found messages are messages with known receiver, but the sending of the message is not described within the specification. See "Message(from BasicInteractions)" |
GeneralOrdering | ![]() |
See "GeneralOrdering (from BasicInteractions)" |
NODE TYPE | NOTATION | REFERENCE |
Frame | ![]() |
The notation shows a rectangular frame around the diagram with a name in a compartment in the upper left corner. See "Interaction (from BasicInteraction, Fragments)" . |
Lifeline | ![]() |
See "Lifeline (from BasicInteractions, Fragments)" |
NODE TYPE | NOTATION | REFERENCE |
Message | ![]() |
See "Message (from
BasicInteractions)" . and "Sequence
expression" The arrow shown here indicates the communication direction. |
NODE TYPE | NOTATION | REFERENCE |
Frame | ![]() |
The notation shows a rectangular frame around the diagram with a name in a compartment in the upper left corner. See "Interaction (from BasicInteraction, Fragments)". |
Interaction | ![]() |
An Interaction diagram of any kind may appear inline as an
ActivityInvocation. See
"Interaction (from
BasicInteraction, Fragments)" . The inline Interaction diagrams may be either anonymous (as here) or named. |
InteractionOccurrence | ![]() |
ActivityInvocation in the form of InteractionOccurrence. See "InteractionOccurrence
(from Fragments)" . The tools may choose to "explode" the view of an InteractionOccurrence into an inline Interaction with the name of the Interaction referred by the occurrence. The inline Interaction will then replace the occurrence by a replica of the definition Interaction where eventual arguments have replaced parameters. |
NODE TYPE | NOTATION | REFERENCE |
Frame | ![]() |
The notation shows a rectangular frame around the diagram with a name in a compartment in the upper left corner. See "Interaction (from BasicInteraction,Fragments)". |
Message | ![]() |
Messages come in different variants depending on what kind of Message they convey. Here we show an asynchronous message, a call and a reply. See "Message (from BasicInteractions)" . |
Message label | ![]() |
Labels are only notational shorthands used to prevent
cluttering
of the diagrams with a number of messages crisscrossing the diagram
between Lifelines that are far apart. The labels denote that a Message may be disrupted by introducing labels with the same name. |
State or condition | ![]() |
This is the state of the classifier or attribute,
or some timeline testable condition, such as an discrete enumerable
value. See also
"StateInvariant (from BasicInteractions)" It is also permissable to let the state-dimension be continuous as well as discrete. This is illustrative for scenarios where certain entities undergo continuous state changes, such as temperature or density. |
General value | ![]() |
Shows the value of the connectable element as a lifeline function of time. Value is explicitly denoted as text. Crossing reflects the event where the value changed. |
Lifeline | ![]() |
See "Lifeline (from BasicInteractions, Fragments)" |
GeneralOrdering | ![]() |
See "GeneralOrdering (from BasicInteractions)" |
Stop | ![]() |
See "Stop (from BasicInteractions)" |