====== 19.4 Implementation Artefacts Prepared for Testability ======

[[fxdemo:04-part:start | Go To Top ]]

[[fxdemo:04-part:19-relationship-to-deployment-testability-and-evidence-plan:start | Return to Relationship to Deployment, Testability, and Evidence Plan ]]

Part 4 prepares implementation artefacts for testability by identifying the implementation mappings and observable behaviours that tests must exercise.

Testability preparation covers:

  - Implementation participants
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics
  - [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures and generated types
  - [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] profile expectations
  - Interaction realisations
  - Logging behaviour
  - [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]] behaviour
  - [[dido:99_annexes:annex-b-terms-and-definitions:a:audit|Audit]] and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] expectations
  - [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships

Part 5 uses those implementation definitions to design test scenarios, demonstration flows, acceptance checks, negative checks, compatibility checks, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection.

Part 4 does not execute tests or record test outcomes. Part 5 defines the testability approach and captures test-related Evidence.

<WRAP centeralign>

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

</WRAP>