A State may also have an associated doActivity Behavior. This Behavior commences execution when the State is entered (but only after the State entry Behavior has completed) and executes concurrently with any other Behaviors that may be associated ...

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Effect, Entry, Do, Exit
Composite state entry and exit points
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: TimeEvent on Transition [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
State
StateMachine
Behavior
State::doActivity
Full quote
A State may also have an associated doActivity Behavior. This Behavior commences execution when the State is entered (but only after the State entry Behavior has completed) and executes concurrently with any other Behaviors that may be associated with the State, until:
  • it completes (in which case a completion event is generated) or
  • the State is exited, in which case execution of the doActivity Behavior is aborted. The execution of a doActivity Behavior of a State is not affected by the firing of an internal Transition of that State.
    Next snippet
    Related snippets
    A State may have an associated entry Behavior. This Behavior, if defined, is executed whenever the State is entered through an external Transition.
    In addition, a State may also have an associated exit Behavior, which, if defined, is executed whenever the State is exited.
    Related snippets (backlinks)
    ... the entry Behavior of the State is executed (if defined) upon entry, but only after any effect Behavior associated with the incoming Transition is completed.
    ... if a doActivity Behavior is defined for the State, this Behavior commences execution immediately after the entry Behavior is executed. It executes concurrently with any subsequent Behaviors associated with entering the State, such as the entry ...
    When exiting a State, regardless of whether it is simple or composite, the final step involved in the exit, after all other Behaviors associated with the exit are completed, is the execution of the exit Behavior of that State.
    If the State has a doActivity Behavior that is still executing when the State is exited, that Behavior is aborted before the exit Behavior commences execution.
    When exiting from a composite State, exit commences with the innermost State in the active state configuration. This means that exit Behaviors are executed in sequence starting with the innermost active State.
    If the exit occurs through an exitPoint Pseudostate, then the exit Behavior of the State is executed after the effect Behavior of the Transition terminating on the exit point.
    When exiting from an orthogonal State, each of its Regions is exited. After that, the exit Behavior of the State is executed.
    Regardless of how a State is exited, the StateMachine is deemed to have “left” that State only after the exit Behavior (if defined) of that State has completed execution.
    Visit also
    Visit also (backlinks)