dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-013-maintain-node-traceability

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-013-maintain-node-traceability [2026/08/17 14:20] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-013-maintain-node-traceability [2026/08/17 14:20] (current) – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-013-maintain-node-traceability to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-013-maintain-node-traceabil nick_dido
Line 1: Line 1:
 +====== NOD-013 — Maintain Node Traceability ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:start|Go to Node Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL maintain each [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|trace relationship]] specified for a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] by the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
 +
 +===== Derived From =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]
 +
 +===== Rationale =====
 +
 +Node [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] preserves the explicit relationships required to reconstruct and evaluate a Node’s participation in a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +The governing Test Definition identifies each required trace relationship. Each relationship identifies two related items and the nature of their relationship.
 +
 +Required trace relationships connect the Node to its [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Bindings]], Dependencies, Test Resources, governing Test Definitions, and governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedures]].
 +
 +Other required relationships connect the Node to authorization, configuration, validation, readiness, lifecycle control, execution, observation, resource control, [[dido:99_annexes:annex-b-terms-and-definitions:f:fault_injection|Fault Injection]], state preservation, reset, exceptions, Test Outcomes, Test Results, and Evidence.
 +
 +Mere co-location in the same record, repository, Test Environment, or Test Execution does not establish Traceability. The DIDO-TE preserves an explicit relationship with an identified meaning.
 +
 +Trace relationships remain distinguishable across Node replacements, replicas, restarted instances, configuration changes, repeated Test Executions, record revisions, and corrected Test Results. Historical relationships remain available after a related item changes.
 +
 +Missing, ambiguous, incorrect, or broken trace relationships prevent reconstruction of Node participation and weaken confidence in Test Results and Evidence.
 +
 +===== Applies To =====
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependency]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exception]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_outcome|Test Outcome]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:a:authorizing_authority|Authorizing Authority]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:f:fault|Fault]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:f:fault_injection|Fault Injection]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +===== Verification =====
 +
 +Verification confirms that:
 +
 +  - The governing Test Definition identifies each trace relationship required for the Node.
 +  - Each trace relationship uniquely identifies its source item.
 +  - Each trace relationship uniquely identifies its target item.
 +  - Each trace relationship identifies the nature of the relationship.
 +  - Each directed trace relationship identifies its direction.
 +  - Each trace relationship identifies its governing context.
 +  - The DIDO-TE maintains each trace relationship specified by the governing Test Definition.
 +  - The DIDO-TE maintains each required relationship between the Node and its Node Definition.
 +  - The DIDO-TE maintains each required relationship between the Node and its Node Implementation.
 +  - The DIDO-TE maintains each required relationship between the Node and its Node Configuration.
 +  - The DIDO-TE maintains each required relationship between the Node and its Node Bindings.
 +  - The DIDO-TE maintains each required relationship between the Node and its Dependencies.
 +  - The DIDO-TE maintains each required relationship between the Node and its Test Resources.
 +  - The DIDO-TE maintains each required relationship between the Node and its governing Test Definitions.
 +  - The DIDO-TE maintains each required relationship between the Node and its governing Test Procedures.
 +  - The DIDO-TE maintains each required relationship between the Node and its authorizations.
 +  - The DIDO-TE maintains each required relationship between the Node and its configuration records.
 +  - The DIDO-TE maintains each required relationship between the Node and its validation records.
 +  - The DIDO-TE maintains each required relationship between the Node and its readiness records.
 +  - The DIDO-TE maintains each required relationship between the Node and its lifecycle records.
 +  - The DIDO-TE maintains each required relationship between the Node and its isolation records.
 +  - The DIDO-TE maintains each required relationship between the Node and its reset records.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Environment in which it participates.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Execution in which it participates.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Input supplied to it.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified activity.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified interaction.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified state transition.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified control action.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified observation.
 +  - The DIDO-TE maintains each required relationship between the Node and each identified output.
 +  - The DIDO-TE maintains each required relationship between the Node and each resource allocation.
 +  - The DIDO-TE maintains each required relationship between the Node and each resource-use observation.
 +  - The DIDO-TE maintains each required relationship between the Node and each resource-control action.
 +  - The DIDO-TE maintains each required relationship between the Node and each resource release.
 +  - The DIDO-TE maintains each required relationship between the Node and each Fault specification.
 +  - The DIDO-TE maintains each required relationship between the Node and each Fault Injection.
 +  - The DIDO-TE maintains each required relationship between the Node and each Fault-control action.
 +  - The DIDO-TE maintains each required relationship between the Node and each Fault-recovery action.
 +  - The DIDO-TE maintains each required relationship between the Node and each preserved state representation.
 +  - The DIDO-TE maintains each required relationship between the Node and each state-preservation action.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Execution Exception affecting it.
 +  - The DIDO-TE maintains each required relationship between a Test Execution Exception and its Test Execution Exception Type.
 +  - The DIDO-TE maintains each required relationship between a Test Execution Exception and its disposition.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Outcome.
 +  - The DIDO-TE maintains each required relationship between the Node and each Test Result.
 +  - The DIDO-TE maintains each required relationship between the Node and each item of Evidence.
 +  - The DIDO-TE distinguishes trace relationships for replacement Nodes.
 +  - The DIDO-TE distinguishes trace relationships for replica Nodes.
 +  - The DIDO-TE distinguishes trace relationships for restarted Node instances.
 +  - The DIDO-TE distinguishes trace relationships for concurrently executing Node instances.
 +  - The DIDO-TE distinguishes trace relationships for successive Node Configurations.
 +  - The DIDO-TE distinguishes trace relationships for repeated Test Executions.
 +  - The DIDO-TE preserves historical trace relationships after a related item changes.
 +  - A correction to a trace relationship produces a distinguishable revision.
 +  - A correction to a trace relationship preserves the prior relationship.
 +  - The DIDO-TE detects a missing required trace relationship.
 +  - The DIDO-TE detects an incomplete trace relationship.
 +  - The DIDO-TE detects a broken trace relationship.
 +  - The DIDO-TE detects a duplicate trace relationship.
 +  - The DIDO-TE detects a conflicting trace relationship.
 +  - The DIDO-TE detects an ambiguous trace relationship.
 +  - The DIDO-TE detects an incorrectly directed trace relationship.
 +  - The DIDO-TE detects a misattributed trace relationship.
 +  - The DIDO-TE protects trace relationships from unauthorized alteration.
 +  - The DIDO-TE protects trace relationships from unauthorized disclosure.
 +  - The DIDO-TE protects trace relationships from unauthorized deletion.
 +  - The DIDO-TE supports traversal from a Node to each related item specified by the governing Test Definition.
 +  - The DIDO-TE supports traversal from a Test Result to each supporting Node, Test Execution, observation, decision, Test Definition, and source artifact.
 +  - The DIDO-TE supports traversal from an item of Evidence to each supporting Node, Test Execution, observation, decision, Test Definition, and source artifact.
 +  - The DIDO-TE supports reconstruction of the Node’s participation in the Test Environment.
 +  - The DIDO-TE retains each trace relationship for the period specified by the governing Test Definition.
 +  - A missing, incomplete, broken, conflicting, ambiguous, altered, or misattributed required trace relationship constitutes nonconformance with this requirement.
 +
 +===== Referenced By =====
 +
 +The following pages reference this requirement:
 +
 +{{backlinks>.#dido:03-dido-te}}
 +
 +===== Delivery Phase =====
 +
 +<todo>Assign the delivery phase.</todo>
 +
 +===== Implementation Status =====
 +
 +<todo>Assign the implementation status.</todo>
 +
 +===== Requirement Status =====
 +
 +<todo>The proposed derived requirement requires review and acceptance.</todo>
 +
 +----
 +
 +===== Issues =====
 +
 +<todo>Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.</todo>
 +
 +----
 +
 +===== Notes for Editors =====
 +
 +<code dokuwiki>
 +{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-013-maintain-node-traceability#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>