C.2 Operational Requirements

Go to Annex C — Requirements

Overview

Operational Requirements specify the required behavior of DIDO-TE during its preparation, operation, administration, monitoring, recovery, and controlled termination.

These requirements translate the Mission Objectives into operationally observable obligations. They establish what DIDO-TE must accomplish under defined operating conditions without prescribing a particular implementation.

Scope

Operational Requirements address the behavior and control of DIDO-TE during its Operational Lifecycle, including:

Preparation for operationEstablishment and maintenance of required operating conditionsInitiation, execution, monitoring, and termination of testing activitiesManagement of operational stateControl of authorized operational actionsDetection and handling of operational errors and exceptionsRecovery from interrupted or failed operationsPreservation of operational records, Evidence, and TraceabilityOperation within connected, disconnected, and air-gapped environmentsOperational 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 Organization

This section organizes Operational Requirements as a hierarchy.

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.

A leaf requirement contains the normative Statement and the information needed to establish its derivation, rationale, applicability, and verification.

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.