SIP-056 — RFP Traceability Map

Go to Annex C: Requirements

The Submission SHALL include a Traceability map covering every applicable mandatory requirement of this RFP.

A Traceability map provides a systematic means of determining whether the Submission addresses every applicable mandatory requirement. It enables evaluators to locate the corresponding specification content, understand how the requirement is satisfied, and identify omissions or incomplete responses.

Without a Traceability map, evaluating a large architectural Submission may depend on manual searches and subjective interpretation.

A conforming Submission demonstrates that:

1. A Traceability map is included
2. Each applicable mandatory requirement is represented by its stable identifier
3. The short title of each requirement is included
4. Each entry identifies one or more corresponding locations within the Submission
5. Each entry indicates how the requirement is satisfied
6. Satisfaction status can be determined for each requirement
7. Inapplicable requirements, if permitted, include an applicability explanation
8. Incompletely satisfied requirements are explicitly identified
9. References within the map resolve to identifiable submission content
10. No applicable mandatory requirement is omitted

This requirement governs the Traceability-map deliverable. SIP-057 defines the required mappings between individual requirements and specification content. SIP-058 governs the disclosure of incomplete satisfaction.

Use the following syntax to include the authoritative Statement on another wiki page:

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-056-rfp-traceability-map#Statement&noheader&nofooter&noeditbtn}}