TWIN-010 — Maintain Twin Traceability

The DIDO-TE SHALL maintain Traceability among each Twin Identity, its associated Twin Realizations, and the Test Results produced using those Twin Realizations.

A Twin Identity may be represented by more than one Twin Realization during different Test Executions or different portions of a Test Execution.

Meaningful comparison, reproduction, validation, and audit therefore require the DIDO-TE to retain the relationship between the logical Twin Identity and the particular Twin Realization that participated in a test.

The resulting Test Results must remain attributable to the Twin Realization that produced them and to the Twin Identity represented by that realization.

Traceability remains independent of whether the Twin Realization is virtual, physical, simulated, or otherwise realized.

Verification confirms that:

  1. Each Twin Realization used during Test Execution is traceable to its Twin Identity.
  2. Each Twin Realization used during Test Execution is identifiable by its Twin Realization Identifier.
  3. Each Test Result produced using a Twin Realization is traceable to that Twin Realization.
  4. Each Test Result produced using a Twin Realization is traceable through that realization to the corresponding Twin Identity.
  5. Traceability distinguishes Test Results produced by different Twin Realizations associated with the same Twin Identity.
  6. Traceability is preserved when different Twin Realizations of the same Twin Identity are selected for different Test Executions.

Verification includes at least two Twin Realizations associated with the same Twin Identity, uses the realizations in separate Test Executions, and confirms that the resulting Test Results remain attributable to the correct Twin Realization and Twin Identity.

This requirement supports reproducibility, comparison, validation, evidence generation, and audit by preserving the relationship among Twin Identity, Twin Realization, Test Execution, and Test Result.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-maintain-twin-traceability#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-03-twin-node-requirements/twin-010-maintain-twin-traceability/start.txt
  • Last modified: 2026/08/22 14:31
  • by nick_dido