FR-DEPC-001 — Capture Build Dependencies

Go to C.3.10 Dependency Capture and Offline Transfer

Crucible SHALL perform Dependency Capture for Build Dependencies.

This requirement derives from:

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

The Original Requirement states:

The system shall capture build dependencies.[C1]

FR-DEPC-001:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Replaces capture build dependencies with the controlled concepts Dependency Capture and Build Dependency
• Retains capture of Build Dependencies as the required behavior

No other substantive normalization is required.

Dependency Capture identifies and collects the Build Dependencies required by a build.

Captured Build Dependencies can be preserved, transferred, and made available for later build operations, including operations performed in a Disconnected Environment.

This requirement establishes Dependency Capture without prescribing:

• Particular Build Dependencies
• A particular dependency source
• A particular dependency format
• A particular package manager
• A particular build tool
• A particular Dependency Store
• A particular capture mechanism
• Creation of a Transfer Bundle
• Population of an Offline Repository
• Transfer across a Transfer Boundary

Separate requirements, architecture specifications, build definitions, and dependency profiles govern those subjects and behaviors.

This requirement applies to:

• Crucible
• Dependency Capture
• Build Dependencies
• Build operations

Verification confirms that:

1. A build with one or more required Build Dependencies is selected for testing
2. Crucible performs Dependency Capture for the selected build
3. Each required Build Dependency captured during the tested operation can be identified
4. The captured Build Dependencies correspond to dependencies required by the selected build
5. The Dependency Capture operation produces an observable result

The following pages reference this requirement:

Implemented and Verified

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

Determine whether separate requirements define the dependency information that Crucible must record during Dependency Capture.

Determine whether separate requirements govern dependency identity, revision, source, provenance, and integrity information.

Determine whether separate requirements define handling of unavailable or unresolved Build Dependencies.

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

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:

• Dependency Capture
• Build Dependency

The Statement addresses capture of Build Dependencies.

FR-DEPC-002 governs preservation of captured dependencies in a Dependency Store.

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 dependency sources, formats, package managers, build tools, storage mechanisms, transfer behavior, or Offline Repository 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-001#Statement&noheader&nofooter&noeditbtn}}