Annex C: Requirements

Go to Annexes

Annex C contains the canonical requirements register for Crucible.

The requirements are organized according to the requirement categories established in the Crucible System Requirements Specification. Each requirement has a stable identifier and resides on a separate page so that architecture pages, implementation artifacts, tests, Evidence, and other records can reference the requirement through a stable URI.

The requirements register distinguishes between:

The governance status of a requirementThe delivery phase associated with a requirementThe implementation status of Crucible relative to a requirementThe architecture and operational concepts that support a requirementThe verification activities used to determine whether Crucible satisfies a requirementThe original System Requirements Specification provides the source baseline for this register. Annex C becomes the maintained representation of the Crucible requirements as the register is reviewed, corrected, and expanded.

Requirement Categories

Requirement Page Structure

Each requirement page uses the following sections where applicable:

StatementSourceRationaleApplies ToVerificationTraceabilityConOps RelationshipDelivery PhaseImplementation StatusRequirement Status

Normative Language

Requirement statements use the following normative terms:

SHALL identifies a mandatory requirementSHALL NOT identifies a mandatory prohibitionMAY identifies a permitted capability or actionSHOULD identifies a recommendation when advisory language remains appropriateA requirement page may editorially correct the original source statement for terminology, atomicity, clarity, or normative style without changing its approved intent.

Requirement Status

Requirement Status identifies the governance state of the requirement.

Possible states include:

DraftProposedApprovedDeprecatedSupersededWithdrawn

Implementation Status

Implementation Status identifies the state of Crucible relative to the requirement.

Possible states include:

ImplementedPartially ImplementedDemonstratedPlannedPhase 2Strategic UnscheduledUnsupportedNot AssessedRequirement Status and Implementation Status remain separate. An approved requirement may remain planned, partially implemented, or unsupported.

Contents

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