| Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/07/15 12:54] – created nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/07/22 12:32] (current) – nick_dido |
|---|
| ====== MO-006 ====== | ====== MO-006 — Infrastructure Lifecycle Management ====== |
| |
| [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] | [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] |
| |
| ===== Statement ===== | ===== Original Requirement ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform the applicable [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activities for each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] from initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] through [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] while preserving the applicable environment state, history, [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. | > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] |
| |
| ===== Source Statement ===== | ===== Assessment of Original Requirement ===== |
| |
| > The system SHALL support infrastructure lifecycle management from initial deployment through retirement. | The Original Requirement preserves the approved mission objective but does not express independently testable normative statements. |
| | |
| ===== Source ===== | |
| | |
| Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-006. | |
| | |
| ===== Assessment ===== | |
| | |
| The source statement expresses the approved mission objective but does not provide a fully testable formulation. | |
| |
| The following Specification Discipline and Authoring findings apply: | The following Specification Discipline and Authoring findings apply: |
| |
| * **The system** does not use the defined system name | * **The system** does not use the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] |
| * **Support** is a weak verb that does not identify the behavior [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs | * **Support** is a weak verb that does not identify an observable behavior performed by Crucible |
| * **Infrastructure lifecycle management** does not identify the lifecycle activities, managed information, responsible components, or required outcomes | * **Infrastructure** does not identify the lifecycle subject as an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] |
| * **Initial deployment** does not identify the event that begins the managed lifecycle | * **Infrastructure lifecycle management** combines multiple independently testable behaviors |
| * **Retirement** does not identify the required termination, archival, preservation, or resource disposition activities | * **Initial deployment** introduces a separate lifecycle-initiation obligation |
| * The source statement does not identify which environment records must remain available throughout and after the lifecycle | * **Through retirement** introduces a separate terminal lifecycle obligation |
| * The source statement does not define the acceptance criteria for lifecycle transitions | |
| * The source statement does not distinguish the lifecycle of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] from the lifecycle of a [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]], or other [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] | |
| |
| The normalized Statement replaces the weak verb with **perform**, identifies the managed [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]], bounds the lifecycle from initial deployment through retirement, and identifies the information that must remain preserved. | The Original Requirement does not identify: |
| |
| ===== Rationale ===== | * The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] associated with each Infrastructure Environment |
| | * The Operational Lifecycle revision associated with each Infrastructure Environment |
| | * The lifecycle state assigned when the Infrastructure Environment is created |
| | * The current lifecycle state of the Infrastructure Environment |
| | * The lifecycle transitions that Crucible performs |
| | * The conditions that permit each lifecycle transition |
| | * The conditions that permit [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] |
| | * The lifecycle records preserved for verification and Traceability |
| |
| An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] changes throughout its [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]. | The Original Requirement therefore requires: |
| |
| After initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]], an organization may need to: | * Replacement of **the system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] |
| | * Replacement of **support** with observable Crucible behavior |
| | * Identification of the lifecycle subject as an Infrastructure Environment |
| | * Association of each Infrastructure Environment with an identified Operational Lifecycle revision |
| | * Identification of the initial lifecycle state |
| | * Recording of the current lifecycle state |
| | * Execution of permitted lifecycle transitions |
| | * Retirement of the Infrastructure Environment when the Retirement conditions are satisfied |
| | * Confirmation that the derived requirements collectively preserve the complete intent of MO-006 |
| |
| * Validate the deployed environment | The decomposition preserves ''MO-006'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page. |
| * Apply configuration changes | |
| * Update [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | |
| * Apply security updates | |
| * Reassess compliance | |
| * Reconcile environment state | |
| * Recover failed operations | |
| * Restore an environment from a backup | |
| * Roll back an unsuccessful change | |
| * Replace or upgrade components | |
| * Preserve operational and compliance records | |
| * Retire the environment and dispose of its resources | |
| |
| Without controlled lifecycle management, an environment may diverge from its approved [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]], lose [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], accumulate configuration drift, or retain resources after the environment is no longer authorized. | ===== Proposed Statements ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] coordinates lifecycle activities through controlled [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]], versioned [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]], recorded lifecycle transitions, validation activities, and preserved [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. | The Original Requirement is decomposed into the following proposed replacement requirements: |
| |
| Each lifecycle transition should preserve the relationship among: | {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006#1|js navbar nocookie maxjs#1 id#crucible_mo_006_requirements_nav}} |
| |
| * The affected [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] | ===== Requirement Status ===== |
| * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] | |
| * The selected [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] revisions | |
| * The prior environment state | |
| * The resulting environment state | |
| * The authorized lifecycle action | |
| * The actor or automated process that initiated the action | |
| * The resulting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| ===== Applies To ===== | <todo>Review and approve the proposed decomposition of MO-006 into independently testable lifecycle association, initiation, state-recording, transition-execution, and Retirement requirements.</todo> |
| |
| This requirement applies to: | <todo>Determine whether MO-006a through MO-006e collectively supersede MO-006.</todo> |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | <todo>If MO-006a through MO-006e are accepted as the complete replacement for MO-006, mark MO-006 as superseded and preserve this page as the parent Traceability record.</todo> |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | |
| * Environment validation | |
| * Environment state | |
| * Lifecycle transitions | |
| * Configuration changes | |
| * State reconciliation | |
| * Backup and restoration | |
| * Recovery | |
| * Upgrades | |
| * Rollback | |
| * Compliance reassessment | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] | |
| * Resource disposition | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] | |
| |
| ===== Verification ===== | ---- |
| | ===== Issues ===== |
| |
| - Verification SHALL confirm that each tested [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] has a unique identifier | The following unresolved issues affect the decomposition of MO-006: |
| - Verification SHALL confirm that the lifecycle record identifies the initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| - Verification SHALL confirm that each tested lifecycle transition has a unique identifier | |
| - Verification SHALL confirm that each tested lifecycle transition identifies the applicable lifecycle activity | |
| - Verification SHALL confirm that each tested lifecycle transition identifies the prior environment state | |
| - Verification SHALL confirm that each tested lifecycle transition identifies the resulting environment state | |
| - Verification SHALL confirm that each tested lifecycle transition identifies the applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] | |
| - Verification SHALL confirm that each tested lifecycle transition identifies the applicable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] revisions | |
| - Verification SHALL confirm that each tested lifecycle transition records the actor or automated process that initiated the action | |
| - Verification SHALL confirm that each tested lifecycle transition records the execution result | |
| - Verification SHALL confirm that each successful lifecycle transition satisfies the applicable acceptance criteria | |
| - Verification SHALL confirm that each failed lifecycle transition preserves the last valid environment state or records the incomplete state | |
| - Verification SHALL confirm that recovery or rollback restores the environment to a defined valid state | |
| - Verification SHALL confirm that compliance reassessment records the applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]] | |
| - Verification SHALL confirm that backup and restoration preserve the applicable environment configuration, state, and records | |
| - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] terminates or transfers the applicable infrastructure resources according to the approved retirement criteria | |
| - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] preserves the records required by the applicable retention policy | |
| - Verification SHALL confirm that the lifecycle record preserves [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from initial deployment through retirement | |
| |
| Verification may include: | <todo>Identify the Operational Lifecycles that may be associated with an Infrastructure Environment.</todo> |
| |
| * Initial deployment tests | <todo>Define how Crucible identifies the Operational Lifecycle revision associated with an Infrastructure Environment.</todo> |
| * Environment validation tests | |
| * Configuration change tests | |
| * State reconciliation tests | |
| * Compliance reassessment tests | |
| * Upgrade tests | |
| * Upgrade rollback tests | |
| * Failed operation recovery tests | |
| * Backup tests | |
| * Restoration tests | |
| * Baseline revision transition tests | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] replacement tests | |
| * Deployment history inspection | |
| * Lifecycle record inspection | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] tests | |
| * Resource disposition inspection | |
| * Record retention inspection | |
| * Connected environment demonstrations | |
| * Disconnected environment demonstrations | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]] demonstrations | |
| * End-to-end [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] tests | |
| |
| The verification record SHALL identify: | <todo>Define the lifecycle state assigned when an Infrastructure Environment is created through an Infrastructure Deployment.</todo> |
| |
| - The tested [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] | <todo>Define the lifecycle states that Crucible records for an Infrastructure Environment.</todo> |
| - The environment identifier | |
| - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activities | |
| - The initial deployment record | |
| - The tested lifecycle transitions | |
| - The prior environment states | |
| - The resulting environment states | |
| - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | |
| - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] revisions | |
| - The initiating actors or automated processes | |
| - The applicable acceptance criteria | |
| - The execution results | |
| - The recovery or rollback results | |
| - The applicable backup and restoration records | |
| - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]] | |
| - The retirement record | |
| - The resource disposition results | |
| - The applicable retention policy | |
| - The retained records | |
| - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| ===== Outgoing Traceability ===== | <todo>Define the lifecycle transitions allocated to Crucible.</todo> |
| |
| This requirement is realized by: | <todo>Define the conditions that permit each lifecycle transition.</todo> |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:start|OR-001 through OR-005]] | <todo>Define the behavior required when a requested lifecycle transition is not permitted.</todo> |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:start|FR-IMG-001 through FR-IMG-006]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|FR-AG-001 through FR-AG-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|FR-COMP-001 through FR-COMP-010]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|FR-BAS-001 through FR-BAS-004]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|FR-DEPC-001 through FR-DEPC-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:06-logging-and-auditing-requirements:start|LOG-001 through LOG-007]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:07-reliability-requirements:start|REL-001 through REL-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:09-maintainability-requirements:start|MAINT-001 through MAINT-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:10-data-management-requirements:start|DATA-001 through DATA-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-003:start|KVP-003 — Improve deployment repeatability]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-004:start|KVP-004 — Improve compliance consistency]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-005:start|KVP-005 — Reduce configuration drift]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-007:start|KVP-007 — Reduce total cost of ownership for platform infrastructure]] | |
| |
| This requirement also relates to: | <todo>Define the conditions that permit Retirement of an Infrastructure Environment.</todo> |
| |
| * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] | <todo>Define the records preserved for lifecycle state changes, transitions, and Retirement.</todo> |
| * [[dido:02-crusible:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] | |
| * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] | |
| * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] | |
| * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] | |
| * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]] | |
| |
| ===== Referenced By ===== | <todo>Determine whether MO-006a through MO-006e provide complete coverage of the approved intent of MO-006.</todo> |
| |
| The wiki Backlinks function provides the current list of pages that reference `MO-006`. | ---- |
| | ===== Notes for Editors ===== |
| |
| Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list. | This page should retain the stable parent requirement identifier ''MO-006''. |
| |
| Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. | This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace. |
| |
| ===== ConOps Relationship ===== | The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces. |
| |
| The Crucible Concept of Operations describes Phase 1 as a [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] integrated command-line utility that performs build, compliance, dependency capture, and deployment activities. | The explicit child-page links should remain while the proposed decomposition is being developed. After the child pages have been created and finalized, the explicit links may be removed because the ''indexmenu'' displays the child requirement pages contained within the MO-006 namespace. |
| |
| The Phase 1 workflow: | This page preserves: |
| |
| * Retrieves controlled and versioned inputs | * The Original Requirement |
| * Composes selected [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | * The assessment of the Original Requirement |
| * Builds and hardens [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | * The reason for decomposition |
| * Captures dependencies and [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the proposed replacement requirements |
| * Performs [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | * The unresolved cross-cutting issues affecting the decomposition |
| * Executes predeployment and postdeployment activities | * The supersession decision |
| * Records deployment and compliance results | |
| * Tears down environments when they are no longer required | |
| |
| The ConOps primarily describes initial deployment and related Phase 1 execution. The broader [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] also includes modification, reassessment, recovery, restoration, upgrade, rollback, and [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]] activities required by this mission objective. | The derived requirements should distinguish: |
| |
| ===== Delivery Phase ===== | * Association of an Infrastructure Environment with an Operational Lifecycle revision |
| | * Assignment of the initial lifecycle state |
| | * Recording of the current lifecycle state |
| | * Execution of lifecycle transitions |
| | * Retirement of the Infrastructure Environment |
| |
| Phase 1 and subsequent phases | Lifecycle association identifies the lifecycle model governing an Infrastructure Environment. |
| |
| ===== Implementation Status ===== | Lifecycle initiation identifies the first lifecycle state assigned to the Infrastructure Environment. |
| |
| Not Assessed | Lifecycle state recording identifies the current state of the Infrastructure Environment. |
| | |
| Implementation status requires verification of the applicable [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activities from initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] through [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]]. | |
| | |
| ===== Requirement Status ===== | |
| | |
| Draft | |
| | |
| The source System Requirements Specification identifies Version 1.1 as a draft. | |
| | |
| ---- | |
| ===== Notes for Editors ===== | |
| |
| This requirement page should retain the stable requirement identifier `MO-006`. | Lifecycle transition execution changes the Infrastructure Environment from one permitted lifecycle state to another. |
| |
| Changes to the Statement SHALL preserve the approved intent of the source requirement. | Retirement places the Infrastructure Environment into its terminal lifecycle state after the defined Retirement conditions are satisfied. |
| |
| Material changes should receive review and should update the related outbound traceability, verification criteria, acceptance criteria, and source records. | The Original Requirement should not be marked as superseded until the requirement owner: |
| |
| The Source Statement should preserve the original wording from the controlling System Requirements Specification. | * Approves the proposed decomposition |
| | * Approves the child requirements |
| | * Defines the Operational Lifecycle association and revision rules |
| | * Defines the initial lifecycle state |
| | * Defines the lifecycle states and permitted transitions |
| | * Defines the Retirement conditions |
| | * Defines the required lifecycle records |
| | * Confirms that the child requirements collectively preserve the complete approved intent of MO-006 |
| | * Confirms that no additional child requirements are required |
| |
| Incoming traceability should use the wiki Backlinks function rather than a manually maintained list. | After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment. |
| |
| Do not rename this page once it has been cited externally unless a redirect or move plan is in place. | Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records. |
| |
| ---- | ---- |