Differences

This shows you the differences between two versions of the page.

--- dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-008:start [2026/08/06 12:23] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-008:start [2026/08/06 12:47] (current) – nick_dido
@@ Line 1: / Line 1: @@
+====== MO-008 — Traceable Test Results and Evidence ======
+[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]
+===== Original Requirement =====
+> //[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL produce traceable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 behavior
+  * **Traceable** does not identify the records or relationships required to establish Traceability
+  * The statement does not identify the objects to which Test Results and Evidence maintain Traceability
+  * The conjunction **and** combines Test Results and Evidence into one normative statement
+  * The statement does not distinguish Test Results from the Evidence used to substantiate or interpret those results
+  * The statement does not identify the lifecycle stages across which Traceability must persist
+  * The statement does not identify the identifiers, metadata, provenance records, or relationships used to establish Traceability
+  * The statement does not identify the conditions under which a Test Result or Evidence item satisfies the requirement
+The 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 Results
+  * DIDO-TE produces traceable Evidence
+A 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:
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solution]]
+  * Test Environment
+  * Configuration and applicable baseline
+  * Inputs, observations, and resulting outcome
+An Evidence item requires Traceability to the applicable:
+  * Test Execution
+  * Test Result or assertion it substantiates
+  * Source
+  * Method of collection or creation
+  * Time of collection or creation
+  * Responsible actor or producing system
+  * Integrity and provenance information
+The 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:
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-008#1|js navbar nocookie maxjs#1 id#dido_te_mo_008_requirements_nav}}
+===== Requirement Status =====
+<todo>Review and approve the decomposition of MO-008 into separate Test Result Traceability and Evidence Traceability requirements.</todo>
+<todo>Determine whether MO-008a and MO-008b collectively supersede MO-008.</todo>
+<todo>If MO-008a and MO-008b are accepted as the complete replacement for MO-008, mark MO-008 as superseded and preserve this page as the parent Traceability record.</todo>
+----
+===== Issues =====
+<todo>Confirm the controlling DIDO-TE architectural or mission source from which MO-008 was derived.</todo>
+<todo>Confirm the minimum relationships required to establish Traceability for each Test Result.</todo>
+<todo>Confirm the minimum relationships required to establish Traceability for each Evidence item.</todo>
+<todo>Determine whether DIDO-TE requires every Evidence item to substantiate a Test Result or whether Evidence also documents environments, configurations, controls, conditions, and exceptions.</todo>
+<todo>Determine whether integrity, provenance, retention, and chain-of-custody obligations require separate requirements elsewhere in the requirements corpus.</todo>
+<todo>Determine whether MO-008a and MO-008b provide complete coverage of the intent expressed by MO-008.</todo>
+----
+===== 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 Traceability''
+  * ''MO-008b — Evidence Traceability''
+The 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 requirements
+  * Confirms that the child requirements collectively preserve the complete intent of MO-008
+  * Confirms the required Traceability relationships for Test Results and Evidence
+  * Confirms that no additional child requirement is required
+After 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:
+<code>
+dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-008:start
+</code>
+The child requirement namespaces omit '':start''.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>