fxdemo:01-part:10-conceptual-traceability-model:10-5-implementation-artefact-psm-to-deployment-artefact

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
fxdemo:01-part:10-conceptual-traceability-model:10-5-implementation-artefact-psm-to-deployment-artefact [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1fxdemo:01-part:10-conceptual-traceability-model:10-5-implementation-artefact-psm-to-deployment-artefact [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== 10.5 Implementation Artifact / PSM to Deployment Artifact ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +An Implementation Artifact / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] traces to a Deployment Artifact when a deployment profile describes how the implementation runs in a concrete environment.
 +
 +For example, a container image may trace to a Kubernetes Deployment, Pod, or Helm chart. A DDS QoS profile may trace to a mounted configuration file or ConfigMap. A generated IDL binding may trace to a deployed service image using that binding.
 +
 +This relationship supports operational review. It allows a reviewer to identify which deployed artifact executed, configured, exposed, or controlled a given implementation artifact.
 +
 +Examples include:
 +
 +Table 10.5-1: Examples of implementation artifacts traced to deployment artifacts
 +
 +^ Implementation Artifact / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] ^ Deployment Artifact ^
 +| OCI-compatible container image | Kubernetes Deployment, Pod, K3s workload, or local container runtime configuration |
 +| DDS Topic configuration | DDS XML configuration, mounted configuration file, or runtime topic registration |
 +| USER_QOS_PROFILES.xml | ConfigMap, mounted file, deployment package, or runtime configuration volume |
 +| Python [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] implementation | Container entry point, process command, service manifest, or pod specification |
 +| Generated language binding | Built package, container layer, deployed runtime dependency, or generated source directory |
 +| Implementation configuration file | Environment-specific configuration file, ConfigMap, Secret, or mounted volume |
 +
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>
 +