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

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-01-test-environment-requirements:env-005-emulate-distributed-systems:env-005c-emulate-communication-behaviour [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1dido: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 [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== ENV-005c — Emulate Communication Behaviour ======
  
 +[[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 behaviour 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-005b-emulate-participating-nodes|ENV-005b — Emulate Participating Nodes]]
 +  * [[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 behaviour affects the interactions among participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] in a distributed system.
 +
 +Relevant behaviour includes connection establishment, discovery, addressing, routing, message exchange, delivery guarantees, ordering, duplication handling, retry behaviour, acknowledgement, flow control, congestion response, and connection termination.
 +
 +Communication behaviour differs from communication failure. This requirement governs the nominal and bounded communication behaviour expected during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. ENV-005g governs the deliberate emulation of communication failures.
 +
 +The applicable Test Definition identifies each communication path and specifies the behaviour required for that path.
 +
 +===== 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 path subject to emulation.
 +  * Each communication path has a unique identity.
 +  * Each communication path identifies its source, destination, direction, interface, and protocol.
 +  * The Test Definition specifies the required discovery, connection, addressing, routing, and termination behaviour.
 +  * The Test Definition specifies the required message-delivery, ordering, acknowledgement, retry, and flow-control behaviour.
 +  * Each specified communication behaviour identifies its required value, state, sequence, range, or tolerance.
 +  * The DIDO-TE applies the specified communication behaviour to each applicable communication path.
 +  * The DIDO-TE observes actual communication behaviour during Test Execution.
 +  * The DIDO-TE detects communication behaviour outside the specified criteria or tolerances.
 +  * The DIDO-TE records communication-path identities, configurations, message interactions, applied conditions, measurements, and detected deviations 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 behaviour, communication path, participating Node, Test Definition, Test Execution, Evidence, and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
 +  * Missing, incorrect, unsupported, unobserved, or untraceable mandatory communication behaviour constitutes nonconformance with this requirement.
 +
 +Verification includes:
 +
 +  * Inspection of the communication paths identified by the Test Definition
 +  * Inspection of endpoints, directions, interfaces, protocols, and applicable communication criteria
 +  * Comparison of specified and applied communication behaviour
 +  * Observation of discovery, connection, message exchange, acknowledgement, retry, flow-control, and termination behaviour, as applicable
 +  * A negative assessment using incorrect message ordering or delivery behaviour
 +  * A negative assessment using incorrect acknowledgement, retry, or flow-control behaviour
 +  * Confirmation that the DIDO-TE detects and records each communication deviation
 +  * Inspection of communication Evidence and Traceability records
 +  * Confirmation that each mandatory communication deviation produces a nonconformance result
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== Related Architecture Sections =====
 +
 +  * Add links to the architecture sections governing communication paths, protocols, message exchange, communication quality, 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-005c-emulate-communication-behaviour#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>