FR-DEPC-002 — Preserve Dependencies in a Dependency Store

Go to C.3.10 Dependency Capture and Offline Transfer

Crucible SHALL preserve captured Build Dependencies in a managed Dependency Store.

This requirement derives from:

• Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEPC-002

The Original Requirement states:

The system shall preserve captured dependencies in a managed dependency store.[C1]

FR-DEPC-002:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Identifies the captured dependencies as Build Dependencies
• Links Dependency Store to its controlling definition
• Retains the direct behavior preserve

No other substantive normalization is required.

Preserving captured Build Dependencies in a managed Dependency Store makes the dependencies available for later build, packaging, and transfer operations.

The Dependency Store provides a managed location for dependencies collected through Dependency Capture.

Preservation allows Crucible to retain captured dependencies independently of the external repositories or services from which the dependencies originated. This capability contributes to repeatable operations in Disconnected Environments.

This requirement establishes preservation in a Dependency Store without prescribing:

• A particular Dependency Store implementation
• A particular storage technology
• A particular repository format
• A particular directory structure
• A particular database
• A particular dependency format
• A retention period
• A deduplication strategy
• A replication strategy
• Creation of a Transfer Bundle
• Population of an Offline Repository

Separate requirements, architecture specifications, storage profiles, and retention policies govern those subjects and behaviors.

This requirement applies to:

• Crucible
• Captured Build Dependencies
• Dependency Stores
• Dependency Capture results

Verification confirms that:

1. One or more captured Build Dependencies are selected for testing
2. A managed Dependency Store is selected for testing
3. Crucible preserves the selected Build Dependencies in the Dependency Store
4. Each preserved Build Dependency can be identified in the Dependency Store
5. Each preserved Build Dependency remains available after the preservation operation completes
6. The preservation operation produces an observable result

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-DEPC-002 as a leaf requirement.

Determine whether separate requirements define the identity, revision, source, provenance, and integrity information preserved with each Build Dependency.

Determine whether separate requirements govern Dependency Store retention, replication, deduplication, and recovery.

Determine whether separate requirements define how Crucible retrieves preserved Build Dependencies from a Dependency Store.

This requirement page retains the stable requirement identifier FR-DEPC-002.

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

The Statement uses the following controlling Terms and Definitions entries:

• Build Dependency
• Dependency Capture
• Dependency Store

The Statement addresses preservation of captured Build Dependencies in a managed Dependency Store.

FR-DEPC-001 governs capture of Build Dependencies.

FR-DEPC-003 governs production of a Transfer Bundle.

FR-DEPC-004 governs population of Offline Repositories.

FR-DEPC-005 governs Dependency Store implementation independence.

Do not add particular storage technologies, repository formats, directory structures, retention periods, replication mechanisms, deduplication strategies, retrieval behavior, or transfer obligations unless the controlling requirement changes through an approved requirements process.

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:fr-depc-002#Statement&noheader&nofooter&noeditbtn}}