MO-006 — Infrastructure Lifecycle Management

Go to Mission Objectives

Original Requirement

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.[C1]

Assessment of Original Requirement

The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system name CrucibleSupport is a weak verb that does not identify an observable behavior performed by CrucibleInfrastructure does not identify the lifecycle subject as an Infrastructure EnvironmentInfrastructure lifecycle management combines multiple independently testable behaviorsInitial deployment introduces a separate lifecycle-initiation obligationThrough retirement introduces a separate terminal lifecycle obligationThe Original Requirement does not identify:

The Operational Lifecycle associated with each Infrastructure EnvironmentThe Operational Lifecycle revision associated with each Infrastructure EnvironmentThe lifecycle state assigned when the Infrastructure Environment is createdThe current lifecycle state of the Infrastructure EnvironmentThe lifecycle transitions that Crucible performsThe conditions that permit each lifecycle transitionThe conditions that permit RetirementThe lifecycle records preserved for verification and TraceabilityThe Original Requirement therefore requires:

Replacement of the system with the defined system name CrucibleReplacement of support with observable Crucible behaviorIdentification of the lifecycle subject as an Infrastructure EnvironmentAssociation of each Infrastructure Environment with an identified Operational Lifecycle revisionIdentification of the initial lifecycle stateRecording of the current lifecycle stateExecution of permitted lifecycle transitionsRetirement of the Infrastructure Environment when the Retirement conditions are satisfiedConfirmation that the derived requirements collectively preserve the complete intent of MO-006The decomposition preserves MO-006 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

The following unresolved issues affect the decomposition of MO-006:

Notes for Editors

This page should retain the stable parent requirement identifier MO-006.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

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.

This page preserves:

The Original RequirementThe assessment of the Original RequirementThe reason for decompositionTraceability to the proposed replacement requirementsThe unresolved cross-cutting issues affecting the decompositionThe supersession decisionThe derived requirements should distinguish:

Association of an Infrastructure Environment with an Operational Lifecycle revisionAssignment of the initial lifecycle stateRecording of the current lifecycle stateExecution of lifecycle transitionsRetirement of the Infrastructure EnvironmentLifecycle association identifies the lifecycle model governing an Infrastructure Environment.

Lifecycle initiation identifies the first lifecycle state assigned to the Infrastructure Environment.

Lifecycle state recording identifies the current state of the Infrastructure Environment.

Lifecycle transition execution changes the Infrastructure Environment from one permitted lifecycle state to another.

Retirement places the Infrastructure Environment into its terminal lifecycle state after the defined Retirement conditions are satisfied.

The Original Requirement should not be marked as superseded until the requirement owner:

Approves the proposed decompositionApproves the child requirementsDefines the Operational Lifecycle association and revision rulesDefines the initial lifecycle stateDefines the lifecycle states and permitted transitionsDefines the Retirement conditionsDefines the required lifecycle recordsConfirms that the child requirements collectively preserve the complete approved intent of MO-006Confirms that no additional child requirements are requiredAfter supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.