Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.078 Create bare business operational scenario
Goal | Visualise the initial understanding of business interactions between operational entities and actors in this scenario |
---|---|
Requirements met by this process step | CSM-SMS Guidance 1.1a) |
Inputs | AMOD-137 Single operational capability context AMOD-024 Operational activity definition and allocation AMOD-028 Operational activities and interaction definitions (single operational capability) AMOD-023 Operational entity/actor states (where applicable) |
Outputs | AMOD-027 Operational bare business scenario |
Methodology | See the chapter "Specific guidance for scenarios applicable at the operational analysis" in Method for definition of scenarios for more guidance. Where new operational activities or interactions are identified, these should be first created on the corresponding AMOD-028 Operational activities and interaction definitions (single operational capability). |
Tools and non-human resources | Team for Capella (optional) General brainstorming equipment |
Cardinality | Once per operational capability |
Completion criteria | The output view complies with its modelling rules. The content of the output view represents the team's current understanding of the way this operational capability is intended to be delivered. |
Step done by (Responsible) | Operational concept architect |
Design review | |
Provides input to/assists (Contributes) | System architect Systems engineer Cross-cutting engineer Operations domain expert |
Uses outputs (Informed) | RAMS manager RAMS engineer Verification & validation manager |