FR-DEPC-005 — Dependency Store Implementation Independence [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== FR-DEPC-005 — Dependency Store Implementation Independence ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|Go to C.3.10 Dependency Capture and Offline Transfer]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL permit the implementation of a [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] to change without changing the [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]] [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]].

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEPC-005

The Original Requirement states:

> //The system shall permit the dependency-store implementation to evolve without changing the dependency-capture contract.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-DEPC-005:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Changes **shall** to the established uppercase normative form **SHALL**
  * Replaces the imprecise verb **evolve** with the directly testable verb **change**
  * Links [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]], and [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] to their controlling definitions
  * Treats **Dependency Capture Contract** as a composition of the existing controlled terms rather than as a separate defined term

No other substantive normalization is required.

===== Rationale =====

The internal implementation of a [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] can change as storage technologies, repository formats, scaling needs, operational constraints, or deployment environments change.

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]] [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] defines the externally observable behavior through which Crucible captures and preserves dependencies.

Separating the Dependency Capture Contract from the Dependency Store implementation allows Crucible to replace or modify the internal storage implementation without requiring dependent workflows, tools, or components to change how they interact with Dependency Capture.

This requirement establishes implementation independence without prescribing:

  * A particular Dependency Store implementation
  * A particular storage technology
  * A particular repository format
  * A particular database
  * A particular directory structure
  * A particular internal data model
  * A particular interface technology
  * A particular migration mechanism
  * Backward compatibility beyond the Dependency Capture Contract
  * Simultaneous use of multiple Dependency Store implementations

Separate requirements, architecture specifications, interface definitions, and migration procedures govern those subjects and behaviors.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] implementations
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contracts]]
  * Components that use the Dependency Capture Contract

===== Verification =====

Verification confirms that:

  - A conforming [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] implementation is selected for testing
  - A second conforming Dependency Store implementation with a different internal implementation is selected for testing
  - A [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]] operation is performed using the first Dependency Store implementation
  - The first Dependency Store implementation is replaced with the second Dependency Store implementation
  - The same Dependency Capture operation is performed using the second Dependency Store implementation without changing the Dependency Capture [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]]
  - Both operations produce results consistent with the Dependency Capture Contract

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-DEPC-005 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Determine whether the architecture explicitly identifies the operations and information defined by the Dependency Capture Contract.</todo>

<todo>Determine whether separate requirements define conformance criteria for alternative Dependency Store implementations.</todo>

<todo>Determine whether separate requirements govern migration of preserved dependencies between Dependency Store implementations.</todo>

----
===== Notes for Editors =====

This requirement page retains the stable requirement identifier ''FR-DEPC-005''.

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:

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]]

The phrase **Dependency Capture Contract** composes the controlled terms Dependency Capture and Contract. Do not create a separate glossary entry unless the architecture assigns additional semantics, required contents, or conformance rules to that combined phrase.

The Statement addresses independence of the Dependency Capture Contract from the internal Dependency Store implementation.

FR-DEPC-001 governs capture of [[dido:99_annexes:annex-b-terms-and-definitions:b:build_dependency|Build Dependencies]].

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

FR-DEPC-003 governs production of a [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]].

FR-DEPC-004 governs population of [[dido:99_annexes:annex-b-terms-and-definitions:o:offline_repository|Offline Repositories]].

Do not add particular storage technologies, internal data models, interface technologies, migration mechanisms, or multi-store operation obligations unless the controlling requirement changes through an approved requirements process.

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

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

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>