dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b [2026/07/21 09:57] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b [2026/07/30 05:28] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-006b — Operational Lifecycle Initiation ======+====== MO-006b — Infrastructure Lifecycle Initiation ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL designate the initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] as the first stage of the assigned [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL designate the initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the first stage of its associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision.
  
 ===== Derived From ===== ===== Derived From =====
Line 17: Line 17:
 > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-MO-006b preserves the lifecycle-initiation boundary expressed by **from initial deployment** in the Original Requirement by identifying the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle.+MO-006b preserves the lifecycle-initiation boundary expressed by **from initial deployment** in the Original Requirement by identifying the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision.
  
 The separate requirements derived from MO-006 address: The separate requirements derived from MO-006 address:
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Operational Lifecycle Assignment]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Operational Lifecycle Association]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Current Lifecycle State Determination]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Infrastructure Lifecycle State Recording]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Lifecycle Transition Execution]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Infrastructure Lifecycle Transition Execution]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]
- 
-===== Assessment ===== 
- 
-The Original Requirement identifies **initial deployment** as the beginning of infrastructure lifecycle management but does not define the lifecycle-initiation relationship. 
- 
-Without an explicit initiation boundary, an evaluator cannot reliably determine: 
- 
-  * When the assigned Operational Lifecycle begins 
-  * Whether lifecycle management begins before, during, or after the initial Infrastructure Deployment 
-  * Which Infrastructure Deployment constitutes the initial deployment 
-  * Which Infrastructure Environment the initial deployment creates 
-  * Which Operational Lifecycle applies when deployment begins 
-  * Whether pre-deployment planning belongs to the Operational Lifecycle 
-  * Whether a redeployment creates a new Operational Lifecycle 
-  * The Evidence required to demonstrate lifecycle initiation 
- 
-The phrase **from initial deployment** embeds a separate lifecycle-initiation obligation within the broader lifecycle-management requirement. 
- 
-MO-006b: 
- 
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
-  * Identifies the initial Infrastructure Deployment as the lifecycle-initiation stage 
-  * Identifies the assigned Operational Lifecycle as the lifecycle being initiated 
-  * Avoids ambiguity between deployment start and deployment completion by treating the initial Infrastructure Deployment as a lifecycle stage 
-  * Separates lifecycle initiation from lifecycle assignment, current-state determination, transition execution, and Retirement 
  
 ===== Rationale ===== ===== Rationale =====
  
-The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] begins the realized lifecycle of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] first realizes an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].
  
-Designating the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle establishes a clear lifecycle boundary without requiring the lifecycle to begin at an ambiguous deployment event.+Designating the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision establishes the point at which management of the realized Infrastructure Environment begins.
  
 The initial Infrastructure Deployment can include: The initial Infrastructure Deployment can include:
  
-  * Selection of the applicable Infrastructure Baseline+  * Selection of the Infrastructure Baseline
   * Preparation of deployment inputs   * Preparation of deployment inputs
   * Provisioning of infrastructure resources   * Provisioning of infrastructure resources
Line 65: Line 40:
   * Application of security controls   * Application of security controls
   * Application of compliance controls   * Application of compliance controls
-  * Deployment validation+  * Deployment Validation
   * Evidence generation   * Evidence generation
-  * Establishment of the initial operational state+  * Establishment of the initial lifecycle state
  
 Lifecycle initiation supports: Lifecycle initiation supports:
  
-  * Consistent treatment of the initial Infrastructure Deployment 
   * Identification of the first lifecycle stage   * Identification of the first lifecycle stage
-  * Association of deployment Evidence with the Operational Lifecycle+  * Association of deployment records with the Operational Lifecycle revision
   * Determination of subsequent lifecycle states   * Determination of subsequent lifecycle states
   * Controlled execution of lifecycle transitions   * Controlled execution of lifecycle transitions
Line 79: Line 53:
   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
   * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]   * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Generation of auditable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] 
  
-Pre-deployment planning, design, approval, and preparation can precede the Operational Lifecycle of the realized Infrastructure Environment. Those activities remain governed by their applicable processes and requirements.+Pre-deployment planning, design, approval, and preparation may precede the Operational Lifecycle of the realized Infrastructure Environment.
  
-A subsequent deployment of the same Infrastructure Environment does not automatically create a new Operational Lifecycle. The applicable lifecycle model determines whether the deployment represents maintenance, restoration, replacement, recreation, or initiation of a new Infrastructure Environment.+A subsequent deployment does not automatically initiate a new Operational Lifecycle. The governing Operational Lifecycle revision determines whether the deployment represents maintenance, restoration, replacement, recreation, or creation of a new Infrastructure Environment.
  
-This requirement does not assign the Operational Lifecycle. MO-006a establishes lifecycle assignment.+This requirement does not associate the Operational Lifecycle revision with the Infrastructure Environment. MO-006a addresses that association.
  
-This requirement does not determine the current lifecycle state after initiation. MO-006c establishes current lifecycle state determination.+This requirement does not record the current lifecycle state after initiation. MO-006c addresses lifecycle-state recording.
  
-This requirement does not execute transitions following the initial stage. MO-006d establishes lifecycle transition execution.+This requirement does not execute lifecycle transitions following initiation. MO-006d addresses transition execution.
  
-This requirement does not establish Retirement. MO-006e establishes Infrastructure Environment Retirement.+This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.
  
 ===== Applies To ===== ===== Applies To =====
Line 102: Line 75:
   * Initial Infrastructure Deployments   * Initial Infrastructure Deployments
   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]
-  * Operational Lifecycle assignments+  * Operational Lifecycle revisions
   * Operational Lifecycle stages   * Operational Lifecycle stages
   * Lifecycle-initiation records   * Lifecycle-initiation records
Line 109: Line 82:
   * Deployment Platforms   * Deployment Platforms
   * Operational environments   * Operational environments
-  * Security profiles 
-  * Compliance profiles 
   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
Line 119: Line 90:
 Verification confirms that: Verification confirms that:
  
-  - The Infrastructure Environment is identified +  - The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is identified 
-  - The assigned Operational Lifecycle is identified +  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] identifier and revision are identified 
-  - The initial Infrastructure Deployment is identified +  - The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] is identified 
-  - The identified Infrastructure Deployment creates or first realizes the Infrastructure Environment +  - The identified Infrastructure Deployment first realizes the Infrastructure Environment 
-  - The initial Infrastructure Deployment is designated as the first stage of the assigned Operational Lifecycle+  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] designates the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision
   - The lifecycle-initiation relationship remains associated with the Infrastructure Environment   - The lifecycle-initiation relationship remains associated with the Infrastructure Environment
-  - The initiation record preserves the required Evidence, Provenance, and Traceability+  - A subsequent deployment does not initiate a new Operational Lifecycle unless the governing Operational Lifecycle revision requires creation of a new Infrastructure Environment 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Environment, initial Infrastructure Deployment, Operational Lifecycle revision, first lifecycle stage, and initiation record
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Environment inspection +The following pages reference this requirement:
-  * Operational Lifecycle assignment inspection +
-  * Initial Infrastructure Deployment inspection +
-  * Deployment-record inspection +
-  * Lifecycle-stage inspection +
-  * Lifecycle-initiation record inspection +
-  * Infrastructure Environment identity inspection +
-  * Subsequent-deployment comparison +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Environment +===== Delivery Phase =====
-  - The assigned Operational Lifecycle +
-  - The Operational Lifecycle identifier +
-  - The Operational Lifecycle revision +
-  - The initial Infrastructure Deployment +
-  - The Infrastructure Deployment identifier +
-  - The lifecycle-initiation stage +
-  - The initiation date and time +
-  - The lifecycle-initiation record +
-  - The authority or process responsible for the designation +
-  - Each conflicting or missing initiation relationship +
-  - Each identified failure or exception +
-  - The observed result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-===== Requirements Realized By =====+Implemented and Verified.
  
-This requirement is realized by:+===== Implementation Status =====
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start|OR-001 — Operational Roles]] +<todo>Assess whether the current Crucible implementation designates the initial Infrastructure Deployment of an Infrastructure Environment as the first stage of its associated Operational Lifecycle revision.</todo>
-  * [[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-005|OR-005 — Distributed Environment Management]] +
-  * [[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-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-metadata-catalog-and-provenance:start|FR-MC-001 through FR-MC-005]] +
-  * [[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]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>Review and accept MO-006b as a proposed derived requirement created from the evaluation and decomposition of MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo>
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[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 =====+---- 
 +===== Issues =====
  
-The following pages reference this requirement:+The following unresolved issues affect this requirement:
  
-{{backlinks>.#dido:02-crusible}}+<todo>Define the criteria used to identify the initial Infrastructure Deployment of an Infrastructure Environment.</todo>
  
-===== Delivery Phase =====+<todo>Define the event at which the initial Infrastructure Deployment first realizes the Infrastructure Environment.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the first stage of each Operational Lifecycle revision that may govern an Infrastructure Environment.</todo>
  
-===== Implementation Status =====+<todo>Identify the authority or process responsible for designating the initial Infrastructure Deployment as the first lifecycle stage.</todo>
  
-Not Assessed+<todo>Define whether pre-deployment planning, approval, and preparation belong to a separate lifecycle or process.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation designates the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle. +<todo>Define when a subsequent deployment creates a new Infrastructure Environment and initiates a new Operational Lifecycle.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 206: Line 141:
 This page is a leaf requirement page and omits a trailing '':start'' from its namespace. This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Changes to the Statement should preserve the relationship between the initial Infrastructure Deployment and the first stage of the assigned Operational Lifecycle.+The parent MO-006 page is a non-leaf page and retains a trailing '':start'' in its namespace. 
 + 
 +Changes to the Statement should preserve: 
 + 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
 +  * The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] as the lifecycle-initiation event 
 +  * The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the lifecycle subject 
 +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision as the governing lifecycle model 
 +  * The first lifecycle stage as the result of initiation
  
 The lifecycle-initiation record should identify: The lifecycle-initiation record should identify:
Line 214: Line 157:
   * The Operational Lifecycle revision   * The Operational Lifecycle revision
   * The initial Infrastructure Deployment identifier   * The initial Infrastructure Deployment identifier
-  * The lifecycle-initiation stage+  * The first lifecycle stage
   * The initiation date and time   * The initiation date and time
   * The authority or process responsible for the designation   * The authority or process responsible for the designation
-  * The applicable Infrastructure Baseline +  * The Infrastructure Baseline 
-  * The applicable Deployment Platform +  * The Deployment Platform 
-  * The applicable operational environment +  * The operational environment 
-  * The associated Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The associated Traceability +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * The supporting Evidence+
  
-Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.+Material changes should receive review and should update the verification criteria, source records, and Issues section.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-006/mo-006b.1784653070.txt.gz
  • Last modified: 2026/07/21 09:57
  • by nick_dido