19.2 Boundary Between Part 4 and Part 5 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== 19.2 Boundary Between Part 4 and Part 5 =====

[[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 defines the Phase 0 implementation [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]. It identifies selected implementation technologies, implementation artefacts, mappings, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures, generated types, [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] profiles, scripts, [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] organisation, Developer Handbook requirements, governance rules, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

Part 5 defines the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]], testability, operation, [[dido:99_annexes:annex-b-terms-and-definitions:o:observation|Observation]], and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] approach. It identifies how the implementation artefacts defined in Part 4 are deployed, started, exercised, observed, reviewed, and evidenced.

Part 4 does not define Deployment topology, runtime environment configuration, operational runbooks, test execution results, Evidence packages, dashboards, [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]] or [[dido:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]] Deployment, [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] scenarios, or acceptance Evidence. Part 5 owns those concerns.

Part 5 does not redefine the implementation artefacts defined in Part 4. It deploys, tests, observes, operates, and evidences those artefacts.