| Both sides previous revision Previous revision Next revision | Previous revision |
| public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-6-implementation-conformance-model:start [2026/09/12 18:33] – ↷ Page moved from dido:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-6-implementation-conformance-model:start to public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-6-impleme nick_dido | public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-6-implementation-conformance-model:start [2026/09/14 18:52] (current) – [Requirements] nick_dido |
|---|
| ====== 6.4.6 Implementation Conformance Model ====== | ====== 6.4.6 Implementation Conformance Model ====== |
| |
| [[dido:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]] | [[public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]] |
| |
| The conformance model defines the conditions under which an implementation conforms to the [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] and identifies inspectable conformance points. | The conformance model defines the conditions under which an implementation conforms to the proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. It identifies objectively inspectable conformance points and distinguishes mandatory architectural elements from optional architectural elements. |
| |
| - Proposals SHALL define a conformance model specifying the conditions under which an implementation conforms to the Reference Architecture. | ===== Requirements ===== |
| - Proposals SHALL define conformance points that are objectively inspectable and independent of implementation technology. | |
| - Proposals SHALL define mandatory and optional architectural elements relevant to implementation conformance. | ^ Requirement ^ Statement ^ |
| - Proposals SHALL define conformance independently of any specific transport protocol, exchange framework, modeling language, or deployment topology. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-054-implementation-conformance-model|SIP-054 — Implementation Conformance Model]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-054-implementation-conformance-model#Statement&noheader&nofooter&noeditbtn}} | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-055-architectural-element-conformance-classification|SIP-055 — Architectural Element Conformance Classification]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-055-architectural-element-conformance-classification#Statement&noheader&nofooter&noeditbtn}} | |
| | ===== Required Coverage ===== |
| | |
| | The conformance model includes the conformance information governed by the following requirements: |
| | |
| | ^ Requirement ^ Required Conformance Information ^ |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-021-independent-conformance-requirements|SIP-021 — Independent Conformance Requirements]] | Conformance requirements defined independently of Interface interaction definitions | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-022-technology-independent-conformance-points|SIP-022 — Technology-Independent Conformance Points]] | Objectively inspectable conformance points independent of implementation technology | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-029-implementation-and-deployment-independence|SIP-029 — Implementation and Deployment Independence]] | Independence from specific implementation technologies, deployment topologies, and System architectures | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-030-tool-and-technology-neutrality|SIP-030 — Tool and Technology Neutrality]] | Independence from specific modeling languages, transport frameworks, and vendor tooling environments | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-041-modeling-and-tooling-conformance-neutrality|SIP-041 — Modeling and Tooling Conformance Neutrality]] | Implementation conformance independent of modeling languages, model-interchange formats, and vendor tooling environments | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-048-platform-independent-model-formal-precision|SIP-048 — Platform Independent Model Formal Precision]] | Formal precision sufficient to support independent implementation and conformance assessment | |
| | |
| | ===== Notes for Editors ===== |
| | |
| | The links to SIP-054 and SIP-055 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. |
| | |
| | SIP-054 requires a conformance model and establishes its purpose. SIP-055 requires the conformance model to distinguish mandatory, optional, and conditional architectural elements. |
| | |
| | The requirements listed under Required Coverage govern the conformance model's independence, inspectability, neutrality, and formal precision. |
| | |
| | The Required Coverage table provides a nonnormative summary. The corresponding Annex C requirement records remain authoritative. |
| |
| ---- | ---- |
| © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| </WRAP> | </WRAP> |
| |