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

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-010a-specify-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-010a-specify-a-node-fault [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== 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:start|Go to NOD-010 — Inject Node Faults]]
 +
 +===== Statement =====
 +
 +The governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] SHALL specify each [[dido:99_annexes:annex-b-terms-and-definitions:f:fault|Fault]] designated for introduction into a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] or a condition governing its operation.
 +
 +===== 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-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 =====
 +
 +Fault specification establishes the controlled conditions governing [[dido:99_annexes:annex-b-terms-and-definitions:f:fault_injection|Fault Injection]] before the DIDO-TE introduces the Fault.
 +
 +The Test Definition identifies the Fault, target Node, injection point, initiating condition, timing, duration, intensity, scope, expected effects, prohibited effects, termination conditions, and recovery conditions. It also identifies the observations and expected Node behaviour used to evaluate the effects of the Fault.
 +
 +The Fault specification distinguishes the deliberately introduced condition from the Node response and the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_outcome|Test Outcome]]. The occurrence of an expected response does not describe the Fault itself.
 +
 +A missing, ambiguous, incomplete, or internally inconsistent Fault specification prevents controlled preparation, authorization, injection, observation, containment, termination, recovery, and evaluation.
 +
 +===== 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_definition|Node Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]]
 +  * [[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_resource|Test Resource]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_outcome|Test Outcome]]
 +  * [[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 uniquely identifies each Fault designated for introduction.
 +  - The governing Test Definition uniquely identifies the target Node.
 +  - The governing Test Definition identifies whether the Fault affects the Node or a condition governing its operation.
 +  - The governing Test Definition identifies the injection point.
 +  - The governing Test Definition specifies the initiating condition, timing, duration, intensity, and scope of the Fault.
 +  - The governing Test Definition specifies each expected effect of the Fault.
 +  - The governing Test Definition specifies each prohibited effect of the Fault.
 +  - The governing Test Definition specifies the conditions that require suspension or termination of the Fault Injection.
 +  - The governing Test Definition specifies the conditions governing recovery.
 +  - The governing Test Definition identifies the expected Node states, activities, interactions, timing, outputs, and resource use used to evaluate the Node response.
 +  - The governing Test Definition identifies the observations required to establish that the Fault was introduced.
 +  - The governing Test Definition identifies the observations required to determine the actual effects of the Fault.
 +  - The governing Test Definition identifies the Nodes, Node Bindings, Dependencies, Test Resources, and Test Environment components permitted within the Fault scope.
 +  - The governing Test Definition identifies the Nodes, Node Bindings, Dependencies, Test Resources, and Test Environment components excluded from the Fault scope.
 +  - The Fault specification distinguishes the injected Fault from the expected Node response and Test Outcome.
 +  - The Fault specification contains no missing, ambiguous, conflicting, or unverifiable condition.
 +  - The DIDO-TE maintains Traceability among the Fault specification, target Node, Node Definition, Node Implementation, Node Configuration, governing Test Definition, governing Test Procedure, Test Environment, expected effects, prohibited effects, Test Outcomes, Test Results, and resulting Evidence.
 +  - A missing, ambiguous, incomplete, conflicting, incorrectly scoped, or untraceable Fault specification 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-010a-specify-a-node-fault#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>