F3_SSTA System State Viewpoint
| Domain | Aspect | Maturity |
|---|---|---|
| Functional | Process & Behavior |  under construction |
Purpose
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.
Applicability
The System State Viewpoint supports the activities included in the “System Requirements Definition Process” of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§2.3.5.3] and contributes to the System Function Definition.
Supported Processes
Supported Information Items
Presentation
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.
Stakeholder
- Hardware Developer
- IV&V Engineer
- Maintainer
- Regulation Authority
- Safety Expert
- Security Expert
- Software Developer
- System Architect
Concern
- Which modes and states does the system have?
- Which system functions are dependent on a systems mode or state?
Exposed Concepts
The Diagram shows the concepts exposed by the viewpoint, and related concepts if necessary.
The Table shows the concepts exposed by the viewpoint, and related concepts if necessary.
| Concept | Documentation |
|---|---|
| LETbeeingInSSE | Specifies the System States a Logical Element can be in. |
| SDKbeeingInSSE | Specifies that a System Domain Kind can have certain states. Note: Of course an item is in only one distinct state at a certain time. The multiplicity means that an Item can have a set of possible states, and a state can be used to specify possible States for several domain items. |
| System State | Describes a state (or mode) of something on system level that can have distinct states. |
| SFNhasPreconditionSSE | Specifies the fact a System Function may have System States as precondition. This means that the Function is only provided in distinct States. |
| System State Transition | Describes an allowed transition between two system states of an item that can be in distinct States. |
| SFNhasPostconditionSSE | Specifies the fact that a System Function can perform a particular set of transitions, resulting in the related target System States. |
| triggering | specifies that an System Triggering Event triggers a System State Transition. |
Realization of exposed Concepts
The Diagram shows the realization of exposed concepts.
The Table shows the realization of exposed concepts.
Related Viewpoints
Required Viewpoints
Recommended Viewpoints
Example
