MO-009b — Test Resource Control

DIDO-TE SHALL control each designated reusable Test Resource throughout its operational lifecycle by maintaining its identity, version, integrity, provenance, authorization, availability status, and change history.

MO-009b derives from MO-009 — Reusable Test Resources.

MO-009b specifies the Test Resource control portion of MO-009.

A reusable Test Resource requires controls that preserve its identity, integrity, provenance, and authorized state across successive uses.

Version control distinguishes the specific state of a Test Resource used during a Test Execution. Change history identifies modifications to the resource and supports evaluation of their effects on previous and subsequent Test Executions.

Authorization controls restrict the creation, modification, approval, release, withdrawal, and restoration of Test Resources to authorized actors. Availability status identifies whether a Test Resource remains approved and available for use.

These controls protect the repeatability, Reproducibility, Traceability, and evidentiary value of testing performed with reusable Test Resources.

MO-009b establishes control over designated reusable Test Resources. The companion requirements separately address Test Resource descriptions, applicability, and use Traceability.

MO-009b applies to:

  • Designated reusable Test Resources
  • Test Resource identities
  • Test Resource versions
  • Test Resource integrity information
  • Test Resource Provenance
  • Test Resource authorization
  • Test Resource availability status
  • Test Resource change histories

Verification confirms that:

  1. Each designated reusable Test Resource has a persistent identity
  2. DIDO-TE distinguishes each controlled version of a Test Resource
  3. DIDO-TE maintains integrity information for each controlled Test Resource version
  4. DIDO-TE maintains the provenance of each controlled Test Resource version
  5. DIDO-TE restricts Test Resource control operations to authorized actors
  6. DIDO-TE records changes made to a controlled Test Resource
  7. Each change record identifies the affected Test Resource and version
  8. Each change record identifies the change made
  9. Each change record identifies the actor responsible for the change
  10. Each change record identifies when the change occurred
  11. DIDO-TE identifies the availability status of each controlled Test Resource version
  12. DIDO-TE prevents use of a withdrawn or otherwise unavailable Test Resource unless an authorized exception permits that use
  13. DIDO-TE preserves the controlled Test Resource version associated with a completed Test Execution

The following pages reference this requirement:

Assign the delivery phase for MO-009b.

Record the implementation status of MO-009b after reviewing the implementation plan.

The proposed derived requirement requires review and acceptance.


Confirm the Test Resource control operations governed by MO-009b.

Confirm the actors authorized to create, modify, approve, release, withdraw, restore, and retire Test Resources.

Confirm the lifecycle states and availability statuses assigned to controlled Test Resources.

Confirm the integrity mechanism required for each controlled Test Resource type.

Confirm the provenance information required for each controlled Test Resource version.

Confirm the retention requirements for withdrawn, superseded, retired, and previously used Test Resource versions.

Confirm the conditions under which an authorized exception permits use of a withdrawn or otherwise unavailable Test Resource.

Confirm that MO-009b remains limited to Test Resource control and does not duplicate the description, applicability, or use Traceability obligations assigned to MO-009a, MO-009c, and MO-009d.


Use the following code to reference the Statement section from another wiki page:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-009:mo-009b#Statement&noheader&nofooter&noeditbtn}}

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

  • dido/03-dido-te/99-annexes/annex-c-requirements/01-mission-objectives/mo-009/mo-009b.txt
  • Last modified: 2026/08/07 01:09
  • by nick_dido