19.6 Implementation Artefacts Prepared for Evidence

Go To Top

Return to Relationship to Deployment, Testability, and Evidence Plan

Part 4 prepares implementation artefacts for Evidence by defining Traceability, Audit, Provenance, logging, generated-file, Repository, and review conventions.

Evidence preparation includes:

1. Traceability from implementation artefacts to FX logical elements
2. File headers that identify purpose and logical source
3. Generated-file headers that identify source definition and regeneration policy
4. DDS Topic mappings that identify Endpoint realisation
5. IDL mappings that identify information-structure realisation
6. QoS mappings that identify communication behaviour expectations
7. Logging conventions that identify operational behaviour
8. Exception Handling conventions that identify processing outcomes
9. Audit and Provenance conventions that identify lineage and review context
10. Repository Workflow that distinguishes Baseline and non-baseline material

Part 5 uses these conventions to collect and organise Evidence. Evidence may include Deployment records, Configuration snapshots, execution logs, status reports, Audit records, Provenance records, 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.