====== 19.6 Implementation Artefacts Prepared for Evidence ======

[[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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] by defining [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:a:audit|Audit]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], logging, generated-file, [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]], and review conventions.

Evidence preparation includes:

  - Traceability from implementation artefacts to FX logical elements
  - File headers that identify purpose and logical source
  - Generated-file headers that identify source definition and regeneration policy
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic mappings that identify [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoint]] realisation
  - [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] mappings that identify information-structure realisation
  - [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] mappings that identify communication behaviour expectations
  - Logging conventions that identify operational behaviour
  - [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]] conventions that identify processing outcomes
  - Audit and Provenance conventions that identify lineage and review context
  - Repository [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]] that distinguishes [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] and non-baseline material

Part 5 uses these conventions to collect and organise Evidence. Evidence may include [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] records, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] snapshots, execution logs, status reports, Audit records, Provenance records, [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]], replay results, review records, and acceptance records.

Part 4 does not create final Evidence packages. It defines the implementation hooks and conventions that make Evidence collection possible.

<WRAP centeralign>

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

</WRAP>