NOD-013 — Maintain Node Traceability

Go to Node Requirements

The DIDO-TE SHALL maintain each trace relationship specified for a Node by the governing Test Definition.

• [DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
• [DTE6] Structured Information Processing Reference Architecture (SIP-RA)
• [DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Node Traceability preserves the explicit relationships required to reconstruct and evaluate a Node’s participation in a 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 Node Definition, Node Implementation, Node Configuration, Node Bindings, Dependencies, Test Resources, governing Test Definitions, and governing Test Procedures.

Other required relationships connect the Node to authorization, configuration, validation, readiness, lifecycle control, execution, observation, resource control, 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.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Node Configuration
• Node Binding
• Dependency
• Test Definition
• Test Procedure
• Test Environment
• Test Execution
• Test Execution Exception
• Test Input
• Test Resource
• Test Outcome
• Test Result
• Authorizing Authority
• Fault
• Fault Injection
• Evidence
• Traceability

Verification confirms that:

1. The governing Test Definition identifies each trace relationship required for the Node.
2. Each trace relationship uniquely identifies its source item.
3. Each trace relationship uniquely identifies its target item.
4. Each trace relationship identifies the nature of the relationship.
5. Each directed trace relationship identifies its direction.
6. Each trace relationship identifies its governing context.
7. The DIDO-TE maintains each trace relationship specified by the governing Test Definition.
8. The DIDO-TE maintains each required relationship between the Node and its Node Definition.
9. The DIDO-TE maintains each required relationship between the Node and its Node Implementation.
10. The DIDO-TE maintains each required relationship between the Node and its Node Configuration.
11. The DIDO-TE maintains each required relationship between the Node and its Node Bindings.
12. The DIDO-TE maintains each required relationship between the Node and its Dependencies.
13. The DIDO-TE maintains each required relationship between the Node and its Test Resources.
14. The DIDO-TE maintains each required relationship between the Node and its governing Test Definitions.
15. The DIDO-TE maintains each required relationship between the Node and its governing Test Procedures.
16. The DIDO-TE maintains each required relationship between the Node and its authorizations.
17. The DIDO-TE maintains each required relationship between the Node and its configuration records.
18. The DIDO-TE maintains each required relationship between the Node and its validation records.
19. The DIDO-TE maintains each required relationship between the Node and its readiness records.
20. The DIDO-TE maintains each required relationship between the Node and its lifecycle records.
21. The DIDO-TE maintains each required relationship between the Node and its isolation records.
22. The DIDO-TE maintains each required relationship between the Node and its reset records.
23. The DIDO-TE maintains each required relationship between the Node and each Test Environment in which it participates.
24. The DIDO-TE maintains each required relationship between the Node and each Test Execution in which it participates.
25. The DIDO-TE maintains each required relationship between the Node and each Test Input supplied to it.
26. The DIDO-TE maintains each required relationship between the Node and each identified activity.
27. The DIDO-TE maintains each required relationship between the Node and each identified interaction.
28. The DIDO-TE maintains each required relationship between the Node and each identified state transition.
29. The DIDO-TE maintains each required relationship between the Node and each identified control action.
30. The DIDO-TE maintains each required relationship between the Node and each identified observation.
31. The DIDO-TE maintains each required relationship between the Node and each identified output.
32. The DIDO-TE maintains each required relationship between the Node and each resource allocation.
33. The DIDO-TE maintains each required relationship between the Node and each resource-use observation.
34. The DIDO-TE maintains each required relationship between the Node and each resource-control action.
35. The DIDO-TE maintains each required relationship between the Node and each resource release.
36. The DIDO-TE maintains each required relationship between the Node and each Fault specification.
37. The DIDO-TE maintains each required relationship between the Node and each Fault Injection.
38. The DIDO-TE maintains each required relationship between the Node and each Fault-control action.
39. The DIDO-TE maintains each required relationship between the Node and each Fault-recovery action.
40. The DIDO-TE maintains each required relationship between the Node and each preserved state representation.
41. The DIDO-TE maintains each required relationship between the Node and each state-preservation action.
42. The DIDO-TE maintains each required relationship between the Node and each Test Execution Exception affecting it.
43. The DIDO-TE maintains each required relationship between a Test Execution Exception and its Test Execution Exception Type.
44. The DIDO-TE maintains each required relationship between a Test Execution Exception and its disposition.
45. The DIDO-TE maintains each required relationship between the Node and each Test Outcome.
46. The DIDO-TE maintains each required relationship between the Node and each Test Result.
47. The DIDO-TE maintains each required relationship between the Node and each item of Evidence.
48. The DIDO-TE distinguishes trace relationships for replacement Nodes.
49. The DIDO-TE distinguishes trace relationships for replica Nodes.
50. The DIDO-TE distinguishes trace relationships for restarted Node instances.
51. The DIDO-TE distinguishes trace relationships for concurrently executing Node instances.
52. The DIDO-TE distinguishes trace relationships for successive Node Configurations.
53. The DIDO-TE distinguishes trace relationships for repeated Test Executions.
54. The DIDO-TE preserves historical trace relationships after a related item changes.
55. A correction to a trace relationship produces a distinguishable revision.
56. A correction to a trace relationship preserves the prior relationship.
57. The DIDO-TE detects a missing required trace relationship.
58. The DIDO-TE detects an incomplete trace relationship.
59. The DIDO-TE detects a broken trace relationship.
60. The DIDO-TE detects a duplicate trace relationship.
61. The DIDO-TE detects a conflicting trace relationship.
62. The DIDO-TE detects an ambiguous trace relationship.
63. The DIDO-TE detects an incorrectly directed trace relationship.
64. The DIDO-TE detects a misattributed trace relationship.
65. The DIDO-TE protects trace relationships from unauthorized alteration.
66. The DIDO-TE protects trace relationships from unauthorized disclosure.
67. The DIDO-TE protects trace relationships from unauthorized deletion.
68. The DIDO-TE supports traversal from a Node to each related item specified by the governing Test Definition.
69. The DIDO-TE supports traversal from a Test Result to each supporting Node, Test Execution, observation, decision, Test Definition, and source artifact.
70. The DIDO-TE supports traversal from an item of Evidence to each supporting Node, Test Execution, observation, decision, Test Definition, and source artifact.
71. The DIDO-TE supports reconstruction of the Node’s participation in the Test Environment.
72. The DIDO-TE retains each trace relationship for the period specified by the governing Test Definition.
73. A missing, incomplete, broken, conflicting, ambiguous, altered, or misattributed required trace relationship constitutes nonconformance with this requirement.

The following pages reference this requirement:

Assign the delivery phase.

Assign the implementation status.

The proposed derived requirement requires review and acceptance.

Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-013-maintain-node-traceability#Statement&noheader&nofooter&noeditbtn}}