MO-005b — Infrastructure Baseline Identification

Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Crucible SHALL assign a unique Artifact identifier to each Infrastructure Baseline.

This requirement derives from:

• MO-005 — Reusable and Version-Controlled Infrastructure Baselines

The Original Requirement states:

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

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:

• MO-005a — Infrastructure Baseline Artifact Management
• MO-005c — Infrastructure Baseline Revision Control
• MO-005d — Approved Infrastructure Baseline Selection
• MO-005e — Infrastructure Baseline Reuse
• MO-005f — Approved Infrastructure Baseline Preservation
• MO-005g — Infrastructure Deployment Baseline Traceability

A unique Artifact identifier provides a stable identity for each Infrastructure Baseline.

The identifier allows Crucible and external systems to refer to the same Infrastructure Baseline across:

• Artifact repositories
• Artifact catalogs
• Baseline composition records
• Approval records
• Revision-control records
• Infrastructure Deployment records
• Compliance records
• Security records
• Evidence records
• Provenance records
• Traceability relationships

The Infrastructure Baseline identifier identifies the baseline as a managed Artifact. A separate revision identifier distinguishes one controlled revision of that Artifact from another.

A stable Artifact identifier supports:

• Unambiguous Infrastructure Baseline selection
• Reuse of the same Infrastructure Baseline across multiple Infrastructure Deployments
• Comparison of Infrastructure Baseline revisions
• Retrieval of Infrastructure Baseline history
• Association of approvals with the correct Infrastructure Baseline
• Association of deployments with the correct Infrastructure Baseline
• Preservation of Provenance
• Maintenance of Traceability

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 address those outcomes.

This requirement applies to:

• Crucible
• Infrastructure Baselines
• Artifacts
• Artifact identifiers
• Artifact catalog records
• Artifact repository records
• Infrastructure Baseline approval records
• Infrastructure Baseline revision records
• Infrastructure Deployment records
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. Each Infrastructure Baseline has an assigned Artifact identifier
2. Each Artifact identifier refers to one Infrastructure Baseline
3. No two Infrastructure Baselines have the same Artifact identifier within the defined identifier scope
4. The Artifact identifier remains associated with the Infrastructure Baseline across repositories, catalogs, and related records
5. The Artifact identifier distinguishes the Infrastructure Baseline from an Infrastructure Deployment created from it
6. The Artifact identifier remains distinguishable from identifiers assigned to individual Infrastructure Baseline revisions
7. The verification record preserves Traceability among the Infrastructure Baseline, assigned Artifact identifier, repository records, catalog records, revision records, and deployment records

The following pages reference this requirement:

Implemented and Verified.

Assess whether the current Crucible implementation assigns a unique Artifact identifier to each Infrastructure Baseline.

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.

The following unresolved issues affect this requirement:

Define the syntax of the Artifact identifier assigned to an Infrastructure Baseline.

Define the uniqueness scope for Infrastructure Baseline Artifact identifiers.

Identify the authority responsible for assigning Infrastructure Baseline Artifact identifiers.

Define the relationship between an Infrastructure Baseline Artifact identifier and an Infrastructure Baseline revision identifier.

Define the behavior required when Crucible detects an identifier collision.

Define the treatment of Artifact identifiers assigned to retired or withdrawn Infrastructure Baselines.

This requirement page should retain the stable requirement identifier MO-005b.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The parent MO-005 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

• Crucible as the responsible actor
• The Infrastructure Baseline as the identified subject
• The Artifact identifier as the assigned identifier
• Uniqueness of the identifier within the defined identifier scope

The identifier scheme should define:

• The identifier syntax
• The uniqueness scope
• The identifier-issuing authority
• The relationship between an Artifact identifier and a revision identifier
• The relationship between the identifier and an Artifact catalog record
• The treatment of identifier collisions
• The treatment of retired Infrastructure Baselines

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:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.