O3_OSTA Operational State Viewpoint
Domain | Aspect | Maturity |
---|---|---|
Operational | Process & Behavior |
Example
Purpose
The viewpoint defines modes of operation for the prosed system (such as normal, on-road, degraded, war-time, maintenance, training etc.) which apply not only to the SOI but also to involved personnel. An operational mode defines a potential life-cycle selection for the SOI which has a relevant impact for the SOI’s stakeholder/users w.r.t. to the operations. [tbd]
Applicability
The Operational State Viewpoint supports the “Business or Mission Analysis Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§ 2.3.5.1] defining states/modes at an operational level (e.g., business or mission profile, and operational scenarios). The operational states/modes viewpoint contributes to Preliminary Life-cycle Concepts and the Business or mission analysis strategy.
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.
Stakeholder
Concern
- What operational states are defined for a system or system's operation?
- Which operational processes are possible to be performed in an operational state?
- Which operational states are possible results of performing an operational process?
Profile Model Reference
The following Stereotypes / Model Elements are used in the Viewpoint:
- attribute PreConditionStates of type SAF_OperationalState at SAF_OperationalProcess
- attribute PostConditionStates of type SAF_OperationalState at SAF_OperationalProcess
- SAF_OperationalState
- SAF_OperationalState contained in StateMachine
- StateMachine contained in SAF_OperationalPerformer
- Transition