====== C.3 Functional Requirements ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

This section identifies the Functional Requirements governing the capabilities and behavior required to support distributed verification and testing.

Functional Requirements define what the architecture provides without prescribing a particular product, implementation, or realization technology.

The requirements are organized into subordinate requirement families based on architectural subject area. A requirement family may contain non-leaf requirement groups that organize subordinate obligations, individual leaf requirements that establish independently verifiable normative obligations, or both.

The requirements in these families derive from the applicable source documents identified in Annex B. Some requirements derive directly from those sources. Others normalize or decompose source concepts into individually verifiable architectural obligations.

===== Contents =====

  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start|C.3.1 Test Environment Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:start|C.3.2 Node Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:start|C.3.3 Twin Node Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:start|C.3.4 Virtual Network and Communication Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:start|C.3.5 State and Time Control Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-06-test-definition-requirements:start|C.3.6 Test Definition Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-07-test-execution-requirements:start|C.3.7 Test Execution Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-08-record-and-playback-requirements:start|C.3.8 Record and Playback Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-and-comparison-requirements:start|C.3.9 Baseline and Comparison Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-10-validation-requirements:start|C.3.10 Validation Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-11-monitoring-and-evidence-requirements:start|C.3.11 Monitoring and Evidence Requirements]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-12-catalog-and-reuse-requirements:start|C.3.12 Catalog and Reuse Requirements]]

{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements#1|js navbar nocookie maxjs#2 id#dido_te_functional_requirements_nav}}

----

===== Notes for Editors =====

The explicit links under Contents remain while the subordinate Functional Requirement category pages are being created and reviewed. After all planned category pages exist, the explicit links may be removed because the ''indexmenu'' automatically discovers them.

Preserve stable requirement identifiers when moving or reorganizing Functional Requirement pages.

Do not allocate Functional Requirements directly to Crucible, DevSecOps, or another realization within the requirement Statement. Maintain realization relationships through Traceability.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>