NOD-005g — Complete Node Execution

Go to NOD-005 — Execute a Node

Statement

The DIDO-TE SHALL complete each execution of a Node through an identified execution procedure.

Derived From

, 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)

Rationale

Completing Node execution establishes the controlled endpoint of the Node’s participation in an identified Test Execution.

The applicable Test Definition identifies the completion conditions, required final activities, expected outputs, time constraints, resulting Node state, and criteria governing successful, unsuccessful, interrupted, or terminated execution.

Completion includes finalizing Node activity, preserving required outputs and observations, releasing or retaining applicable Test Resources, closing or retaining Node Bindings as specified, and determining the resulting execution status.

Completion of Node execution does not necessarily stop the Node. The Node may remain ready for another execution, enter another permitted lifecycle state, or proceed through an identified stop or recovery procedure.

An incomplete, ambiguous, unauthorized, or unrecorded completion may leave active work, unresolved exceptions, uncollected outputs, allocated resources, or an unknown Node state. Such conditions may invalidate applicable Test Results or affect subsequent Test Execution.

Applies To

Verification

Verification confirms that:

The DIDO-TE uniquely identifies the Node whose execution is being completed.The DIDO-TE identifies the applicable Test Definition and Test Execution.The DIDO-TE uses an identified and approved execution-completion procedure.The Test Definition identifies the conditions governing completion of Node execution.The DIDO-TE determines whether the applicable completion conditions have been satisfied.The DIDO-TE distinguishes successful, unsuccessful, interrupted, timed-out, canceled, and terminated Node execution.The DIDO-TE prevents a Node execution from receiving a successful completion status when a mandatory completion condition remains unsatisfied.The DIDO-TE prevents new Node activity after execution reaches the applicable completion point.The DIDO-TE completes, cancels, or records each outstanding Node activity according to the applicable procedure.The DIDO-TE collects and preserves each required Node output, observation, log, finding, and exception.The DIDO-TE confirms the disposition of each applicable Test Input.The DIDO-TE confirms the disposition of each unresolved Test Execution Exception.The DIDO-TE closes, releases, or retains each Node Binding and Test Resource in accordance with the applicable Test Definition.The DIDO-TE identifies the actual Node state at completion.The DIDO-TE confirms that the resulting Node state permits the intended subsequent lifecycle or execution activity.The DIDO-TE detects residual activity, unintended connections, unreleased resources, incomplete outputs, or an unknown resulting Node state.The DIDO-TE identifies the effect of an unsuccessful, interrupted, timed-out, canceled, or terminated Node execution on the applicable Test Execution and Test Results.The DIDO-TE assigns a distinguishable completion status to the Node execution.The DIDO-TE prevents completion of Node execution from being treated as completion of the entire Test Execution unless the applicable Test Definition establishes that relationship.An unsuccessful completion leaves the Node in a known state or identifies the resulting state and required corrective action.The DIDO-TE records the Node identity, Test Execution, completion procedure, completion conditions, final activities, outputs, observations, timing, exceptions, resource dispositions, resulting Node state, findings, and completion status.Repeated completion under equivalent controlled conditions produces equivalent completion states within specified tolerances.The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node Configuration, Test Definition, Test Inputs, Node Bindings, Test Resources, Node activity, observations, outputs, exceptions, completion conditions, Test Outcome, Test Results, and resulting Evidence.An incomplete, incorrect, unsuccessful, unauthorized, ambiguous, or untraceable completion of Node execution constitutes nonconformance with this requirement.Verification includes:

Inspection of Node execution completion criteria and proceduresObservation of successful completion of Node executionObservation of unsuccessful or interrupted completionConfirmation that mandatory outputs, observations, logs, findings, and exceptions are preservedConfirmation of Test Input, Node Binding, and Test Resource dispositionsConfirmation of the actual resulting Node stateA negative assessment involving an unsatisfied mandatory completion conditionA negative assessment involving residual Node activityA negative assessment involving an unreleased Test Resource or unintended Node BindingConfirmation that unsuccessful completion does not produce a successful completion statusConfirmation that Node execution completion remains distinct from completion of the entire Test ExecutionInspection of completion records, Test Outcomes, Test Results, Evidence, and Traceability

Referenced By

Related Architecture Sections

Add links to the architecture sections governing completion of Node execution, Test Outcomes, Test Results, resource disposition, Node lifecycle control, Evidence, and Traceability.

Delivery Phase

Requirement Status

Draft

Statement Reference

Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-005-execute-a-node:nod-005g-complete-node-execution#Statement&noheader&nofooter&noeditbtn}}

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