This is an old revision of the document!
C.3.1 Configuration Management
Go to Crucible Functional Requirements
The Configuration Management requirements define the behaviors that Crucible performs to create, validate, maintain, version, select, compare, and apply controlled configuration information.
These requirements establish the configuration controls required to preserve consistency, Provenance, Reproducibility, and Traceability throughout the Operational Lifecycle.
Contents
Notes for Editors
The individual requirement pages should retain the stable identifiers FR-CFG-001 through FR-CFG-005.
Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.
The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.
Normalized Statements should use direct, testable behavior and should identify the applicable configuration artifact, controlled input, operation, result, and acceptance criteria.
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.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.