| Domain | Aspect | Maturity |
|---|---|---|
| Functional | Process & Behavior |  released |
The System State Viewpoint defines the conditions of the SOI or parts of thereof that constrain the execution of System Functions. System States are used as pre- or post-condition of System Use Cases, and as constraints within the definition of System Functions to specifying valid transitions. Valid transitions between System States and the conditions for transitioning are specified in system wide concepts captured in System Requirements.
The System State Viewpoint supports the "System Requirements Definition Process" activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2015 [§4.3] and contributes to the System Function Definition.
A block definition diagram (BDD) featuring states, and state transitions. Note: References to model elements that are dependent of states, or transitions shall be shown as callout, or compartment notation.
A tabular format listing states, state transitions, and the conditons to be fullfilled before the transition will occur. References to model elements that are dependent of states (Domain Item Kinds, System Functions, System Use Cases, etc.), or transitions shall be shown in the table.
- Hardware Developer
- IV&V Engineer
- Maintainer
- Regulation Authority
- Safety Expert
- Security Expert
- Software Developer
- System Architect
- Which modes and states does the system have?
- Which system functions are dependent on a systems mode or state?
The following Stereotypes / Model Elements are used in the Viewpoint:
- Event [UML_Standard_Profile]
- State [UML_Standard_Profile]
- StateMachine [UML_Standard_Profile]
- Transition [UML_Standard_Profile]
- SAF_DomainKind
- SAF_F3_SSTA
- SAF_F3_SSTA_Table
- SAF_LogicalElement
- SAF_SystemFunction
none