C.3 Functional Requirements

Go to Crucible Requirements

The Functional Requirements define the behaviors that Crucible performs to configure, build, deploy, manage, test, assess, transfer, and operate infrastructure across supported environments.

These requirements refine the Mission Objectives and Operational Requirements into functional behavior that can be allocated to architecture components, implemented, and verified.

Each Functional Requirements subsection should remain a separate namespace index page containing links to its individual requirement leaf pages.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

Each requirement page should retain its stable requirement identifier and preserve the original source statement from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should avoid weak verbs, undefined qualifiers, and implementation-specific language unless the implementation constraint forms part of the approved requirement.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.