NOD-007 — Identify a Node

Go to Node Requirements

The DIDO-TE SHALL uniquely identify each Node that participates in a Test Environment or Test Execution.

• [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)

Unique Node identification distinguishes each Node from every other Node participating in a Test Environment or Test Execution.

The identity of a Node provides a stable basis for associating the Node with its Node Definition, Node Implementation, Node Configuration, Node Bindings, lifecycle state, Test Inputs, Test Resources, observations, outputs, control actions, exceptions, and Test Results.

A Node identity distinguishes the Node from its definition, implementation, configuration, deployment location, network address, execution process, and other properties that change during the Node lifecycle. A change to one of these properties does not, by itself, establish a different Node identity.

A replacement, replica, restarted instance, or concurrently executing instance requires an identity relationship that distinguishes the participating Node instance while preserving its relationship to the applicable Node Definition, Node Implementation, and Node Configuration.

Unambiguous identification prevents observations, control actions, inputs, outputs, exceptions, Test Results, and Evidence from being attributed to the wrong Node. It also supports reconstruction, repeatability, accountability, and Traceability across Test Executions.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Node Configuration
• Node Binding
• Test Definition
• Test Environment
• Test Execution
• Test Input
• Test Resource
• Test Execution Exception
• Test Result
• Evidence
• Traceability

Verification confirms that:

1. Each Node participating in a Test Environment or Test Execution has an identifier.
2. Each Node identifier is unique within the applicable identification scope.
3. The applicable identification scope is explicitly specified.
4. The DIDO-TE prevents two participating Nodes from using the same identifier within the applicable identification scope.
5. The DIDO-TE distinguishes the identity of a Node from the identity of its Node Definition, Node Implementation, Node Configuration, Node Bindings, deployment location, execution process, and network address.
6. The DIDO-TE associates each Node with its applicable Node Definition.
7. The DIDO-TE associates each Node with its applicable Node Implementation.
8. The DIDO-TE associates each Node with its applicable Node Configuration.
9. The DIDO-TE associates each Node with its applicable Node Bindings.
10. The DIDO-TE associates each Node with the Test Environments and Test Executions in which it participates.
11. The DIDO-TE preserves the identity of a Node when a mutable Node property changes without establishing a different Node.
12. The DIDO-TE distinguishes a replacement, replica, restarted instance, or concurrent instance when the distinction affects Test Execution, Test Results, or Evidence.
13. The DIDO-TE preserves the relationship between each participating Node instance and its applicable Node Definition, Node Implementation, and Node Configuration.
14. The DIDO-TE identifies the Node associated with each material Test Input, Test Resource, observation, output, control action, lifecycle-state change, Test Execution Exception, and Test Result.
15. The DIDO-TE uses the Node identity consistently throughout authorization, initiation, execution, observation, control, isolation, completion, and recording activities.
16. The DIDO-TE detects a missing, duplicate, conflicting, malformed, unauthorized, expired, or ambiguous Node identifier.
17. The DIDO-TE prevents a Node with a missing, duplicate, conflicting, malformed, unauthorized, expired, or ambiguous identifier from participating in Test Execution.
18. The DIDO-TE detects an attempt to attribute Node activity, observations, outputs, exceptions, or Test Results to a different Node.
19. A change to a Node identifier produces a distinguishable record that preserves the prior identifier and the reason for the change.
20. The DIDO-TE records the Node identifier, identification scope, applicable Node Definition, Node Implementation, Node Configuration, Node Bindings, Test Environment, Test Executions, and changes to identification information.
21. The DIDO-TE maintains Traceability among the Node identity, Node Definition, Node Implementation, Node Configuration, Node Bindings, Test Definition, Test Environment, Test Execution, Test Inputs, Test Resources, observations, outputs, exceptions, Test Results, and resulting Evidence.
22. A missing, duplicate, conflicting, unauthorized, ambiguous, incorrectly attributed, or untraceable Node identity constitutes nonconformance with this requirement.

The following pages reference this requirement:

Assign the applicable 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.

Specify the identification scope within which each Node identifier must be unique.

Use the following DokuWiki section-transclusion syntax to reference this requirement’s Statement section:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-007-identify-a-node#Statement&noheader&nofooter&noeditbtn}}