| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start [2026/07/16 12:18] – nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start [2026/07/17 00:23] (current) – nick_dido |
|---|
| [[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]] | [[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]] |
| |
| The [[functional_requirement|Functional Requirements]] define the behaviors that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs to configure, build, deploy, manage, test, assess, transfer, and operate infrastructure across supported environments. | The [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|Functional Requirements]] define the behaviors that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs to configure, build, deploy, manage, test, assess, transfer, and operate infrastructure across supported environments. |
| |
| These requirements refine the [[dido:99_annexes:annex-b-terms-and-definitions:m:mission_objective|Mission Objectives]] and [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_requirement|Operational Requirements]] into functional behavior that can be allocated to architecture components, implemented, and verified. | These requirements refine the [[dido:99_annexes:annex-b-terms-and-definitions:m:mission_objective|Mission Objectives]] and [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_requirement|Operational Requirements]] into functional behavior that can be allocated to architecture components, implemented, and verified. |
| |
| ===== Contents ===== | ===== Contents ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|C.3.1 Configuration Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:start|C.3.2 Image Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|C.3.3 Deployment Orchestration]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:start|C.3.4 Multi-Cloud Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|C.3.5 Air-Gapped Operations]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|C.3.6 Compliance Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-07-test-framework-integration:start|C.3.7 Test Framework Integration]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|C.3.8 DevSecOps Integration]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|C.3.9 Baseline Composition and Workspace]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|C.3.10 Dependency Capture and Offline Transfer]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:start|C.3.11 Management Interfaces]] | |
| |
| {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements#1|js navbar nocookie maxjs#2 id#crucible_functional_requirements_nav}} | {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements#1|js navbar nocookie maxjs#2 id#crucible_functional_requirements_nav}} |