Annex C: Requirements [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Annex C: Requirements ======

[[dido:02-crusible:99-annexes:start|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 requirement
  * The delivery phase associated with a requirement
  * The implementation status of Crucible relative to a requirement
  * The architecture and operational concepts that support a requirement
  * The verification activities used to determine whether Crucible satisfies a requirement

The 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 Page Structure =====

Each requirement page uses the following sections where applicable:

  * Statement
  * Source
  * Rationale
  * Applies To
  * Verification
  * Traceability
  * ConOps Relationship
  * Delivery Phase
  * Implementation Status
  * Requirement Status

===== Normative Language =====

Requirement statements use the following normative terms:

  * **SHALL** identifies a mandatory requirement
  * **SHALL NOT** identifies a mandatory prohibition
  * **MAY** identifies a permitted capability or action
  * **SHOULD** identifies a recommendation when advisory language remains appropriate

A 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:

  * Draft
  * Proposed
  * Approved
  * Deprecated
  * Superseded
  * Withdrawn

===== Implementation Status =====

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

Possible states include:

  * Implemented
  * Partially Implemented
  * Demonstrated
  * Planned
  * Phase 2
  * Strategic Unscheduled
  * Unsupported
  * Not Assessed

Requirement Status and Implementation Status remain separate. An approved requirement may remain planned, partially implemented, or unsupported.

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements#1|js navbar nocookie maxjs#4 id#crucible_annex_c_requirements_nav}}

----

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