The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine
Using submachines 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
Submachines: entryPoint and exitPoint 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
State configurations 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
Kinds of States 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
uml101 - StateMachines - NOTATION REFERENCE CARD 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
Figure 13-1: Block definition diagram with state machines as blocks associated with submachines and types of parameters Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 13 StateMachines Slide kind SysML Block Definition Diagram (BDD)
State machines in block definition diagrams can also appear with the same notation as submachine states. Source OMG Systems Modeling Language (SysML) 1.6
Properties with AdjunctProperty applied, where the principal of the AdjunctProperty is a submachine state, can be used as the end of the associations towards the sub state machine. Source OMG Systems Modeling Language (SysML) 1.6
When a Region of the submachine StateMachine reaches the corresponding exit point, the submachine state is exited via this exit point. Source Unified Modeling Language 2.5.1
An exit point connection point reference as the source of a Transition implies that the source of the Transition is the exit point Pseudostate as defined in the submachine of the submachine State that has the exit point connection point defined. Source Unified Modeling Language 2.5.1
An entry point connection point reference as the target of a Transition implies that the target of the Transition is the entryPoint Pseudostate as defined in the submachine of the submachine State. As a result, the Regions of the submachine ... Source Unified Modeling Language 2.5.1
Connection point references are sources/targets of Transitions implying exits out of/entries into the submachine StateMachine referenced by a submachine State. Source Unified Modeling Language 2.5.1
Connection point references of a submachine State can be used as sources/targets of Transitions. They represent entries into or exits out of the submachine StateMachine referenced by the submachine State. Source Unified Modeling Language 2.5.1
14.2.3.5 ConnectionPointReference ... a connection point reference represents a usage (as part of a submachine State) of an entry/exit point defined in the StateMachine referenced by the submachine State. Source Unified Modeling Language 2.5.1
Exiting via a FinalState or by a group Transition has the same meaning as for ordinary composite States. Source Unified Modeling Language 2.5.1
a submachine Statemachine can be exited as a result of: reaching its FinalState; triggering of a group Transition originating from a submachine State, or; via any of its exit points. Source Unified Modeling Language 2.5.1
Any guards associated with these entry point Transitions must evaluate to true in order for the specification to be well formed. 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
A submachine StateMachine can be entered via its default (initial) Pseudostate or via any of its entry points (i.e., it may imply entering a non-orthogonal or an orthogonal composite State with Regions). Entering via the initial Pseudostate ... Source Unified Modeling Language 2.5.1
NOTE. Each submachine State represents a distinct instantiation of a submachine, even when two or more submachine States reference the same submachine. Source Unified Modeling Language 2.5.1
The entry, exit, and effect Behaviors and internal Transitions are defined as contained in the submachine State. Source Unified Modeling Language 2.5.1
The Regions of the submachine StateMachine are the Regions of the composite State. Source Unified Modeling Language 2.5.1
A submachine State implies a macro-like insertion of the specification of the corresponding submachine StateMachine. It is, therefore, semantically equivalent to a composite State. Source Unified Modeling Language 2.5.1
Each ConnectionPointReference is matched by a corresponding entry or exit point in the referenced submachine StateMachine. This provides the necessary binding mechanism between the submachine invocation and its specification. Source Unified Modeling Language 2.5.1
A ConnectionPointReference represents a point on the submachine State at which a Transition either terminates or originates. That is, they serve as targets for incoming Transitions to submachine States, as well as sources for outgoing Transitions ... Source Unified Modeling Language 2.5.1
The concept of ConnectionPointReference is provided to support binding between the submachine State and the referenced StateMachine. Source Unified Modeling Language 2.5.1
Consequently, they require a more complex binding. This is achieved through the concept of submachine State (i.e., States with isSubmachineState = true), which represent references to corresponding submachine StateMachines. Source Unified Modeling Language 2.5.1
However, whereas encapsulated composite States and their internals are contained within the StateMachine in which they are defined, submachines are, like programming language macros, distinct Behavior specification ... 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
