Vertex

UML-2.5.1: Has an incorrect local Transition with same source and vertex in 'Figure 14.34 Local Transitions'

Transitions of the kind internal are not shown explicitly in diagrams.

Source

Unified Modeling Language 2.5.1

kind = internal ... This kind of Transition can only be defined if the source Vertex is a State.

Source

Unified Modeling Language 2.5.1

kind = internal is a special case of a local Transition that is a self-transition (i.e., with the same source and target States), such that the State is never exited (and, thus, not re-entered), which means that no exit or entry Behaviors are executed ...

Source

Unified Modeling Language 2.5.1

kind = local ... However, for local Transitions the target Vertex must be different from its source Vertex. A local Transition can only exist within a composite State.

Source

Unified Modeling Language 2.5.1

kind = local is the opposite of external, meaning that the Transition does not exit its containing State (and, hence, the exit Behavior of the containing State will not be executed). ...

Source

Unified Modeling Language 2.5.1

kind = external means that the Transition exits its source Vertex. If the Vertex is a State, then executing this Transition will result in the execution of any associated exit Behavior of that State.

Source

Unified Modeling Language 2.5.1

The semantics of a Transition depend on its relationship to its source Vertex. Three different possibilities are defined, depending on the value of the Transition’s kind attribute ...

Source

Unified Modeling Language 2.5.1

Otherwise, the appropriate history entry into the Region is executed (see above). If no default history Transition is defined, then standard default entry of the Region is performed ....

Source

Unified Modeling Language 2.5.1

This is a Transition that originates in the history Pseudostate and terminates on a specific Vertex (the default history state) of the Region containing the history Pseudostate. This Transition is only taken if execution leads to the history Pseudostate a

Source

Unified Modeling Language 2.5.1

In cases where a Transition terminates on a history Pseudostate when the State has not been entered before (i.e., no prior history) or it had reached its FinalState, there is an option to force a transition to a specific substate, using the default ...

Source

Unified Modeling Language 2.5.1

Shallow history (shallowHistory) represents a return to only the topmost substate of the most recent state configuration, which is entered using the default entry rule.

Source

Unified Modeling Language 2.5.1

The effect is the same as if the Transition terminating on the deepHistory Pseudostate had, instead, terminated on the innermost State of the preserved state configuration, including execution of all entry Behaviors encountered along the way.

Source

Unified Modeling Language 2.5.1

Deep history (deepHistory) represents the full state configuration of the most recent visit to the containing Region.

Source

Unified Modeling Language 2.5.1

Two types of history Pseudostates are provided.

Source

Unified Modeling Language 2.5.1

Pseudostates - deepHistory and shallowHistory

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

Pseudostates - choice

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

Pseudostates - junction

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

UML StateMachine Diagram

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

Slide kind

UML StateMachine Diagram

In effect, the latter is a continuation of the external incoming Transition, with the proviso that the execution of the entry Behavior of the composite State (if defined) occurs between the effect Behavior of the incoming Transition and the effect ...

Source

Unified Modeling Language 2.5.1

Entry points represent termination points (sources) for incoming Transitions and origination points (targets) for Transitions that terminate on some internal Vertex of the composite State.

Source

Unified Modeling Language 2.5.1

If the composite State has an exit Behavior defined, it is executed after any effect Behavior of the incoming inside Transition and before any effect Behavior of the outgoing external Transition.

Source

Unified Modeling Language 2.5.1

In a well-formed model, such a Transition should have a corresponding external Transition outgoing from the same exit point, representing a continuation of the terminating Transition.

Source

Unified Modeling Language 2.5.1

Exit points are the inverse of entry points. That is, Transitions originating from a Vertex within the composite State can terminate on the exit point.

Source

Unified Modeling Language 2.5.1

Transition::target : Vertex [1..1] ... Designates the target Vertex that is reached when the Transition is taken.

Source

Unified Modeling Language 2.5.1

Transition::source : Vertex [1..1] ... Designates the originating Vertex (State or Pseudostate) of the Transition.

Source

Unified Modeling Language 2.5.1

Transition::kind : TransitionKind [1..1] = external Indicates the precise type of the Transition.

Source

Unified Modeling Language 2.5.1

A Transition represents an arc between exactly one source Vertex and exactly one Target vertex (the source and targets may be the same Vertex). It may form part of a compound transition, which takes the StateMachine from one steady State configuration...

Source

Unified Modeling Language 2.5.1

UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:02: UML 101 for model-based systems engineering with SysML

Slide kind

UML Profile Diagram

A StateMachine or composite State may contain multiple Regions representing behaviors that may occur in parallel.

Source

Unified Modeling Language 2.5.1

A Region is a top-level part of a StateMachine or a composite State, that serves as a container for the Vertices and Transitions of the StateMachine.

Source

Unified Modeling Language 2.5.1

A Pseudostate is an abstraction that encompasses different types of transient Vertices in the StateMachine graph. A StateMachine instance never comes to rest in a Pseudostate, instead, it will exit and enter the Pseudostate within a single ... step

Source

Unified Modeling Language 2.5.1

A Vertex is an abstraction of a node in a StateMachine graph. It can be the source or destination of any number of Transitions.

Source

Unified Modeling Language 2.5.1

In each Region of the StateMachine or composite State owning the entryPoint, there is at most a single Transition from the entry point to a Vertex within that Region.

Source

Unified Modeling Language 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.

Source

Unified Modeling Language 2.5.1

There can be at most one initial Vertex in a Region.

Source

Unified Modeling Language 2.5.1

An entry point is equivalent to a junction Pseudostate (fork in cases where the composite State is orthogonal): Entering via an entry point implies that the entry Behavior of the composite state is executed, followed by the Transition from the entry ...

Source

Unified Modeling Language 2.5.1

Submachines are a means by which a single StateMachine specification can be reused multiple times. They are similar to encapsulated composite States in that they need to bind incoming and outgoing Transitions to their internal Vertices.

Source

Unified Modeling Language 2.5.1

Subscribe to Vertex