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.041 Transfer or trace upper level model elements to system level

SM-2777 - Populate Confluence page for activity definition: ARCH.041 Transfer or trace OA to system capability Finished

RCAMT-464 - Update ARCH.911 and ARCH.912 after refinment proposal was approved Finished  

RCAMT-490 - Update ARCH process diagram to reflect SoS / SuS transfer steps Finished

Goal

Transfer relevant upper level model elements to system level and establish traceability.

Record and maintain traceability within the analysis model

Requirements met by this process step

ISO 15268 6.4.2.3.a.1

ISO 15288 6.4.3.2 f

Inputs

AMOD-046 Selected system boundary tradeoff record

AMOD-120 Record of system capabilities and missions

AMOD-121 Record of system and actor functions

AMOD-122 Record of system actors

Content from collaborative projects (optional)

Logical architecture elements from Parent model in case of Child model: AMOD.025, AMOD-081, AMOD-082, AMOD-084, AMOD-088, AMOD.091, AMOD.092, AMOD-125, AMOD.147 (these viewpoints are truncated according to the scope of the child model)

ARCH.M.060 Method for the execution of automatic transition in capella

Outputs

Outputs will be generated by the following process steps: ARCH.119 Define consolidated set of system capabilities/missions and ARCH.045 Define complete set of system-level actors

+

AMOD-103 Consolidated system functions

AMOD-104 System level - operational level traceability report

Methodology

In the case of the parent model (the one with an upper level which is operational analysis):

See operational analysis to system analysis → ARCH.M.060 Method for the execution of automatic transition in capella


In the case of the child model (the one without an operational analysis & with an upper level which is the logical architecture of a parent model):

See Vertical transition between LA layer of parent model and SA layer of new child models (section "Actions in the child model") → ARCH.M.060 Method for the execution of automatic transition in capella


Traceability between upper level and System Level

To be determined. SM-3129

Tools and non-human resourcesTeam for Capella
Cardinality

In case of SoS model:

One-off with revisions for managing changes to the set of operational activities

Once per operational capability 

In case of Child model:

One-off with revisions for managing changes to the set of logical functions 

Once per logical capability 

Completion criteria

The transfer of all model elements that shall be transferred as system level (in accordance with AMOD-120, AMOD-121, AMOD-122 is completed and a traceability link from system level to the upper level is implemented.

Design reviewARCH.R.3 System capability review
Step done by (Responsible)Lead system architect
Provides input to/assists (Contributes)
  • Operational concept architect
  • System architect
  • Engineer
  • Cross-cutting engineer
Uses outputs (Informed)None directly