Differences

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

--- dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/08/07 06:01] – created nick_dido
+++ dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/08/19 18:11] (current) – nick_dido
@@ Line 1: / Line 1: @@
 ====== C.2 Operational Requirements ======
-[[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]]
-===== Overview =====
+This section identifies the requirements governing the operation of the capabilities, services, and realizations that satisfy this specification's requirements.
-Operational Requirements specify the required behavior of [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] during its preparation, operation, administration, monitoring, recovery, and controlled termination.
+Operational Requirements address the conditions under which distributed verification and testing operate across organizational, administrative, technical, jurisdictional, and governance boundaries.
-These requirements translate the [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Mission Objectives]] into operationally observable obligations. They establish what DIDO-TE must accomplish under defined operating conditions without prescribing a particular implementation.
+These requirements govern operational behavior and constraints without prescribing a particular product, implementation, or realization technology.
-===== Scope =====
+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 address the behavior and control of DIDO-TE during its [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]], including:
+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.
-  * Preparation for operation
+===== Requirements =====
-  * Establishment and maintenance of required operating conditions
-  * Initiation, execution, monitoring, and termination of testing activities
-  * Management of operational state
-  * Control of authorized operational actions
-  * Detection and handling of operational errors and exceptions
-  * Recovery from interrupted or failed operations
-  * Preservation of operational records, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Operation within connected, disconnected, and air-gapped environments
-Operational Requirements do not prescribe implementation technologies, product selections, internal software structures, or deployment-specific configurations unless an operational obligation depends upon such a constraint.
+^ 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> |
-===== Requirement Organization =====
+===== Contents =====
-This section organizes Operational Requirements as a hierarchy.
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-001-support-distributed-operation|OPR-001 — Support Distributed Operation]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-002-operate-across-governance-boundaries|OPR-002 — Operate Across Governance Boundaries]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-003-identify-applicable-governance-context|OPR-003 — Identify Applicable Governance Context]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-004-preserve-governance-determinations|OPR-004 — Preserve Governance Determinations]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-005-escalate-unresolved-conflicts|OPR-005 — Escalate Unresolved Conflicts]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-006-operate-across-organizational-boundaries|OPR-006 — Operate Across Organizational Boundaries]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-007-preserve-traceability-across-boundaries|OPR-007 — Preserve Traceability Across Boundaries]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements:opr-008-preserve-evidence-across-boundaries|OPR-008 — Preserve Evidence Across Boundaries]]
-A non-leaf requirement establishes a broader operational obligation and provides the context for its derived requirements. Its child requirements decompose that obligation into independently verifiable statements.
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements#1|js navbar nocookie maxjs#2 id#dido_te_operational_requirements_nav}}
-A leaf requirement contains the normative Statement and the information needed to establish its derivation, rationale, applicability, and verification.
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements#1|js navbar nocookie maxjs#2 id#dido_te_operational_requirements_nav}}
-The requirement pages constitute the authoritative requirement records. This index presents the hierarchy dynamically and does not reproduce requirement statements or titles as hard-coded content.
+----
-===== Contents =====
+===== Notes for Editors =====
+<todo>Derive the Operational Requirements from the applicable source requirements, governance constraints, operational concepts, and ConOps material before creating individual OPR requirement pages.</todo>
+<todo>Add explicit links to proposed OPR requirement pages under Contents while the requirement set is being created. Remove the explicit links after the pages are finalized because the indexmenu automatically discovers them.</todo>
+Operational Requirements use the ''OPR'' requirement prefix.
+Do not place Test Environment, Node, Test Definition, Test Execution, or other capability-specific Functional Requirements in this section.
-{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:02-operational-requirements#2|js navbar nocookie maxjs#2 id#dido_te_operational_requirements_nav}}
+Do not use Operational Requirements to prescribe Crucible, DevSecOps, or another specific realization unless the requirement explicitly governs interoperability with that realization.
 ----