The Traceability map SHALL link each applicable mandatory requirement associated with Section 5 General Requirements on Proposals and Section 6 Specific Requirements on Proposals to one or more locations within the Submission and SHALL identify how each requirement is satisfied.
Requirement identifiers alone do not demonstrate satisfaction. Evaluators need direct relationships between each applicable requirement and the architectural models, definitions, constraints, explanations, or other submission material that addresses it.
Combining location references with a description of satisfaction makes the Traceability map useful for completeness review, technical evaluation, conformance analysis, and later specification maintenance.
A conforming Submission demonstrates that:
Every normative requirement associated with Sections 5 and 6 should have an authoritative Annex C record. The section pages should display the authoritative Statements by transclusion.
The Traceability map should reference the stable Annex C requirement identifier even when a requirement appears contextually in Sections 5 or 6.
Use the following syntax to include the authoritative Statement on another wiki page:
{{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.