====== 19.3 Implementation Artefacts Prepared for Deployment ======

[[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:d:deployment|Deployment]] by identifying their purpose, location, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] needs, runtime role, [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

Implementation artefacts prepared for Deployment include:

  - Implementation [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] modules
  - Process entry points
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic mappings
  - [[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
  - Configuration artefacts
  - Scripts
  - [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] artefacts
  - Traceability artefacts

Part 5 uses those artefacts to define the Phase 0 Deployment approach. It identifies how the selected environment packages, starts, connects, monitors, and manages the implementation participants.

Part 4 therefore provides the Deployment input, while Part 5 defines the Deployment use.

<WRAP centeralign>

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

</WRAP>