Pseudostates - initial, fork, join, terminate

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
01:03: UML Behavior: StateMachines quick start
Topic level
ESSENTIAL
UML keywords
StateMachine
StateMachine Diagram
State
Transition
Vertex
PseudostateKind
PseudostateKind::initial
PseudostateKind::fork
PseudostateKind::join
PseudostateKind::terminate
Transition::effect
Behavior
Keywords
Slide kind
UML StateMachine Diagram
NOTATION REFERENCE ONLY: This diagram is not meant to be executable!
The absence of explicit triggers or guards on Transition symbols in this diagram is for brevity only and does not imply completion Transitions with implicit triggers.
Click on the image to view it full size
Up next
Pseudostates - junction
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] initial - An initial Pseudostate represents a starting point for a Region; that is, it is the point from which execution of its contained behavior commences when the Region is entered via default activation.
  [UML-2.5.1] There can be at most one initial Vertex in a Region.
  [UML-2.5.1] initial - ... It is the source for at most one Transition, which may have an associated effect Behavior, but not an associated trigger or guard.
  [UML-2.5.1] fork – fork Pseudostates serve to split an incoming Transition into two or more Transitions terminating on Vertices in orthogonal Regions of a composite State.
  [UML-2.5.1] The Transitions outgoing from a fork Pseudostate cannot have a guard or a trigger.
  [UML-2.5.1] terminate – Entering a terminate Pseudostate implies that the execution of the StateMachine is terminated immediately. The StateMachine does not exit any States nor does it perform any exit Behaviors. Any executing doActivity Behaviors are ... aborted
  [UML-2.5.1] join – This type of Pseudostate serves as a common target Vertex for two or more Transitions originating from Vertices in different orthogonal Regions.
  [UML-2.5.1] Transitions terminating on a join Pseudostate cannot have a guard or a trigger.
  [UML-2.5.1] Similar to junction points in Petri nets, join Pseudostates perform a synchronization function, whereby all incoming Transitions have to complete before execution can continue through an outgoing Transition.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
StateMachine diagram for comparing action language access to an operation for a guard
Overview: Controller class (and its Activity), Dialer Class (and its StateMachine), Number class
StateMachine for the Dialer class
Behavior StateMachines can be used to specify any of the following
The number.append Activity as entry Behavior for the PartialDial State
The number.print Activity as exit Behavior for the PartialDial State
Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”
Figure 13-1: Block definition diagram with state machines as blocks associated with submachines and types of parameters
Related slides (backlinks, includes other tutorials)