Differences

This shows you the differences between two versions of the page.

--- public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-7-rfp-traceability:start [2026/09/12 18:34] – ↷ Links adapted because of a move operation nick_dido
+++ public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-7-rfp-traceability:start [2026/09/14 18:55] (current) – [Requirements] nick_dido
@@ Line 3: / Line 3: @@
 [[public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]]
-Traceability establishes an explicit correspondence between the mandatory requirements of this RFP and the submitted specification.
+[[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] establishes an explicit correspondence between the requirements of this RFP and the locations within the Submission where those requirements are addressed.
-  - Proposals SHALL include a traceability map.
+===== Requirements =====
-  - Proposals SHALL link each mandatory requirement defined in [[public:00-sip-ra:05-general-requirements-on-proposals:start|Section 5 General Requirements on Proposals]] to one or more specific locations within the submitted specification.
-  - Proposals SHALL link each mandatory requirement defined in [[public:00-sip-ra:06-specific-requirements-on-proposals:start|Section 6 Specific Requirements on Proposals]] to one or more specific locations within the submitted specification.
-  - Proposals SHALL identify how each mandatory requirement is satisfied within the submitted architecture.
-  - Proposals SHALL identify any mandatory requirement that is not fully satisfied and provide justification.
+^ Requirement ^ Statement ^
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-056-rfp-traceability-map|SIP-056 — RFP Traceability Map]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-056-rfp-traceability-map#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability|SIP-057 — Requirement-to-Specification Traceability]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability#Statement&noheader&nofooter&noeditbtn}} |
+| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-058-incomplete-requirement-disclosure|SIP-058 — Incomplete Requirement Disclosure]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-058-incomplete-requirement-disclosure#Statement&noheader&nofooter&noeditbtn}} |
 ===== Note =====
-> A consolidated corpus of mandatory requirements is provided in Appendix C for convenience. The normative source of all requirements remains Sections 5 and 6.
+> Annex C provides the authoritative requirement records for this RFP. Sections 5 and 6 organize those requirements within their applicable context and display their authoritative Statements by transclusion from Annex C.
----
+> Identifying an incompletely satisfied mandatory requirement does not make the Submission conformant with that requirement or waive the requirement. Any determination concerning acceptability remains subject to the applicable OMG process.
+===== Notes for Editors =====
+The links to SIP-056 through SIP-058 provide temporary access to their individual Annex C requirement pages while those records are being created and reviewed.
+After those records are complete, replace each locally maintained Statement with a transclusion of its authoritative Statement.
+Every normative requirement in Sections 5 and 6 should have a corresponding authoritative record in Annex C. Section pages should transclude the Statement from that record rather than maintain a separate copy.
+SIP-056 requires the traceability-map deliverable. SIP-057 defines its required mappings and satisfaction information. SIP-058 requires transparent identification of requirements that are not fully satisfied.
+----
 <WRAP centeralign>
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP>