dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:start

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:start [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:start [2026/08/18 13:59] (current) – nick_dido
Line 1: Line 1:
 +====== ENV-005 — Emulate Distributed Systems ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start|Go to C.3.1 Test Environment Requirements]]
 +
 +ENV-005 is a non-leaf requirement group governing the emulation of distributed-system conditions in accordance with the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
 +
 +Conformance is assessed against the individual leaf requirements listed below. ENV-005 does not establish a separate conformance obligation.
 +
 +===== Contents =====
 +
 +{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems#1|js navbar nocookie maxjs#1 id#dido_te_env_005_requirements_nav}}
 +
 +===== Source =====
 +
 +  * [[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 =====
 +
 +A distributed system comprises independently executing components whose behaviour depends on communication, coordination, timing, topology, resource availability, failure conditions, and changes in system membership.
 +
 +Testing a distributed system requires the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] to reproduce the conditions under which participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] interact.
 +
 +A Test Execution limited to nominal communication and infrastructure conditions provides insufficient support for assessing behaviour under delay, message loss, network partition, resource contention, Node failure, recovery, or topology change.
 +
 +Distributed-system emulation establishes controlled representations of participating Nodes, communication paths, infrastructure resources, external services, failure conditions, and recovery behaviour.
 +
 +The applicable Test Definition identifies the required emulation scope, Configuration, operating conditions, permitted variation, and acceptance criteria.
 +
 +The child requirements in this group define the individually verifiable obligations governing distributed topology, participating Nodes, communication behaviour, time, resources, failures, recovery, observation, Evidence, Traceability, and emulation fidelity.
 +
 +===== 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]]
 +
 +===== Traceability =====
 +
 +{{backlinks>.}}
 +
 +===== ConOps Relationship =====
 +
 +Add links to the ConOps activities and architecture sections governing distributed-system topology, Node interaction, communication, timing, resource conditions, fault injection, recovery, observation, Evidence, Traceability, and emulation fidelity.
 +
 +===== Delivery Phase =====
 +
 +Assign the applicable delivery phase.
 +
 +===== Requirement Status =====
 +
 +Draft
 +
 +===== Notes for Editors =====
 +
 +The subordinate leaf requirements define the normative obligations and corresponding verification criteria for ENV-005.
 +
 +The former ENV-005 Statement and Verification sections were removed because ENV-005 serves as a non-leaf requirement group and does not establish an independently verifiable conformance obligation.
 +
 +After you create and finalize all subordinate requirement pages, you may remove explicit child links because the ''indexmenu'' automatically discovers the leaf pages.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>