dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005g-complete-node-execution

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005g-complete-node-execution [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-005-execute-a-node:nod-005g-complete-node-execution [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== NOD-005g — Complete Node Execution ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:start|Go to NOD-005 — Execute a Node]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL complete each execution of a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] through an identified execution procedure.
 +
 +===== Derived From =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:start|NOD-005 — Execute a Node]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005a-authorize-node-execution|NOD-005a — Authorize Node Execution]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005b-initiate-node-execution|NOD-005b — Initiate Node Execution]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005c-provide-node-inputs|NOD-005c — Provide Node Inputs]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005d-observe-node-execution|NOD-005d — Observe Node Execution]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005e-control-node-execution|NOD-005e — Control Node Execution]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005f-handle-a-node-execution-exception|NOD-005f — Handle a Node Execution Exception]]
 +  * [[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 =====
 +
 +Completing Node execution establishes the controlled endpoint of the Node’s participation in an identified [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].
 +
 +The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] or affect subsequent Test Execution.
 +
 +===== 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:t:test_definition|Test Definition]]
 +  * [[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_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_outcome|Test Outcome]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
 +  * [[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 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 procedures
 +  * Observation of successful completion of Node execution
 +  * Observation of unsuccessful or interrupted completion
 +  * Confirmation that mandatory outputs, observations, logs, findings, and exceptions are preserved
 +  * Confirmation of Test Input, Node Binding, and Test Resource dispositions
 +  * Confirmation of the actual resulting Node state
 +  * A negative assessment involving an unsatisfied mandatory completion condition
 +  * A negative assessment involving residual Node activity
 +  * A negative assessment involving an unreleased Test Resource or unintended Node Binding
 +  * Confirmation that unsuccessful completion does not produce a successful completion status
 +  * Confirmation that Node execution completion remains distinct from completion of the entire Test Execution
 +  * Inspection of completion records, Test Outcomes, Test Results, Evidence, and Traceability
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== 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 =====
 +
 +<todo>Assign the applicable delivery phase.</todo>
 +
 +===== Requirement Status =====
 +
 +Draft
 +
 +===== Statement Reference =====
 +
 +Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:
 +
 +<code dokuwiki>
 +{{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}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>