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.191 Refine capability realisations for the logical architecture

GoalCapture any refinements/adjustments to system capabilities after splits are done at logical level
Requirements met by this process step

ISO 15288 6.4.3.3 d) 2)

EN 50126 7.6.2

Inputs

AMOD-045 System capabilities

ARCH.M.040 Method for definition of capabilities

OutputsAMOD-147 Logical capability realisation
Methodology

For the most part, the system capabilities are not expected to change when transferred down to logical architecture level.

However, the "logical capability realisations" still need to be shown on a dedicated viewpoint for at least two reasons:

  1. this viewpoint is a statement of the capabilities that will be tested in the simulation of the logical architecture and therefore is an input to SIM and IVV activities.
  2. during decomposition of logical functions it may arise that a system capability must be split or specialised because the functional splitting results in variations in the functional chain.

Some example conditions (non-exhaustive) under which it may be appropriate to refine the system capabilities can be found in ARCH.M.040 Method for definition of capabilities.

Important

The amount of refinement of capability realisations at logical level should be kept to the minimum necessary, because each new capability realisation creates new work to do in verification and validation.

Further refinement will be allowed at subsystem level - see ARCH.192 Refine capability realisations for the subsystem architecture

Tools and non-human resourcesTeam for Capella
CardinalityOnce per package of system capabilities being delivered
Completion criteriaThe output view conforms to its modelling rules.
Design review

ARCH.R.5 Logical capability review

ARCH.R.6 Logical review - consolidated

Step done by (Responsible)Lead system architect
Provides input to/assists (Contributes)
  • System architect
  • Subsystem architect
  • Engineer
Uses outputs (Informed)

IVV role TBD  RCAMT-400 - Updates to ARCH to integrate artefact usage and role involvement with IVV BACKLOG