P4-REQ-21-14-004
Statement
Implementation traceability SHALL support backward review from Phase 0 implementation artifacts to FX logical elements or implementation concerns.
Source
Part 4, Section 21.14: Implementation Traceability Requirements.
Rationale
Backward traceability allows reviewers to begin with a Phase 0 implementation artifact and determine why that artifact exists and which FX logical element or implementation concern it supports.
This prevents unexplained implementation artifacts from entering the baseline and supports review, maintenance, governance, and change-impact analysis.
Applies To
This requirement applies to:
-
implementation modules;
-
DDS Topics;
-
IDL structures and generated types;
-
QoS profiles;
-
scripts;
-
configuration artifacts; and
-
repository artifacts.
Verification
Verification SHALL confirm that backward review from Phase 0 implementation artifacts is supported.
Verification activities should include review checks confirming that:
-
governed implementation artifacts identify applicable sources;
-
FX logical elements can be identified where applicable;
-
implementation concerns can be identified where no direct FX logical element applies; and
-
unexplained baseline artifacts can be detected.
Traceability
This requirement establishes backward traceability from Phase 0 implementation artifacts to their FX logical or implementation sources.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.