dido:03-dido-te:99-annexes:annex-c-requirements:11-conformance-requirements:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:11-conformance-requirements:start [2026/08/17 13:52] – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:01-conformance-requirements:start to dido:03-dido-te:99-annexes:annex-c-requirements:11-conformance-requirements:start nick_didodido:03-dido-te:99-annexes:annex-c-requirements:11-conformance-requirements:start [2026/08/19 17:50] (current) nick_dido
Line 1: Line 1:
-====== C.Conformance Requirements ======+====== C.11 Conformance Requirements ======
  
-[[dido:03-dido-te:99-annexes:annex-c-requirements:start|Return to Annex C: Requirements]]+[[dido:03-dido-te:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]
  
-This section identifies the DIDO-TE requirements governing architectural conformance.+This section identifies the requirements governing architectural conformance to this specification.
  
-The requirements in this section derive from the applicable source documents identified in Annex B. Some requirements derive directly from those sources. Others decompose higher-level requirements into individually verifiable architectural obligations. Each requirement is maintained as an individual leaf page with a stable requirement identifier and URI.+The requirements in this section derive from the applicable source documents identified in Annex B. Some requirements derive directly from those sources. Others decompose higher-level requirements into individually verifiable architectural obligations. 
 + 
 +Conformance requirements define how an implementation, realization, architectural capability, or conformance profile demonstrates satisfaction of the applicable requirements of this specification without prescribing a particular product, technology, or implementation approach. 
 + 
 +Each requirement has a stable requirement identifier and URI.
  
 ===== Requirements ===== ===== Requirements =====
Line 22: Line 26:
 ===== Requirement Pages ===== ===== Requirement Pages =====
  
-{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-conformance-requirements#1|js navbar nocookie maxjs#1 id#dido_te_conformance_requirements_nav}}+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:11-conformance-requirements#1|js navbar nocookie maxjs#1 id#dido_te_conformance_requirements_nav}}
  
 ---- ----
  • dido/03-dido-te/99-annexes/annex-c-requirements/11-conformance-requirements/start.1786999939.txt.gz
  • Last modified: 2026/08/17 13:52
  • by nick_dido