OTX Reference  
OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State Class Reference

State of a state machine. More...

Inheritance diagram for OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State:
Inheritance graph

Public Attributes

Flow entryFlow
 Cardinality [0..1]
If the state-machine switches to this state, if available, the entryFlow will execute first. More...
 
Flow exitFlow
 Cardinality [0..1]
If the state-machine leaves this state, if available, the exitFlow will execute last. For more information regarding from please refer to Part 2 of ISO 13209. The exitFlow shall not be executed if an unhandled exception occurs, or if the StateMachine execution is interrupted by a TerminateLanes node. More...
 
Transitions transitions
 Cardinality [0..1]
Collection of all transitions related to this state. More...
 
Triggers triggers
 Cardinality [0..1]
The collection of all triggers related to this state. More...
 
- Public Attributes inherited from OpenTestSystem.Otx.Core.UniversalTypes.NamedAndSpecified
ExtensibleData[] extendedData
 Declares general data for NamedAndSpecified which can be extented by new general data defined in new OTX extensions using the standardised extension mechanism. For example it can be used to specify specification relevant content in a better structured way. More...
 
OtxId id
 Unique identifier of an element More...
 
MetaData metaData
 Additional tool-specific data More...
 
OtxName name
 Name of an element More...
 
NamedAndSpecifiedSpecification[] specification
 Descriptive specification More...
 

Detailed Description

State of a state machine.

Status of the status machine. A state machine is always in exactly one state at a time. Between states it can be switched over a transition. An transition is executed when an event occurs and optionally a condition is met. Optionally, upon reaching a status, the Entry Flow and exiting the Exit Flow status can be executed.

Checker rules
CheckerRule.StateMachineProcedure_Chk004 - Mandatory trigger
CheckerRule.StateMachineProcedure_Chk005 - Mandatory transition

Member Data Documentation

◆ entryFlow

Flow OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State.entryFlow

Cardinality [0..1]
If the state-machine switches to this state, if available, the entryFlow will execute first.

◆ exitFlow

Flow OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State.exitFlow

Cardinality [0..1]
If the state-machine leaves this state, if available, the exitFlow will execute last. For more information regarding from please refer to Part 2 of ISO 13209. The exitFlow shall not be executed if an unhandled exception occurs, or if the StateMachine execution is interrupted by a TerminateLanes node.

◆ transitions

Transitions OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State.transitions

Cardinality [0..1]
Collection of all transitions related to this state.

If a trigger terminates its wait state, all transitions which refer to this trigger will be checked in order of XML occurrence.
Each state except the completed state shall have a at least one transition.

◆ triggers

Triggers OpenTestSystem.Otx.Extensions.StateMachineProcedure.DataTypes.State.triggers

Cardinality [0..1]
The collection of all triggers related to this state.

The order of the triggers is not specified. This means, that if two trigger event sources fire at the same time, it cannot be guaranteed, that the transitions referred to by the first trigger(in XML order) are performed.
Each state except the completed (final) state shall have a at least one trigger.