Legal information

Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)

ARCH.002 Create initial set of operational capabilities

GoalIdentify enough operational capabilities to provide a starting point for understanding the problem space
Requirements met by this process step

CSM-SMS guidance 1.1a)

EN 50126-1 7.2.2 a)

ISO 15288 6.4.1.3 b 2)

Inputs

Business briefing material

Knowledge of contributors

AMOD-022 Enterprise & environment definition

ARCH.M.040 Method for definition of capabilities

OutputsAMOD-021 Operational capabilities definition
Methodology

Brainstorming using any practical method to identify candidates, then rationalise by agreeing a reasonable level and size of item.

Model the capabilities in Capella. Multiple diagrams can be created to implement view AMOD-021, to keep diagram size acceptable. Diagrams could group capabilities on a similar theme. Capabilities may appear on multiple diagrams if they cross multiple themes.

Note: it is not necessary to identify all dependencies/relationships between operational capabilities, nor to define very precise and synchronised start/end conditions at this stage. However, there should be some idea of these properties so that they can be used as a starting point for operational scenario analysis. They will be updated later in the process as more is learned about the capability set and the operational needs.

Tools

Any practical brainstorming tools + appropriate environment

Team for Capella

Cardinality

One-off at the beginning of the project.

Revisions allowed to the whole set based on what is learned during analysis of the individual capabilities.

Completion criteria

The participants in brainstorming agree that a reasonable level of coverage has been achieved;

The output model views comply with their model specification and modelling rules;

The accountable role judges that a reasonable level of coverage has been achieved.

Design review

ARCH.R.1 Operational capability review

ARCH.R.2 Operational review - consolidated

Step done by (Responsible)Operational concept architect
Provides input to/assists (Contributes)

Circle/Cluster lead

Lead system architect

System architect

Systems engineer

Operations domain expert

Uses outputs (Informed)None directly