P1-REQ-13-7-008

Return to Part 1 Requirements

Statement

Traceability SHALL support impact analysis across conceptual, logical, implementation, deployment, and Evidence layers.

Source

Part 1, Section 13.7: Traceability Requirements.

Rationale

Impact analysis depends on traceability across architectural layers. A change to a conceptual concern may affect logical elements, implementation artefacts, deployment artefacts, and evidence. A change to evidence, deployment, implementation, or logical material may also affect the interpretation of architectural support.

This requirement supports change control, review, governance, and risk management across the architecture lifecycle.

Applies To

This requirement applies to traceability relationships used for impact analysis.

It applies specifically to impact analysis across:

Conceptual layersLogical layersImplementation layersDeployment layersEvidence layers

Verification

Verification SHALL confirm that Traceability supports impact analysis across conceptual, logical, implementation, deployment, and Evidence layers.

Verification activities include review checks confirming that:

Traceability identifies affected upstream elementsTraceability identifies affected downstream elementsImpact analysis spans the required architectural layersImpact analysis distinguishes one-to-one, one-to-many, many-to-one, and many-to-many relationships where applicable

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.