Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.006 Create initial set of operational states for operational entities/actors
Goal | Capture understanding of state-based differences in behaviour of operational entities/actors |
---|---|
Requirements met by this process step | CSM-RA Guidance 3.11 |
Inputs | Knowledge of workshop participants AMOD-022 Enterprise & environment definition |
Outputs | AMOD-023 Operational entity/actor states |
Methodology | This activity does not need to be done for every operational entity and actor. It is only needed when
In either case it should be fairly clear what the states are, based on knowledge of the modeller; if necessary, a brainstorming workshop can be held to identify candidates and come to an agreement. The results should be modelled as a states diagram in accordance with modelling rules. Where there are existing state definitions, but only a subset of them are of interest, then it is permissible to merge some states into a larger one. There is no real need to precisely follow an external definition if it is not helpful to do so. |
Tools and non-human resources | Standards and definitions belonging to particular entities |
Cardinality | Once per operational entity, but only where necessary. |
Completion criteria | There exists a model view (AMOD-023 Operational entity/actor states) for the entity/actor of interest, that is compliant with its definition and rules. |
Design review | |
Step done by (Responsible) | Operational concept architect |
Provides input to/assists (Contributes) | Operations domain expert |
Uses outputs (Informed) | ARCH.010 Carry out initial operational scenario analysis for each operational capability |