SIP-058 — Incomplete Requirement Disclosure

Go to Annex C: Requirements

The Submission SHALL identify each applicable mandatory requirement that it does not fully satisfy and SHALL provide the reason for the incomplete satisfaction.

Explicit disclosure of incomplete satisfaction prevents omissions or partial responses from being mistaken for complete conformance. It enables evaluators to understand the nature, extent, and consequences of each identified gap.

Providing the reason for incomplete satisfaction supports consistent evaluation but does not change the normative requirement or make an incomplete response conformant.

A conforming Submission demonstrates that:

1. Each applicable mandatory requirement that is not fully satisfied is identified
2. The authoritative requirement identifier is provided
3. The degree of satisfaction can be determined
4. The unsatisfied portion of the requirement is described
5. The reason for incomplete satisfaction is provided
6. Affected architectural elements or submission artifacts are identified
7. Dependencies and consequences associated with the gap are described
8. Any proposed resolution or future work is distinguishable from the submitted solution
9. No claim of complete satisfaction is made for an incompletely satisfied requirement

Disclosure under SIP-058 does not waive, modify, or satisfy the affected mandatory requirement. It also does not establish that a Submission containing the disclosed gap is acceptable under the applicable OMG process.

The Traceability map should identify incomplete satisfaction using a consistent status and should link to the explanation required by this requirement.

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

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-058-incomplete-requirement-disclosure#Statement&noheader&nofooter&noeditbtn}}