P4-REQ-21-14-011
Statement
Implementation traceability SHALL NOT redefine logical traceability.
Source
Part 4, Section 21.14: Implementation Traceability Requirements.
Rationale
Logical traceability is established by the conceptual, logical, and FX logical architecture layers. Part 4 extends that traceability into implementation artifacts but does not replace or alter the logical relationships defined by earlier parts.
Maintaining this boundary prevents implementation mappings, repository organization, technology selections, or handbook rules from changing architectural meaning.
Applies To
This requirement applies to:
-
the Implementation Traceability Model;
-
logical-to-implementation mappings;
-
implementation traceability records;
-
repository and script traceability;
-
Developer Handbook traceability; and
-
implementation governance.
Verification
Verification SHALL confirm that implementation traceability does not redefine logical traceability.
Verification activities should include review checks confirming that:
-
logical traceability relationships remain authoritative;
-
implementation mappings extend rather than replace logical traceability;
-
implementation artifacts do not alter logical relationships;
-
implementation concerns remain distinguishable from logical concerns; and
-
changes to logical traceability are governed by the applicable earlier architectural part.
Traceability
This requirement preserves the boundary between logical traceability and the implementation traceability added by Part 4.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.