6.7 Traceability Baseline

Go To Phase 0 Implementation Preconditions

The Phase 0 traceability baseline must be in place before implementation artifacts are authored, generated, or accepted.

The traceability baseline defines how implementation artifacts identify the logical elements or implementation concerns they realize or support. It includes conventions for file headers, generated-file metadata, IDL comments, topic mapping tables, repository documentation, script documentation, and review records.

The traceability baseline must support forward and backward review. A reviewer must be able to trace from a Part 3 FX logical element to the Phase 0 implementation artifact that realizes it, and from a Phase 0 implementation artifact back to the Part 3 FX logical element or implementation concern that justifies it.

This precondition prevents orphan implementation artifacts. Contributors and reviewers must not include any file, topic, IDL structure, generated type, script, configuration file, or module in the Phase 0 implementation baseline unless the artifact identifies its architectural purpose.