C.3 Functional Requirements

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

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.

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