GPR-005 — Precise and Functionally Complete Submission

Go to Annex C: Requirements

The Submission SHALL be precise and functionally complete.

Mandatory

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.

A conforming Submission demonstrates that:

1. Normative concepts and architectural constructs are identified and defined
2. Relationships among normative constructs are specified
3. Applicable constraints and conditions are stated
4. Required architectural responsibilities are allocated
5. Behavior relevant to implementation and conformance can be determined
6. Mandatory requirements are addressed
7. Required specification sections and normative artifacts are included
8. Undefined terms, unresolved placeholders, and contradictory statements do not prevent implementation
9. Normative and nonnormative material can be distinguished
10. Independent implementers can determine the capabilities and responsibilities required by the specification
11. Conformance assessors can determine whether the applicable requirements are satisfied

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}}