MO-008 — Traceable Test Results and Evidence

Go to Mission Objectives

Original Requirement

DIDO-TE SHALL produce traceable Test Results and Evidence.

Assessment of Original Requirement

MO-008 was generated as part of the DIDO-TE mission-objective requirements set. The identifier, title, and Original Requirement express the architectural intent that DIDO-TE outputs retain sufficient Traceability to support review, verification, audit, and authorization activities.

CWE Assessment

The Original Requirement communicates its high-level intent clearly, but it does not provide sufficient precision for implementation or verification.

The following CWE findings apply:

Produce identifies an observable DIDO-TE behaviorTraceable does not identify the records or relationships required to establish TraceabilityThe statement does not identify the objects to which Test Results and Evidence maintain TraceabilityThe conjunction and combines Test Results and Evidence into one normative statementThe statement does not distinguish Test Results from the Evidence used to substantiate or interpret those resultsThe statement does not identify the lifecycle stages across which Traceability must persistThe statement does not identify the identifiers, metadata, provenance records, or relationships used to establish TraceabilityThe statement does not identify the conditions under which a Test Result or Evidence item satisfies the requirementThe Original Requirement therefore expresses the mission objective but does not define a complete, measurable requirement.

SDA Assessment

The Original Requirement contains two independently verifiable obligations:

DIDO-TE produces traceable Test ResultsDIDO-TE produces traceable EvidenceA conforming implementation could provide adequate Traceability for Test Results while failing to provide adequate Traceability for Evidence, or the reverse. Combining the two obligations under one requirement would permit a single verification outcome to obscure this distinction.

Test Result Traceability and Evidence Traceability also involve different relationships.

A Test Result requires Traceability to the applicable:

Test EnvironmentConfiguration and applicable baselineInputs, observations, and resulting outcomeAn Evidence item requires Traceability to the applicable:

Test ExecutionTest Result or assertion it substantiatesSourceMethod of collection or creationTime of collection or creationResponsible actor or producing systemIntegrity and provenance informationThe parent requirement does not establish whether every Evidence item must relate directly to a Test Result. Some Evidence may instead document the Test Environment, configuration, execution conditions, controls, exceptions, or other facts needed to interpret a Test Result.

The requirement therefore requires decomposition into separately verifiable Test Result Traceability and Evidence Traceability obligations.

The decomposition preserves MO-008 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

Notes for Editors

MO-008 was generated as part of the DIDO-TE mission-objective requirements set. It does not reproduce an independently approved source statement.

This page retains the Original Requirement label to preserve the wording assessed during decomposition. The label identifies the original generated wording within this requirements corpus, not wording quoted from an external source.

This page should retain the stable parent requirement identifier MO-008.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The proposed child requirements are:

MO-008a — Test Result TraceabilityMO-008b — Evidence TraceabilityThe explicit links in Proposed Statements provide temporary links for creating the child pages. After both child pages exist and appear in the dynamic index, remove the explicit list to prevent duplicate entries.

The Original Requirement should not be marked as superseded until the requirement owner:

Approves both child requirementsConfirms that the child requirements collectively preserve the complete intent of MO-008Confirms the required Traceability relationships for Test Results and EvidenceConfirms that no additional child requirement is requiredAfter supersession, this page should remain as the parent Traceability record and continue to preserve the Original Requirement, its assessment, and the supersession decision.

The non-leaf page namespace is:

dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-008:start

The child requirement namespaces omit :start.

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