| DWF_SM_01 - A state machine must have only one initial state | |
| This rule checks that a state machine have only one initial state | |
| DWF_SM_02 - An initial state must have only one outgoing transition | |
| This rule checks that an initial state have only one outgoing transition. | |
| DWF_SM_03 - Referenced states of a state must be all involved states in its subregions | |
| This rule checks that referenced States in a State are the sum of all involved States of sub regions. | |
| DWF_SM_04 - A decision or a fork must have only one entering transition | |
| This rule checks that a decision or a fork have only one entering transition. | |
| DWF_SM_05 - A join connector must have only one outgoing transition | |
| This rule checks that a join connector have only one outgoing transition. | |
| DWF_SM_06 - Mode and State shouldn't be in same hierarchy | |
| This rule depends on the Preference option "Mode/State mixed hierarchy allowed". If this option is set to false, the rule checks that a state is not in a mode hierarchy or a mode is not in a state hierarchy. In this case, hierarchy includes siblings. | |
| DWF_SM_07 - Fork and Join State must be used in the context of concurrent Region | |
| This rule ensure that Join/Fork states are used in concurrent region context. | |
| DWF_SM_08 - State must reference a function with doActivity/entry/exit related with its owning component | |
| This rule check if doActivity/Entry/Exit reference only functions associated to the component owning the state Machine or allocated to one of its subcomponents. | |
| DWF_SM_09 - StateTransitions trigger shall not reference unallocated Functions or Functional Exchanges and be consistent with business query. | |
| This rule check that Functions or Functional Exchanges which triggers the StateTransition are allocated on the Component or one of its subcomponents. | |
| DWF_SM_10 - StateTransition source and target shouldn't be stored in concurrent region | |
| This rule check that source and target of StateTransition are not stored in concurrent region. | |
| DWF_SM_11 - EntryPoint must have only one outgoing transition and one or more incoming transition | |
| This rule check that EntryPoint have only one outgoing transition and one or more incoming transition. | |
| DWF_SM_12 - ExitPoint must have only one incoming transition and one or more outgoing transition | |
| This rule check that ExitPoint have only one incoming transition and one or more outgoing transition. | |
| DWF_SM_13 - Shallow/Deep History shall have only incoming transitions | |
| This rule check that Shallow/Deep History state has only incoming transitions. | |
| DWF_SM_14 - Functions referenced in a State must be referened as available in this State. | |
| This rule check that Functions referenced as DoActivity, Entry or Exit of a Mode/State are available via the Operational Activities/Functions reference of this State. | |
| DWF_SM_15 - Mode and State shouldn't reuse each other | |
| This rule depends on the Preference option"Mode/State mixed hierarchy allowed". If this option is set to false, the rule checks that a state does not reuse a mode or a mode does not reuse a state. | |
| DWF_SM_16 - Mode and State can not be mixed in the same State Machine | |
| This rule depends on the Preference option "Mode/State mixed hierarchy allowed". If this option is set to false, the rule checks that a State Machine has no mixed States and Modes. | |