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.177 Complete the definition of the operational capability of interest

Goal

Visualise the E2E relationships between the OCs from the perspective of one operational capability of interest

Define precisely the value delivered by an operational capability

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

AMOD-021 Operational capabilities definition

ARCH.M.040 Method for definition of capabilities

Outputs

AMOD-137 Single operational capability context

AMOD-021 Operational capabilities definition (updated)

Methodology

At the end of ARCH.002 Create initial set of operational capabilities the AMOD-021 Operational capabilities definition was created and the capabilities have been broadly defined but without precise pre- and post-conditions, which are crucial to modelling the operational process and scenario.

In this activity:

  • Precise pre- and post-conditions of the operational capability shall be defined (Note: these can be further elaborated later when more is known ARCH.904 Incorporate risk control measures in the operational needs)
  • Check and complete the involved entities or actors of the operational capability
  • Check and complete the relationships with other operational capabilitie
  • If needed it shall be determined if the operational capability of interest must be split into more refined ones, due to identification of several success scenarios, different operational processes due to different preconditions, or different stakeholders involved with different intentions.

The output of this activity is the context of operational capability diagram.

At this point, there is no need to align with other operational capabilities.

Note: If there are entities/actors connected to the operational capability of interest, you can decide to remove those if this makes the diagram clearer.

Tools and non-human resources

Team for Capella

Cardinality

Once per Operational Capability

Completion criteria

The output views conform to their modelling rules.

Design review

ARCH.R.1 Operational feature review

ARCH.R.2 Operational review - consolidated

Step done by (Responsible)

Operational concept architect

Provides input to/assists (Contributes)

System architect

Systems engineer

Uses outputs (Informed)

None