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.192 Refine capability realisations for the subsystem architecture

SM-5415 - Create Confluence page for process step ARCH.192 Refine physical capability realisations Finished

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

ISO 15288 6.4.3.3 d) 2)

EN 50126-1 7.6.2

Inputs

AMOD-147 Logical capability realisation

AMOD-045 System capabilities

ARCH.M.040 Method for definition of capabilities

OutputsAMOD-148 Subsystem capability realisation
Methodology

In many cases, the system capabilities/logical capability realisations can stay at the same level of granularity when transferred down to physical level.

However, the "physical 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 physical architecture and therefore is an input to SIM and IVV activities.
  2. during decomposition of physical functions it may arise that a capability realisation must be split or specialised because the functional splitting results in variations in the functional chain.
  3. some logical components may need to be instantiated several times within different subsystem boundaries (for example, diagnostics, configuration data), resulting in several independent variant functional chains (example: logical capability realisation "update configuration data of topology" splits to "update configuration data of topology on SL subsystem", "update configuration data of topology on PE subsystem", and so on, because these can be independently done at different times).

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

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.7 Subsystem capability review

ARCH.R.8 Subsystem 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