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
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] – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-005-emulate-distributed-systems:start to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements: nick_didodido: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 ====== ====== ENV-005 — Emulate Distributed Systems ======
  
-[[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:start|Go to Test Environment Requirements]]+[[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]]
  
-===== Statement =====+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]].
  
-The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL emulate distributed systems 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.
  
-===== Derived From =====+===== 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-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
Line 17: Line 21:
 A distributed system comprises independently executing components whose behaviour depends on communication, coordination, timing, topology, resource availability, failure conditions, and changes in system membership. 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 Test Environment to reproduce the conditions under which its 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.+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.
  
-Distributed-system emulation establishes controlled representations of participating Nodes, communication paths, infrastructure resources, external services, failure conditions, and recovery behaviour. The applicable Test Definition specifies the required emulation scope, configuration, operating conditions, permitted variation, and acceptance criteria.+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.
  
-The child requirements decompose this requirement into individually verifiable obligations governing distributed topology, participating Nodes, communication behaviour, time, resources, failures, recovery, observation, evidence, and emulation fidelity.+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 ===== ===== Applies To =====
Line 35: Line 43:
   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  
-===== Contents ===== +===== Traceability =====
- +
-{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-005-emulate-distributed-systems#1|js navbar nocookie maxjs#1 id#dido_te_env_005_requirements_nav}} +
- +
-===== Verification ===== +
- +
-Verification confirms that: +
- +
-  * The applicable Test Definition identifies the distributed system subject to emulation. +
-  * The Test Definition identifies the participating Nodes, communication paths, infrastructure resources, external services, and system boundaries. +
-  * The Test Definition specifies the required topology, communication behaviour, time conditions, resource conditions, failure conditions, recovery behaviour, and permitted variation. +
-  * Each applicable child requirement has a conforming verification result. +
-  * The DIDO-TE establishes the specified distributed-system conditions before Test Execution. +
-  * The DIDO-TE maintains or changes those conditions according to the Test Definition during Test Execution. +
-  * The DIDO-TE observes interactions among participating Nodes and supporting Test Resources. +
-  * The DIDO-TE records the applied emulation configuration, actual conditions, interactions, changes, failures, and recovery events as [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. +
-  * The DIDO-TE validates the fidelity of the emulated conditions against the criteria specified by the Test Definition. +
-  * The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Test Definition, emulated conditions, participating Nodes, Test Execution, Evidence, and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]. +
-  * An unidentified, incorrectly configured, uncontrolled, unobserved, unsupported, or untraceable distributed-system condition constitutes nonconformance with this requirement. +
- +
-Verification includes: +
- +
-  * Inspection of the distributed-system model and Test Definition +
-  * Inspection of participating Nodes, communication paths, resources, services, and system boundaries +
-  * Comparison of specified and established distributed-system conditions +
-  * Observation of nominal distributed interactions +
-  * Observation of specified timing, resource, failure, partition, membership-change, and recovery conditions +
-  * Inspection of distributed-system observations and Evidence +
-  * Inspection of emulation-fidelity validation results +
-  * Inspection of Traceability records +
-  * Confirmation that each applicable child requirement has a conforming verification result +
-  * Confirmation that a missing or incorrectly emulated mandatory condition produces a nonconformance result +
- +
-===== Referenced By =====+
  
 {{backlinks>.}} {{backlinks>.}}
  
-===== Related Architecture Sections =====+===== ConOps Relationship =====
  
-  * Add links to the architecture sections governing distributed-system topology, Node interaction, communication, timing, resource conditions, fault injection, recovery, observation, Evidence, and Traceability.+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 ===== ===== Delivery Phase =====
Line 84: Line 59:
 Draft Draft
  
-===== Statement Reference =====+===== 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. 
 + 
 +----
  
-Use the following syntax to reference this requirement+<WRAP centeralign> 
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. 
 +</WRAP>
  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-01-test-environment-requirements/env-005-emulate-distributed-systems/start.1787081667.txt.gz
  • Last modified: 2026/08/18 12:34
  • by nick_dido