Differences
This shows you the differences between two versions of the page.
| 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-009-control-node-resources:nod-009d-handle-a-node-resource-control-exception [2026/08/17 14:20] – removed - external edit (Unknown date) 127.0.0.1 | 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 [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-009d — Handle a Node Resource-Control Exception ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A resource-control exception arises when resource allocation, access, use, modification, | ||
| + | |||
| + | Such conditions include an unavailable resource, unsuccessful allocation, unauthorized access, excessive consumption, | ||
| + | |||
| + | 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: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== 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, | ||
| + | - 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, | ||
| + | - 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, | ||
| + | - An undetected, unhandled, unauthorized, | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | The following pages reference this requirement: | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ===== Implementation Status ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Issues ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Notes for Editors ===== | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||