Table of Contents

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

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:

Verification includes:

Referenced By

Delivery Phase

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