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

Differences

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

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b [2026/07/20 08:47] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b [2026/07/30 05:25] (current) – [Delivery Phase] nick_dido
Line 17: Line 17:
 > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-MO-005b preserves the identification needed to manage infrastructure as a reusable and version-controlled asset by requiring each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] to have a unique [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] identifier.+MO-005b preserves the identification needed to manage infrastructure as a reusable and version-controlled asset by requiring each Infrastructure Baseline to have a unique Artifact identifier.
  
 The separate requirements derived from MO-005 address: The separate requirements derived from MO-005 address:
  
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Version Control]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Revision Control]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Infrastructure Baseline Selection]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Approved Infrastructure Baseline Selection]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Baseline Immutability]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Infrastructure Baseline Preservation]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Baseline Revision Deployment Traceability]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]]
- +
-===== Assessment ===== +
- +
-The Original Requirement identifies infrastructure as an asset but does not require a unique identifier for the managed asset. +
- +
-Without a unique identifier, an evaluator cannot reliably distinguish: +
- +
-  * One Infrastructure Baseline from another Infrastructure Baseline +
-  * An Infrastructure Baseline from an Infrastructure Deployment created from it +
-  * References to the same Infrastructure Baseline across repositories, catalogs, deployment records, and Evidence +
-  * The identity of an Infrastructure Baseline from the identity of one of its revisions +
- +
-The Original Requirement does not identify: +
- +
-  * The object receiving the identifier +
-  * The uniqueness boundary for the identifier +
-  * The relationship between the identifier and the Infrastructure Baseline Artifact +
-  * The use of the identifier in selection, reuse, deployment records, Provenance, and Traceability +
-  * The Evidence required to demonstrate identifier uniqueness +
- +
-MO-005b: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies the Infrastructure Baseline as the object receiving the identifier +
-  * Identifies the assigned identifier as an Artifact identifier +
-  * Requires the identifier to be unique +
-  * Separates Infrastructure Baseline identity from revision identification and Version Control +
-  * Separates identification from Artifact management, selection, reuse, immutability, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
Line 60: Line 32:
 A unique Artifact identifier provides a stable identity for each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]]. A unique Artifact identifier provides a stable identity for each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]].
  
-The identifier enables Crucible and external systems to reference the same Infrastructure Baseline across:+The identifier allows Crucible and external systems to refer to the same Infrastructure Baseline across:
  
   * Artifact repositories   * Artifact repositories
Line 66: Line 38:
   * Baseline composition records   * Baseline composition records
   * Approval records   * Approval records
-  * Version Control systems+  * Revision-control records
   * Infrastructure Deployment records   * Infrastructure Deployment records
   * Compliance records   * Compliance records
Line 74: Line 46:
   * Traceability relationships   * Traceability relationships
  
-The Infrastructure Baseline identifier identifies the baseline as a managed Artifact. A separate revision identifier can distinguish individual revisions of that Artifact.+The Infrastructure Baseline identifier identifies the baseline as a managed Artifact. A separate revision identifier distinguishes one controlled revision of that Artifact from another.
  
-The stable Artifact identifier supports:+A stable Artifact identifier supports:
  
-  * Unambiguous baseline selection +  * Unambiguous Infrastructure Baseline selection 
-  * Reuse of the same baseline across multiple Infrastructure Deployments +  * Reuse of the same Infrastructure Baseline across multiple Infrastructure Deployments 
-  * Comparison of baseline revisions +  * Comparison of Infrastructure Baseline revisions 
-  * Retrieval of baseline history +  * Retrieval of Infrastructure Baseline history 
-  * Association of approvals with the correct baseline +  * Association of approvals with the correct Infrastructure Baseline 
-  * Association of deployments with the correct baseline +  * Association of deployments with the correct Infrastructure Baseline 
-  * Preservation of Provenance +  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * Maintenance of 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]]+
  
-This requirement does not establish the revision identifier or revision-management behavior. MO-005c establishes Version Control requirements.+This requirement does not establish the revision identifier or revision-control behavior. MO-005c addresses those outcomes.
  
-This requirement does not require selection or reuse of the identified Infrastructure Baseline. MO-005d and MO-005e establish those requirements.+This requirement does not require selection or reuse of the identified Infrastructure Baseline. MO-005d and MO-005e address those outcomes.
  
 ===== Applies To ===== ===== Applies To =====
Line 101: Line 72:
   * Artifact identifiers   * Artifact identifiers
   * Artifact catalog records   * Artifact catalog records
-  * Artifact repositories +  * Artifact repository records 
-  * Baseline composition records +  * Infrastructure Baseline approval records 
-  * Baseline approval records +  * Infrastructure Baseline revision records
-  * Version Control records+
   * Infrastructure Deployment records   * Infrastructure Deployment records
-  * Compliance records 
-  * Security records 
   * [[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 116: Line 84:
 Verification confirms that: Verification confirms that:
  
-  - Each Infrastructure Baseline has an Artifact identifier +  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] has an assigned [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] identifier 
-  - The Artifact identifier refers to one Infrastructure Baseline +  - Each Artifact identifier refers to one Infrastructure Baseline 
-  - No two Infrastructure Baselines have the same Artifact identifier within the applicable identifier scope+  - No two Infrastructure Baselines have the same Artifact identifier within the defined identifier scope
   - The Artifact identifier remains associated with the Infrastructure Baseline across repositories, catalogs, and related records   - The Artifact identifier remains associated with the Infrastructure Baseline across repositories, catalogs, and related records
   - The Artifact identifier distinguishes the Infrastructure Baseline from an Infrastructure Deployment created from it   - The Artifact identifier distinguishes the Infrastructure Baseline from an Infrastructure Deployment created from it
-  - The Artifact identifier remains distinguishable from identifiers assigned to individual baseline revisions +  - The Artifact identifier remains distinguishable from identifiers assigned to individual Infrastructure Baseline revisions 
-  - The identification record preserves the required Evidence, Provenance, and Traceability+  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Baseline, assigned Artifact identifier, repository records, catalog records, revision records, and deployment records
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Artifact identifier inspection +
-  * Identifier uniqueness testing +
-  * Artifact catalog inspection +
-  * Artifact repository inspection +
-  * Cross-repository identifier comparison +
-  * Baseline composition record inspection +
-  * Baseline approval record inspection +
-  * Version Control record inspection +
-  * Infrastructure Deployment record inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Baseline +===== Delivery Phase =====
-  - The assigned Artifact identifier +
-  - The applicable identifier scope +
-  - The associated Artifact catalog record +
-  - The associated Artifact repository record +
-  - Each related baseline record inspected +
-  - Each duplicate or conflicting identifier detected +
-  - The uniqueness determination +
-  - 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:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +<todo>Assess whether the current Crucible implementation assigns a unique Artifact identifier to each Infrastructure Baseline.</todo>
-  * [[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-005b as a proposed derived requirement created from the evaluation and decomposition of MO-005 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: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 syntax of the Artifact identifier assigned to an Infrastructure Baseline.</todo>
  
-===== Delivery Phase =====+<todo>Define the uniqueness scope for Infrastructure Baseline Artifact identifiers.</todo>
  
-Phase 1 and subsequent phases+<todo>Identify the authority responsible for assigning Infrastructure Baseline Artifact identifiers.</todo>
  
-===== Implementation Status =====+<todo>Define the relationship between an Infrastructure Baseline Artifact identifier and an Infrastructure Baseline revision identifier.</todo>
  
-Not Assessed+<todo>Define the behavior required when Crucible detects an identifier collision.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation assigns a unique Artifact identifier to each Infrastructure Baseline. +<todo>Define the treatment of Artifact identifiers assigned to retired or withdrawn Infrastructure Baselines.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 198: Line 134:
 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 Infrastructure Baseline identification intent derived from MO-005.+The parent MO-005 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 [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the identified subject 
 +  * The [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] identifier as the assigned identifier 
 +  * Uniqueness of the identifier within the defined identifier scope
  
 The identifier scheme should define: The identifier scheme should define:
  
   * The identifier syntax   * The identifier syntax
-  * The applicable uniqueness scope+  * The uniqueness scope
   * The identifier-issuing authority   * The identifier-issuing authority
   * The relationship between an Artifact identifier and a revision identifier   * The relationship between an Artifact identifier and a revision identifier
-  * The relationship between the identifier and the Artifact catalog record+  * The relationship between the identifier and an Artifact catalog record
   * The treatment of identifier collisions   * The treatment of identifier collisions
   * The treatment of retired Infrastructure Baselines   * The treatment of retired Infrastructure Baselines
-  * 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-005/mo-005b.1784562445.txt.gz
  • Last modified: 2026/07/20 08:47
  • by nick_dido