====== GPR-005 — Precise and Functionally Complete Submission ======
[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]
===== Statement =====
The Submission SHALL be precise and functionally complete.
===== Requirement Level =====
Mandatory
===== Rationale =====
A precise Submission defines its normative concepts, relationships, constraints, behaviors, and conformance conditions without material ambiguity.
A functionally complete Submission addresses the capabilities and responsibilities within the scope of the RFP with sufficient detail to support technical evaluation, independent implementation, and conformance assessment.
===== Evaluation Criteria =====
A conforming Submission demonstrates that:
- Normative concepts and architectural constructs are identified and defined
- Relationships among normative constructs are specified
- Applicable constraints and conditions are stated
- Required architectural responsibilities are allocated
- Behavior relevant to implementation and conformance can be determined
- Mandatory requirements are addressed
- Required specification sections and normative artifacts are included
- Undefined terms, unresolved placeholders, and contradictory statements do not prevent implementation
- Normative and nonnormative material can be distinguished
- Independent implementers can determine the capabilities and responsibilities required by the specification
- Conformance assessors can determine whether the applicable requirements are satisfied
===== Referenced By =====
{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-005-precise-and-functionally-complete-submission}}
===== Notes for Editors =====
Functional completeness applies to the scope established by the RFP. It does not require a Submission to define capabilities explicitly identified as out of scope.
GPR-005 applies to the complete Submission. SIP-042 applies specifically to the completeness of the proposed Reference Architecture specification. SIP-048 applies specifically to the formal precision of its Platform Independent Model.
Use the following syntax to include the authoritative Statement on another wiki page:
{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-005-precise-and-functionally-complete-submission#Statement&noheader&nofooter&noeditbtn}}
----
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.