SIP-057 — Requirement-to-Specification Traceability [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== SIP-057 — Requirement-to-Specification Traceability ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

The [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] map SHALL link each applicable mandatory requirement associated with [[public:00-sip-ra:05-general-requirements-on-proposals:start|Section 5 General Requirements on Proposals]] and [[public:00-sip-ra:06-specific-requirements-on-proposals:start|Section 6 Specific Requirements on Proposals]] to one or more locations within the Submission and SHALL identify how each requirement is satisfied.

===== Rationale =====

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.

===== Evaluation Criteria =====

A conforming Submission demonstrates that:

  - Each applicable mandatory requirement associated with Section 5 is represented
  - Each applicable mandatory requirement associated with Section 6 is represented
  - Every represented requirement is identified by its authoritative requirement identifier
  - Each requirement links to one or more specific locations within the Submission
  - Referenced locations are sufficiently precise to support direct review
  - Each entry explains how the referenced content satisfies the requirement
  - Multiple submission locations are identified when satisfaction depends on more than one location
  - Relationships remain valid in the submitted version of the specification
  - The Traceability map distinguishes complete, incomplete, and inapplicable responses
  - Evaluators can navigate from a requirement to the corresponding submission content

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability}}

===== Notes for Editors =====

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:

<code dokuwiki>
{{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>