Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.055 Model system and actor states
Goal | Capture understanding of how the system's behaviour changes based on states; Refine understanding of state-based differences in behaviour of system actors |
---|---|
Requirements met by this process step | None defined |
Inputs | AMOD-119 System context definition AMOD-056 System functions and exchanges (single system capability) AMOD-023 Operational entity/actor states (as reference) In particular if there exists an instance of AMOD-023 for the wider system of interest, this is a reference for the creation of states on the system's state model. |
Outputs | |
Methodology | Tasks
During analysis of a system capability, new states may be identified for the system or for the actors. New states diagrams should be created when statefulness is identified on an actor or the system for the first time. Thereafter, the existing instance of AMOD-060 should be updated unless it is necessary to create a separate view for size reasons. Independent dimensions of statefulness should be modelled as regions on the same state machine, rather than as a separate state machine.
System functions may not be available all the time. Their availability may be dependent on a system state or mode. This activity should be carried out in parallel to the modelling of system functionality for a single system capability. The scope of the activity is all system functions involved in the capability. For each state dimension (that is, each individual state machine or state machine region on the system): If a system function is only available in certain system states Allocate the function to those states where it is available; Else if a system function is available independently of this state dimension: Allocate the function to all states in this dimension end for |
Tools and non-human resources | Team for Capella |
Cardinality | Once per system capability |
Completion criteria | The output view conforms to its modelling rules. All known/identified states associated with the system, or an actor, for the current capability, have been captured in the output view. All system functions involved in this capability are allocated to the correct states |
Design review | |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None directly |