====== 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: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 the distributed topology specified by 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-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 topology defines the participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], their communication paths, their logical and physical relationships, and the boundaries across which they interact.

Topology influences reachability, routing, communication latency, fault propagation, dependency relationships, trust boundaries, and system behaviour. A difference between the specified topology and the emulated topology may change the behaviour observed during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

The applicable Test Definition identifies the required topology, relationships, boundaries, connection states, and permitted variation. Topology emulation establishes those conditions without requiring every element to use its production implementation.

===== 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 the distributed topology subject to emulation.
  * The specified topology identifies each participating Node and Test Resource.
  * The specified topology identifies each communication path.
  * The specified topology identifies the endpoints of each communication path.
  * The specified topology identifies applicable logical, physical, administrative, security, jurisdictional, and network boundaries.
  * The specified topology identifies required connection states and permitted topology variation.
  * Each emulated topology element has a unique identity.
  * The DIDO-TE establishes each required topology element and relationship before Test Execution.
  * The DIDO-TE verifies the reachability and connection state of each applicable topology element.
  * The DIDO-TE detects a missing, additional, substituted, misplaced, incorrectly connected, or unreachable topology element.
  * The DIDO-TE records the specified and emulated topologies 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 the topology, participating Nodes, communication paths, Test Definition, Test Execution, Evidence, and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
  * A missing, additional, incorrectly connected, unsupported, or untraceable mandatory topology element constitutes nonconformance with this requirement.

Verification includes:

  * Inspection of the distributed topology specified by the Test Definition
  * Inspection of participating Nodes, Test Resources, communication paths, endpoints, and boundaries
  * Comparison of the specified and emulated topologies
  * Observation of reachability and connection-state checks
  * A negative assessment with a missing or additional topology element
  * A negative assessment with an incorrectly connected or unreachable topology element
  * Confirmation that the DIDO-TE detects and records each topology deviation
  * Inspection of topology Evidence and Traceability records
  * Confirmation that each mandatory topology deviation produces a nonconformance result

===== Referenced By =====

{{backlinks>.}}

===== Related Architecture Sections =====

  * Add links to the architecture sections governing distributed topology, Nodes, communication paths, boundaries, 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-005a-emulate-distributed-topology#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>