This is an old revision of the document!


MO-006 — Infrastructure Lifecycle Management

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

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 Crucible
  • Support is a weak verb that does not identify the behavior Crucible performs
  • Infrastructure does not identify the lifecycle subject as an Infrastructure Environment
  • Infrastructure lifecycle management combines multiple independently verifiable behaviors
  • The Original Requirement does not require association of an Infrastructure Environment with an identified Operational Lifecycle
  • The Original Requirement does not identify the Operational Lifecycle revision applicable to the Infrastructure Environment
  • Initial deployment embeds a separate lifecycle-initiation obligation
  • Through retirement embeds a separate terminal lifecycle obligation
  • The Original Requirement does not identify the current lifecycle state of the Infrastructure Environment
  • The Original Requirement does not identify the lifecycle transitions allocated to Crucible
  • The Original Requirement does not identify the conditions that permit a lifecycle transition
  • The Original Requirement does not identify the conditions that permit Retirement
  • The Original Requirement combines lifecycle assignment, lifecycle initiation, lifecycle-state determination, lifecycle-transition execution, and Retirement within one normative statement
  • These obligations can pass or fail independently
  • The Original Requirement does not provide independently identifiable statements for verification and traceability

The previously normalized Statement also combined:

  • Management of each Infrastructure Environment
  • Association with an applicable Operational Lifecycle
  • Lifecycle initiation at the initial Infrastructure Deployment
  • Management of intermediate lifecycle states
  • Execution or coordination of lifecycle transitions
  • Continuation of lifecycle management through Retirement

These obligations can pass or fail independently. The term throughout also does not identify whether the requirement applies continuously, during each lifecycle state, during each transition, or whenever a lifecycle activity occurs. The current page consequently places several substantive obligations within its Verification section rather than expressing them as atomic Statements. :contentReference[oaicite:0]{index=0}

The Original Requirement therefore requires decomposition into independently identifiable normative requirements.

The decomposition preserves MO-006 as the stable parent requirement identifier. Each replacement requirement receives a lettered identifier and a separate requirement page.

The Original Requirement is replaced by the following independently identifiable normative requirements:


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

  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-006/start.1784563844.txt.gz
  • Last modified: 2026/07/20 09:10
  • by nick_dido