NOD-009e — Release Node Resources [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== NOD-009e — Release Node Resources ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:start|Go to NOD-009 — Control Node Resources]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL release each resource assigned to a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] when the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] requires its release.

===== Derived From =====

  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:start|NOD-009 — Control Node Resources]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:nod-009a-establish-node-resource-controls|NOD-009a — Establish Node Resource Controls]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:nod-009b-allocate-node-resources|NOD-009b — Allocate Node Resources]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:nod-009c-control-node-resource-use|NOD-009c — Control Node Resource Use]]
  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-009-control-node-resources:nod-009d-handle-a-node-resource-control-exception|NOD-009d — Handle a Node Resource-Control 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 =====

Releasing a Node resource ends the Node’s allocation, access, occupation, use, or control of that resource under the conditions specified by the governing Test Definition.

The governing Test Definition identifies the event, state, time, completion condition, exception disposition, or decision that requires release. The governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]] specifies the actions used to release the resource and verify its resulting state.

Release prevents unnecessary retention, exhaustion, contention, unauthorized reuse, lingering access, and interference with later Test Executions. It also allows a shared resource to become available for another authorized use.

Release may require the DIDO-TE to revoke access, terminate a session, close an interface, remove a binding, clear temporary information, return capacity, or restore the resource to a specified state. Those actions remain governed by the Test Procedure.

A release is incomplete until the DIDO-TE verifies that the Node no longer possesses prohibited access or control and that the resource occupies the resulting state specified by the governing Test Definition.

===== 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_configuration|Node Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependency]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]]
  * [[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_resource|Test Resource]]
  * [[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 governing Test Definition identifies each resource requiring release.
  - The governing Test Definition identifies the Node from which each resource requires release.
  - The governing Test Definition specifies the event, state, time, completion condition, exception disposition, or decision that triggers release.
  - The governing Test Definition specifies the required resulting state of the released resource.
  - The governing Test Procedure specifies the actions used to release the resource.
  - The DIDO-TE uniquely identifies the Node and resource before performing the release.
  - The DIDO-TE releases the resource when the specified release condition occurs.
  - The DIDO-TE revokes the Node’s access to the resource when the governing Test Definition requires revocation.
  - The DIDO-TE ends the Node’s allocation, occupation, use, or control of the resource.
  - The DIDO-TE removes or closes associated Node Bindings, sessions, interfaces, credentials, or access paths specified by the governing Test Procedure.
  - The DIDO-TE returns reusable resource quantity or capacity to the controlled resource pool.
  - The DIDO-TE verifies that the Node no longer possesses prohibited access to the released resource.
  - The DIDO-TE verifies that the resource reaches the resulting state specified by the governing Test Definition.
  - The DIDO-TE detects a delayed, incomplete, unsuccessful, misdirected, unauthorized, or bypassed release.
  - The DIDO-TE detects residual allocation, access, occupation, use, retention, or control after release.
  - The DIDO-TE prevents release of a resource from unnecessarily affecting an unrelated Node or Test Execution.
  - The DIDO-TE determines the effect of an unsuccessful release on affected Nodes, resources, Test Executions, and Test Results.
  - An unsuccessful release leaves the Node and resource in known states or identifies their actual states and required corrective action.
  - The DIDO-TE maintains Traceability among the Node identity, resource identity, governing Test Definition, governing Test Procedure, allocation, resource use, release condition, release actions, resulting state, Test Executions, Test Results, and resulting Evidence.
  - A missing, delayed, incomplete, unsuccessful, misdirected, unauthorized, bypassed, or untraceable resource release constitutes nonconformance with this requirement.

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:03-dido-te}}

===== Delivery Phase =====

<todo>Assign the delivery phase.</todo>

===== Implementation Status =====

<todo>Assign the implementation status.</todo>

===== Requirement Status =====

<todo>The proposed derived requirement requires review and acceptance.</todo>

----

===== Issues =====

<todo>Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.</todo>

----

===== Notes for Editors =====

<code dokuwiki>
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-009-control-node-resources:nod-009e-release-node-resources#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>