Adding execution occurrence to interactions

Sequence diagrams can add execution occurrence to lifelines to control the start and finish behavior or flow of interactions to develop interactions for C/C++ applications..

An execution occurrence is created automatically when you create a synchronous or an asynchronous message on a lifeline. You can also manually create an execution occurrence to control the start and finish behavior in an interaction.

You can nest execution occurrences to indicate nested behavior in a call sequence. A nested execution occurrence overlaps an existing execution occurrence, and enables you to distinguish exactly where the activity associated with each message starts and finishes.

Parent topic: Developing behavioral features of C/C++ applications with UML sequence diagrams

Related concepts
Execution occurrences

Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.