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.169 Consolidate traceability between model elements at physical level and model elements at logical level

RCAMT-330 - Create Confluence page for process step ARCH.169 Finished

GoalTraceability between model elements at logical level and model elements at physical level established.
Requirements met by this process stepNone defined
Inputs

All relevant model elements on logical level and physical level


Outputs

AMOD-127 Physical level - logical level traceability report

Methodology

Identify a model element to be considered in the physical architecture layer:

Check if the model element already possesses a relationship to a corresponding model element at logical level. If that is the case, check if that relationship is reasonable and correct.

All elements that are present on the physical layer as a result of a Capella transition are automatically provided with Realisation Links between themselves and their source logical-level elements. This is the preferred solution for assuring correct traceability in the model. If no Realisation Links can be automatically generated for a given model element, establish a new Generic Trace relationship between them.

Repeat the above steps until all model elements at physical level possess either Realisation Links or an outgoing Generic Trace relationship to at least one corresponding model element at logical level. Afterwards, check once again whether all of those relationships are correct.

Guidance on creating Generic Traces:

  • Right click on the system-level model element in the Capella Explorer → Wizards → Trace Manager
  • Add a new outgoing generic trace relationship from the physical-level model element to the corresponding logical-level model element
Tools and non-human resources

Team for Capella

Cardinality

At least once prior to ARCH.R.8 Subsystem review - consolidated

Completion criteria

Each physical-level model element possesses either a Realisation Link or a Generic Trace relationship to at least one logical-level model element.

Design reviewARCH.R.8 Subsystem review - consolidated
Step done by (Responsible)Cross-cutting engineer
Provides input to/assists (Contributes)
  • Engineer
  • Cross-cutting engineer
  • Subsystem Architect
Uses outputs (Informed)

None