19.8 Relationship to Deployment, Testability, and Evidence Plan Summary

Return to Relationship to Deployment, Testability, and Evidence Plan

Part 4 and Part 5 work together but address different concerns.

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

Concern	Part 4 treatment	Part 5 treatment
Implementation artefacts	Defines artefacts, mappings, conventions, and Traceability	Deploys, executes, observes, and evidences selected artefacts
Deployment	Identifies deployment-relevant artefacts and Dependencies	Defines deployment topology, environment, packaging, startup, and runtime management
Testability	Defines implementation behaviours and mappings that tests must exercise	Defines test scenarios, Acceptance checks, execution procedures, and results
Observation	Defines status, logging, Exception Handling, and observability hooks	Defines how runtime behaviour is observed, collected, displayed, and reviewed
Evidence	Defines Traceability, Audit, Provenance, logging, and 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 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.