Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.159 Model operational states
Goal | Refine understanding of state-based differences in behaviour of operational entities/actors |
---|---|
Requirements met by this process step | None identified |
Inputs | AMOD-024 Operational activity definition and allocation AMOD-023 Operational entity/actor states AMOD-028 Operational activities and interaction definitions (single operational capability) |
Outputs | AMOD-023 Operational entity/actor states (updated/new) |
Methodology | Tasks:
During analysis new states may be identified for operational entities, actors or abstract concepts, that were not known during ARCH.006. Either update existing instances of views or, where no statefulness was previously identified for an operational actor/entity, create a new one.
Define the set of activities, allocated to a entity/actor, that are available while the entity/actor is in a state. If it is not clear whether an activity should or should not be available, set it to be available. Example from current (staffed) train operation: the "train conductor" might have two states, "Routine operation" and "Emergency operation". In each state they have different duties. During routine operation, the "train conductor" might be involved in checking the tickets of passengers. But they would not bother doing this during an emergency, rather they might be performing their duties to protect the train and evacuate passengers. Hence "check tickets" as an operational activity would be made available only in the "routine operation" state and not in the "emergency operation" state. Note: Mapping of operational activities to states can be done by setting "Available in states" property of the activities or the "Operational Activities / Functions" property of a state. Whereas the properties "entry", "exit" and "do activity" of a state shall NOT be used. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per operational capability |
Completion criteria | (The output views conform to their modelling rules AND For all the involved entities for this capability, the operational activities associated with each state have been correctly assigned. AND Statefulness that was identified during the analysis of the operational capability has been captured in the model) OR No further statefulness was identified during the analysis of this operational capability. |
Design review | |
Step done by (Responsible) | Operational concept architect |
Provides input to/assists (Contributes) | System architect Systems engineer |
Uses outputs (Informed) | None directly |