dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-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
dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/08/19 18:09] nick_didodido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/08/19 18:11] (current) nick_dido
Line 3: Line 3:
 [[dido:03-dido-te:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]] [[dido:03-dido-te:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]
  
-This section identifies the requirements governing the operation of the capabilities, services, and realizations that satisfy the requirements of this specification.+This section identifies the requirements governing the operation of the capabilities, services, and realizations that satisfy this specification's requirements.
  
 Operational Requirements address the conditions under which distributed verification and testing operate across organizational, administrative, technical, jurisdictional, and governance boundaries. Operational Requirements address the conditions under which distributed verification and testing operate across organizational, administrative, technical, jurisdictional, and governance boundaries.
Line 11: Line 11:
 The requirements in this section derive from the source documents identified in Annex B. Some requirements derive directly from those sources. Others normalize or decompose source concepts into individually verifiable architectural obligations. The requirements in this section derive from the source documents identified in Annex B. Some requirements derive directly from those sources. Others normalize or decompose source concepts into individually verifiable architectural obligations.
  
-Operational Requirements are distinct from Functional Requirements. Functional Requirements define capabilities and behavior provided by the architecture. Operational Requirements define conditions, constraints, responsibilities, and operating characteristics applicable when those capabilities are used.+Operational Requirements are distinct from Functional Requirements. Functional Requirements define the capabilities and behavior the architecture provides. Operational Requirements define conditions, constraints, responsibilities, and operating characteristics applicable when those capabilities are used. 
 + 
 +===== Requirements ===== 
 + 
 +^ Requirement ID ^ Requirement Title ^ Primary Source Basis ^ 
 +| OPR-001 | Support Distributed Operation | <source basis> | 
 +| OPR-002 | Operate Across Governance Boundaries | <source basis> | 
 +| OPR-003 | Identify Applicable Governance Context | <source basis> | 
 +| OPR-004 | Preserve Governance Determinations | <source basis> | 
 +| OPR-005 | Escalate Unresolved Conflicts | <source basis> | 
 +| OPR-006 | Operate Across Organizational Boundaries | <source basis> | 
 +| OPR-007 | Preserve Traceability Across Boundaries | <source basis> | 
 +| OPR-008 | Preserve Evidence Across Boundaries | <source basis> |
  
 ===== Contents ===== ===== Contents =====
  • dido/03-dido-te/99-annexes/annex-c-requirements/02-operational-requirements/start.txt
  • Last modified: 2026/08/19 18:11
  • by nick_dido