Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.161
SM-3522
-
Create Confluence page for activity definition ARCH.161
Finished
Goal | Refine understanding of state-based differences in behaviour of operational entities/actors |
---|---|
Requirements met by this process step | None identified (TBD) |
Inputs | AMOD-023 Operational entity/actor states AMOD-027 Operational bare business scenario AMOD-028 Operational activities and interaction definitions (single operational capability) |
Outputs | Output is not directly visible on a view, it is a set of relationships in the model viewable via the "Available in states" property of the activities or the "Operational Activities / Functions" property of a state. |
Methodology | For each operational entity/actor involved in the scenario For each state that the entity/actor can exhibit Define the set of activities, allocated to this entity/actor, that are available while the entity/actor is in this state end for end for 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 (Zugchef) might have two states, "Routine operation" and "Emergency operation". In each state they have different duties. During routine operation, the Zugchef 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 | For all the involved entities for this capability, the operational activities associated with each state have been correctly assigned. |
Design review | |
Step done by (Responsible) | System architect |
Provides input to/assists (Contributes) | None identified |
Uses outputs (Informed) | None directly |