Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.110 Consolidate traceability between model elements at logical level and model elements at system level
RCAMT-267
-
Populate Confluence page for activity definition: ARCH.110 Consolidate traceability between model elements at logical level and model elements at system level
Finished
Goal | Traceability between model elements at logical level and model elements at system level established. |
---|---|
Requirements met by this process step | None defined |
Inputs | All relevant model elements on logical level and system level |
Outputs | AMOD-126 Logical level - system level traceability report |
Methodology | Identify a model element to be considered in the logical architecture layer: Check if the model element already possesses a relationship to a corresponding model element at system level. If that is the case, check if that relationship is reasonable and correct. All elements that are present on the logical architecture layer as a result of a Capella transition are automatically provided with Realisation Links between themselves and their source system-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 logical level possess either Realisation Links or an outgoing Generic Trace relationship to at least one corresponding model element at system level. Afterwards, check once again whether all of those relationships are correct. Guidance on creating Generic Traces:
|
Tools and non-human resources | Team for Capella |
Cardinality | At least once prior to ARCH.R.6 |
Completion criteria | Each logical-level model element possesses either a Realisation Link or a Generic Trace relationship to at least one system-level model element. |
Design review | ARCH.R.6 Logical review - consolidated |
Step done by (Responsible) | Cross-cutting engineer |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None |