dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:nod-010e-control-a-node-fault

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-010-inject-node-faults:nod-010e-control-a-node-fault [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-010-inject-node-faults:nod-010e-control-a-node-fault [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== NOD-010e — Control a Node Fault ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:start|Go to NOD-010 — Inject Node Faults]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL control each introduced [[dido:99_annexes:annex-b-terms-and-definitions:f:fault|Fault]] 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-010-inject-node-faults:start|NOD-010 — Inject Node Faults]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:nod-010a-specify-a-node-fault|NOD-010a — Specify a Node Fault]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:nod-010b-authorize-node-fault-injection|NOD-010b — Authorize Node Fault Injection]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:nod-010c-prepare-node-fault-injection|NOD-010c — Prepare Node Fault Injection]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-010-inject-node-faults:nod-010d-inject-a-node-fault|NOD-010d — Inject a Node Fault]]
 +  * [[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 =====
 +
 +Control of an introduced Fault maintains its timing, duration, intensity, scope, and effects within the conditions specified by the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
 +
 +Fault control begins when the DIDO-TE introduces the Fault and continues until the Fault terminates or the governing Test Procedure completes the required containment or removal actions.
 +
 +The DIDO-TE observes the introduced Fault separately from the Node response. This distinction allows the DIDO-TE to determine whether a difference in Node behaviour results from the specified Fault, an incorrectly introduced Fault, or another condition.
 +
 +Control actions include maintaining, varying, restricting, suspending, resuming, containing, or terminating the Fault. The governing Test Procedure identifies which actions the DIDO-TE performs and the conditions that initiate each action.
 +
 +An unexpected expansion, persistence, interruption, reduction, or intensification of the Fault constitutes a Test Execution Exception. The DIDO-TE contains such a condition before it affects targets outside the authorized scope.
 +
 +===== Applies To =====
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:f:fault|Fault]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:f:fault_injection|Fault Injection]]
 +  * [[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: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 DIDO-TE uniquely identifies each introduced Fault.
 +  - The DIDO-TE associates the Fault with its authorization, target Node, Test Definition, Test Procedure, and Fault Injection.
 +  - The DIDO-TE observes the actual presence, timing, duration, intensity, and scope of the Fault.
 +  - The DIDO-TE distinguishes the introduced Fault from the observed Node response.
 +  - The DIDO-TE maintains the Fault within the timing, duration, intensity, and scope specified by the governing Test Definition.
 +  - The DIDO-TE prevents the Fault from affecting an unauthorized Node, Node Binding, Dependency, Test Resource, Test Environment, or Test Execution.
 +  - The DIDO-TE applies each Fault-control action when the condition specified by the governing Test Procedure occurs.
 +  - The DIDO-TE verifies the target before applying a Fault-control action.
 +  - The DIDO-TE maintains, varies, restricts, suspends, resumes, contains, or terminates the Fault only through an authorized procedure.
 +  - The DIDO-TE observes the actual effect of each Fault-control action.
 +  - The DIDO-TE detects a difference between the intended and actual effect of a Fault-control action.
 +  - The DIDO-TE detects an unexpected expansion, persistence, interruption, reduction, or intensification of the Fault.
 +  - The DIDO-TE detects an unexpected or prohibited effect of the Fault.
 +  - The DIDO-TE initiates exception handling when the Fault differs from its specification or authorization.
 +  - The DIDO-TE prevents an unauthorized, duplicate, conflicting, mistimed, or out-of-sequence Fault-control action.
 +  - The DIDO-TE prevents the Fault from continuing after a termination condition occurs.
 +  - An unsuccessful control action leaves the Fault, Node, and affected Test Environment components in known states or identifies their actual states and required corrective action.
 +  - The DIDO-TE determines the effect of each Fault-control action or deviation on affected Test Executions, Test Outcomes, Test Results, and Evidence.
 +  - The DIDO-TE maintains Traceability among the Fault, Fault Injection, authorization, target Node, governing Test Definition, governing Test Procedure, observations, control actions, exceptions, Test Outcomes, Test Results, and resulting Evidence.
 +  - Missing, delayed, incomplete, ineffective, incorrectly scoped, unauthorized, or untraceable control of an introduced Fault 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-010-inject-node-faults:nod-010e-control-a-node-fault#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>