| Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start [2026/07/16 07:59] – created nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start [2026/07/16 12:25] (current) – nick_dido |
|---|
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]] | [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]] |
| |
| The Configuration Management requirements define the behaviors that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs to create, validate, maintain, version, select, compare, and apply controlled configuration information. | The [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_management|Configuration Management]] [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] represents infrastructure through [[dido:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|Declarative Configuration]], treats [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] as [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_as_code|Infrastructure as Code]], reuses [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprints]], resolves environment inheritance, and preserves configuration [[dido:99_annexes:annex-b-terms-and-definitions:r:revision_history|Revision History]]. |
| |
| These requirements establish the configuration controls required to preserve consistency, [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] throughout the [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]. | Together, these [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] establish controlled and reusable configuration representations that contribute to [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. |
| |
| ===== Contents ===== | ===== Contents ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-001|FR-CFG-001]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-002|FR-CFG-002]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-003|FR-CFG-003]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-004|FR-CFG-004]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-005|FR-CFG-005]] | |
| |
| {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management#1|js navbar nocookie maxjs#1 id#crucible_configuration_management_requirements_nav}} | {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management#1|js navbar nocookie maxjs#1 id#crucible_configuration_management_requirements_nav}} |
| ===== Notes for Editors ===== | ===== Notes for Editors ===== |
| |
| The individual requirement pages should retain the stable identifiers ''FR-CFG-001'' through ''FR-CFG-005''. | The individual [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|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. | 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. | 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. | Normalized Statements should use direct, testable behavior and should identify the applicable [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]], operation, and required result. |
| | |
| | Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations. |
| |
| Incoming traceability should use the wiki Backlinks function rather than a manually maintained list. | Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list. |
| |
| To reference a requirement Statement from another wiki page, insert: | To reference a requirement Statement from another wiki page, insert: |