| Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/07/16 01:33] – created nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:start [2026/07/16 12:13] (current) – [C.2 Operational Requirements] 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 Operational Requirements define the actors, deployment environments, operational classifications, concurrency needs, and management scope within which [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operates. | The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_requirement|Operational Requirements]] define the actors, deployment environments, operational classifications, concurrency needs, and management scope within which [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operates. |
| |
| These requirements establish the operational conditions that constrain and guide the functional, security, reliability, performance, maintainability, data management, and interoperability requirements. | These requirements establish the operational conditions that constrain and guide the functional, security, reliability, performance, maintainability, data management, and interoperability requirements. |
| |
| ===== Contents ===== | ===== Contents ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001 — Operational Roles]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002 — Deployment Environments]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003|OR-003 — Classified and Unclassified Environments]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004 — Concurrent Environment Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] | |
| |
| {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements#1|js navbar nocookie maxjs#1 id#crucible_operational_requirements_nav}} | {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements#1|js navbar nocookie maxjs#1 id#crucible_operational_requirements_nav}} |
| |
| ===== Requirement Summary ===== | |
| |
| ^ Requirement ^ Source Statement ^ | |
| | [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001]] | The system SHALL support operation by Developers, DevSecOps Engineers, Platform Engineers, System Administrators, Security Engineers, and Compliance Officers | | |
| | [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002]] | The system SHALL support deployment into AWS, Azure, Google Cloud Platform, VMware, OpenShift, Kubernetes, Bare Metal Infrastructure, and Air-Gapped Environments | | |
| | [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003|OR-003]] | The system SHALL support classified and unclassified deployment environments | | |
| | [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004]] | The system SHALL support deployment and management of multiple environments simultaneously | | |
| | [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005]] | The system SHALL support centralized management of distributed environments | | |
| |
| ===== Assessment Approach ===== | |
| |
| Each Operational Requirement page: | |
| |
| - Preserves the source statement | |
| - Evaluates the source statement using the Specification Discipline and Authoring framework | |
| - Confirms and classifies defects using the Common Specification Weakness Enumeration | |
| - Provides a normalized requirement statement | |
| - Identifies applicable actors, environments, activities, and constraints | |
| - Defines ordered verification statements | |
| - Identifies outgoing traceability | |
| - Uses wiki backlinks for incoming traceability | |
| - Identifies additional concepts that require entries in the shared Terms and Definitions corpus | |
| |
| ===== Shared Terms and Definitions ===== | |
| |
| The Operational Requirements use or introduce concepts that should link to the shared Terms and Definitions corpus, including: | |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_environment|Operational Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_role|Operational Role]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:distributed_environment|Distributed Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:classified_environment|Classified Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:u:unclassified_environment|Unclassified Environment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:concurrent_operation|Concurrent Operation]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:centralized_management|Centralized Management]] | |
| |
| ===== Notes for Editors ===== | ===== Notes for Editors ===== |
| |
| The individual requirement pages should retain the stable identifiers `OR-001` through `OR-005`. | The individual requirement pages should retain the stable identifiers ''OR-001'' through ''OR-005''. |
| |
| The source statements should preserve the wording from the controlling System Requirements Specification. | The source statements should preserve the wording from the controlling System Requirements Specification. |
| Incoming traceability should use the wiki Backlinks function rather than a manually maintained list. | Incoming traceability should use the wiki Backlinks function rather than a manually maintained list. |
| |
| Individual requirement links should omit a trailing `:start` when the requirement record is a leaf page. | To reference the requirement Statement from another wiki page, insert: |
| | |
| | <code dokuwiki> |
| | {{section><namespace>#Statement&noheader&nofooter&noeditbtn}} |
| | </code> |
| | |
| | Replace ''<namespace>'' with the namespace of the requirement page to reference. |
| |
| Do not rename requirement pages after external citation unless a redirect or move plan is in place. | Do not rename requirement pages after an external citation unless a redirect or move plan is in place. |
| |
| ---- | ---- |