====== NOD-009d — Handle a Node Resource-Control Exception ====== [[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 handle each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exception]] arising from the control of a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] resource using the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]]. ===== 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-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 ===== A resource-control exception arises when resource allocation, access, use, modification, restriction, suspension, restoration, retention, or release differs from a condition specified by the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]. Such conditions include an unavailable resource, unsuccessful allocation, unauthorized access, excessive consumption, exhaustion, contention, leakage, unsuccessful restriction, ineffective control action, unintended effect, or failure to release a resource. The governing Test Procedure specifies the actions used to detect, contain, classify, assess, correct, escalate, and disposition the exception. The disposition identifies whether the DIDO-TE continues, restricts, suspends, restores, retries, terminates, or invalidates the affected activity. Exception handling prevents a resource-control failure from changing test conditions without detection, affecting unrelated Nodes, exhausting shared resources, or allowing invalid Test Results to be treated as valid. The DIDO-TE preserves the distinction between the exception, its cause, its effects, and its disposition. A detected exception remains unresolved until the DIDO-TE verifies the required disposition and resulting resource and Node states. ===== 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_execution_exception_type|Test Execution Exception Type]] * [[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:a:authorizing_authority|Authorizing Authority]] * [[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 the resource-control conditions whose violation produces a Test Execution Exception. - The governing Test Procedure specifies the actions used to handle each resource-control exception. - The DIDO-TE uniquely identifies each resource-control exception. - The DIDO-TE identifies the affected Node and resource. - The DIDO-TE identifies the expected condition and the observed condition. - The DIDO-TE assigns a Test Execution Exception Type to each exception. - The DIDO-TE identifies the time, sequence, source, scope, severity, and potential effect of each exception. - The DIDO-TE identifies affected Nodes, resources, Test Environments, Test Executions, and Test Results. - The DIDO-TE contains or restricts the affected resource use when the governing Test Procedure requires containment or restriction. - The DIDO-TE prevents the exception from unnecessarily affecting unrelated Nodes, resources, or Test Executions. - The DIDO-TE retries a resource-control action only when the governing Test Procedure specifies a retry. - The DIDO-TE prevents unlimited, duplicate, or uncontrolled retries. - The DIDO-TE assigns a disposition to each resource-control exception. - Each disposition identifies the responsible Authorizing Authority, rationale, scope, required actions, and governing conditions. - The DIDO-TE verifies completion of each containment, corrective, recovery, termination, or escalation action. - The DIDO-TE determines the effect of the exception on affected Test Executions and Test Results. - The DIDO-TE identifies the resulting Node and resource states. - The DIDO-TE prevents closure of the exception without a disposition and supporting Evidence. - The DIDO-TE maintains Traceability among the Node, resource, governing Test Definition, governing Test Procedure, resource control, exception, disposition, corrective actions, Test Executions, Test Results, and resulting Evidence. - An undetected, unhandled, unauthorized, unresolved, incorrectly dispositioned, or untraceable resource-control exception constitutes nonconformance with this requirement. ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:03-dido-te}} ===== Delivery Phase ===== Assign the delivery phase. ===== Implementation Status ===== Assign the implementation status. ===== Requirement Status ===== The proposed derived requirement requires review and acceptance. ---- ===== Issues ===== Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register. ---- ===== Notes for Editors ===== {{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-009-control-node-resources:nod-009d-handle-a-node-resource-control-exception#Statement&noheader&nofooter&noeditbtn}} ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.