Differences

This shows you the differences between two versions of the page.

--- dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:env-005g-emulate-communication-failures [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:env-005g-emulate-communication-failures [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== ENV-005g — Emulate Communication Failures ======
+[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:start|Go to ENV-005 — Emulate Distributed Systems]]
+===== Statement =====
+The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL emulate communication failures in accordance with the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
+===== Derived From =====
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:start|ENV-005 — Emulate Distributed Systems]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:env-005a-emulate-distributed-topology|ENV-005a — Emulate Distributed Topology]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:env-005c-emulate-communication-behaviour|ENV-005c — Emulate Communication Behaviour]]
+  * [[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 =====
+Communication failures alter or prevent interactions among otherwise operating participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]].
+Relevant failures include connection refusal, connection termination, message loss, message corruption, duplication, reordering, delay, jitter, bandwidth restriction, acknowledgement loss, routing failure, discovery failure, asymmetric reachability, and intermittent connectivity.
+Controlled emulation permits assessment of retry, timeout, buffering, deduplication, ordering, error handling, degradation, failover, and recovery behaviour.
+A communication failure may affect an individual message, communication path, interface, protocol, or endpoint. ENV-005h separately governs a network partition that divides Nodes into mutually isolated or asymmetrically connected groups.
+The applicable Test Definition identifies each affected communication path, failure type, direction, trigger, duration, extent, rate, and required restoration condition.
+===== Applies To =====
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
+===== Verification =====
+Verification confirms that:
+  * The applicable Test Definition identifies each communication failure subject to emulation.
+  * Each specified communication failure has a unique identity.
+  * The Test Definition identifies each affected communication path, source, destination, direction, interface, and protocol.
+  * The Test Definition specifies the failure type, trigger, initiation point, duration, extent, rate, and termination condition.
+  * The Test Definition specifies whether the failure affects all communications or a defined subset of messages, message types, endpoints, or paths.
+  * The Test Definition specifies the required restoration condition following the communication failure.
+  * The DIDO-TE establishes the required pre-failure communication state.
+  * The DIDO-TE initiates each communication failure at the specified event, state, or time.
+  * The DIDO-TE applies each failure only to the specified communication scope.
+  * The DIDO-TE maintains each communication failure for its specified duration or until its specified termination condition occurs.
+  * The DIDO-TE observes affected and unaffected communications during the failure.
+  * The DIDO-TE restores communication to the specified state when the failure terminates.
+  * The DIDO-TE distinguishes an injected communication failure from an unintended Test Environment failure.
+  * The DIDO-TE detects a failure that does not begin, persist, affect communications, terminate, or recover as specified.
+  * The DIDO-TE records the failure identity, affected paths, failure type, trigger, initiation time, duration, affected communications, observed responses, termination, and restoration as [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
+  * The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among each communication failure, affected paths and Nodes, Test Definition, Test Execution, Evidence, and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
+  * A missing, incorrect, uncontrolled, unobserved, unsupported, or untraceable mandatory communication failure constitutes nonconformance with this requirement.
+Verification includes:
+  * Inspection of the communication failures specified by the Test Definition
+  * Inspection of affected paths, endpoints, directions, protocols, failure types, triggers, durations, rates, and restoration conditions
+  * Observation of communication before, during, and after each failure
+  * Emulation of message loss, delay, duplication, reordering, or corruption when specified
+  * Emulation of connection refusal, termination, discovery failure, routing failure, or intermittent connectivity when specified
+  * Testing that unaffected communication paths remain within their specified conditions
+  * Testing restoration of communication following failure termination
+  * Confirmation that the DIDO-TE detects an incorrectly initiated, scoped, sustained, terminated, or restored failure
+  * Inspection of communication-failure Evidence and Traceability records
+  * Confirmation that each mandatory communication-failure deviation produces a nonconformance result
+===== Referenced By =====
+{{backlinks>.}}
+===== Related Architecture Sections =====
+  * Add links to the architecture sections governing communication paths, fault injection, communication quality, failure handling, recovery, Evidence, and Traceability.
+===== Delivery Phase =====
+Assign the applicable delivery phase.
+===== Requirement Status =====
+Draft
+===== Statement Reference =====
+Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:
+<code dokuwiki>
+{{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-005-emulate-distributed-systems:env-005g-emulate-communication-failures#Statement&noheader&nofooter&noeditbtn}}
+</code>
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>