dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001

This is an old revision of the document!


FR-IMG-001 — Build Virtual Machine Images

Crucible SHALL build a Machine Image.

The system shall build virtual machine images.

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-IMG-001.

The source statement expresses a direct functional behavior but requires normalization of terminology.

The following Specification, Discipline, and Authoring findings apply:

  • The system does not use the defined system name
  • shall does not follow the established uppercase normative convention
  • virtual machine images does not use the defined Machine Image term
  • The source statement does not identify a particular image format, target platform, build tool, or build method
  • The source statement does not require image signing, image verification, image promotion, compliance assessment, or deployment

The normalized Statement:

  • Replaces The system with Crucible
  • Uses the direct and testable verb build
  • Replaces virtual machine images with the defined Machine Image term
  • Preserves the implementation independence of the source requirement
  • Retains one primary required behavior

The normalized Statement does not add requirements for the contents, format, signing, verification, promotion, compliance, or deployment of the resulting Machine Image. Separate requirements define those obligations.

A Machine Image captures the software, configuration, and other image content required to instantiate a virtual machine.

Building Machine Images through Crucible allows the Image Management workflow to create image Artifacts for later verification, signing, promotion, distribution, and deployment.

Machine Image building contributes to:

The build operation may consume:

The applicable architecture and lower-level requirements determine which inputs apply to a particular Machine Image build.

This requirement applies to:

  1. Verification SHALL confirm that Crucible executes a Machine Image build
  2. Verification SHALL confirm that the build produces a Machine Image

Verification may include:

  • Machine Image build testing
  • Build-output inspection
  • Machine Image artifact inspection
  • Build-log inspection
  • Automated CI/CD Pipeline testing

The verification record SHALL identify:

  1. The tested Machine Image build
  2. The resulting Machine Image
  3. The build result
  4. The observed output
  5. The generated Evidence

The wiki Backlinks function provides the current list of pages that reference FR-IMG-001.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

The Crucible Concept of Operations describes a Phase 1 workflow in which a CI/CD Pipeline invokes Crucible to compose selected inputs and build a hardened Machine Image.

FR-IMG-001 establishes the required Machine Image build behavior within that workflow.

Requirements governing image composition, hardening, signing, verification, promotion, compliance, and deployment define separate behavior associated with the resulting Machine Image.

Phase 1

Not Assessed

Implementation status requires verification that Crucible builds a Machine Image.

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.


This requirement page should retain the stable requirement identifier FR-IMG-001.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to building a Machine Image.

Requirements for image composition, hardening, signing, verification, promotion, compliance assessment, distribution, and deployment should remain in their applicable requirement pages.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001#Statement&noheader&nofooter&noeditbtn}}

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


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

  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-02-image-management/fr-img-001.1784299150.txt.gz
  • Last modified: 2026/07/17 07:39
  • by nick_dido