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

The DIDO-TE SHALL emulate the distributed topology specified by the applicable Test Definition.

A distributed topology defines the participating 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 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.

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 Evidence.
  • The DIDO-TE maintains Traceability among the topology, participating Nodes, communication paths, Test Definition, Test Execution, Evidence, and 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
  • Add links to the architecture sections governing distributed topology, Nodes, communication paths, boundaries, Evidence, and Traceability.

Assign the applicable delivery phase.

Draft

Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:

{{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}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • 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.txt
  • Last modified: 2026/08/18 12:34
  • by nick_dido