====== 19.8 Relationship to Deployment, Testability, and Evidence Plan Summary ======

[[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 and Part 5 work together but address different concerns.

<WRAP centeralign>

**Table 19-1: Boundary between Part 4 and Part 5**

</WRAP>

^ Concern ^ Part 4 treatment ^ Part 5 treatment ^
| Implementation artefacts | Defines artefacts, mappings, conventions, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | Deploys, executes, observes, and evidences selected artefacts |
| [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] | Identifies deployment-relevant artefacts and [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] | Defines deployment topology, environment, packaging, startup, and runtime management |
| Testability | Defines implementation behaviours and mappings that tests must exercise | Defines test scenarios, [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance]] checks, execution procedures, and results |
| [[dido:99_annexes:annex-b-terms-and-definitions:o:observation|Observation]] | Defines status, logging, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], and observability hooks | Defines how runtime behaviour is observed, collected, displayed, and reviewed |
| [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | Defines Traceability, [[dido:99_annexes:annex-b-terms-and-definitions:a:audit|Audit]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], logging, and [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] conventions | Defines Evidence collection, preservation, review, and Evidence packages |
| Scripts | Defines script categories and expected behaviour | Uses scripts in Deployment, execution, testing, Observation, and Evidence [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflows]] |
| Developer Handbook | Defines required development discipline before coding | Uses handbook-conformant artefacts as inputs to Deployment and Evidence planning |

The Phase 0 Implementation Profile prepares implementation artefacts for Deployment, testability, Observation, operation, and Evidence. The Deployment, Testability, and Evidence Plan defines how the Phase 0 environment uses those artefacts.

<WRAP centeralign>

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

</WRAP>