These concepts about Unified Modeling Language (UML) sequence diagrams help you create and use sequence diagrams to understand and develop the behaviors and interactions between artifacts in C/C++ applications.
Sequence diagrams
A Unified Modeling Language (UML) sequence diagram illustrates the chronological sequence of messages between instances in an interaction.Interaction frames
In Unified Modeling Language (UML) diagrams, an interaction frame provides a context or boundary to the diagram in which you create diagram elements, such as lifelines or messages, and in which you observe behavior.Lifelines
In Unified Modeling Language (UML) sequence diagrams, a lifeline represents a connectable element of the enclosing classifier, including inherited properties or parameters, and describes how each instance participates in the interaction over a period of time. Each instance in an interaction is represented by a lifeline.Messages
A messages is a Unified Modeling Language (UML) sequence diagram element that defines a specific kind of communication between instances in an interaction. A message conveys information from one instance, which is represented by a lifeline, to another instance in an interaction.Execution occurrences
In Unified Modeling Language (UML) sequence diagrams, execution occurrences show the period of time when an instance that is represented by a lifeline is active. Each execution occurrence represents an execution in a behavior.Interaction occurrences
In Unified Modeling Language (UML) sequence diagrams, an interaction occurrence is an interaction that is referenced in another interaction frame. You can use interaction occurrences to take common content from one interaction and reuse it in another sequence diagram.Combined fragments
In Unified Modeling Language (UML) sequence diagrams, combined fragments define conditional structures in interactions.Interaction operators
In Unified Modeling Language (UML) sequence diagrams, an interaction operator defines the semantics of a combined fragment and determines how to use the interaction operands in the combined fragment.Interaction operands
In Unified Modeling Language (UML) sequence diagrams, an interaction operand is a container that groups the interaction fragments in a combined fragment and that represents a scenario that you add to a combined fragment.Guard conditions
In Unified Modeling Language (UML) sequence diagrams, a guard condition, also called as an interaction constraint, is a Boolean conditional expression that guards an interaction operand in a combined fragment. A guard condition contains two expressions that designate the minimum and maximum number of times that a loop combined fragment executes.Stop nodes
In Unified Modeling Language (UML) sequence diagrams, a stop node represents the destruction of an instance in an interaction.
Parent topic: Developing behavioral features of C/C++ applications with UML sequence diagrams
Related tasks
Developing behavioral features of C/C++ applications with UML sequence diagrams