| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:10-conceptual-traceability-model:10-4-logical-element-pim-to-implementation-artefact-psm [2026/06/30 17:06] – owen | fxdemo:01-part:10-conceptual-traceability-model:10-4-logical-element-pim-to-implementation-artefact-psm [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== 10.4 Logical Element / PIM to Implementation Artefact / PSM ====== | ====== 10.4 Logical Element / PIM to Implementation Artifact / PSM ====== |
| [[fxdemo:01-part:start | Go to Top ]] | [[fxdemo:01-part:start | Go to Top ]] |
| |
| A Logical Element / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] traces to an Implementation Artefact / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] when an implementation profile maps the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] to selected technologies. | A Logical Element / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] traces to an Implementation Artifact / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] when an implementation profile maps the [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] to selected technologies. |
| |
| For example, a logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] may map to a DDS Topic in a DDS-based implementation profile. A logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] may map to an IDL structure. A logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node|Node]] may map to a Python process packaged as an OCI-compatible container image. | For example, a logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] may map to a DDS Topic in a DDS-based implementation profile. A logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] may map to an IDL structure. A logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] may map to a Python process packaged as an OCI-compatible container image. |
| |
| This mapping realises the logical model for a selected implementation context. It does not redefine the logical element or the conceptual element behind it. | This mapping realizes the logical model for a selected implementation context. It does not redefine the logical element or the conceptual element behind it. |
| |
| Examples include: | Examples include: |
| |
| Table 10.4-1: Examples of logical elements traced to implementation artefacts | Table 10.4-1: Examples of logical elements traced to implementation artifacts |
| |
| ^ Logical Element / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] ^ Implementation Artefact / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] ^ | ^ Logical Element / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] ^ Implementation Artifact / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] ^ |
| | Logical Node | Python process, service process, or containerised executable | | | Logical Node | Python process, service process, or containerised executable | |
| | Logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] | DDS Topic, API endpoint, message queue, event stream, or file exchange point | | | Logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] | DDS Topic, API endpoint, message queue, event stream, or file exchange point | |
| | Logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] | IDL structure, JSON Schema, XML Schema, SysML block, or generated language type | | | Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] | IDL structure, JSON Schema, XML Schema, SysML block, or generated language type | |
| | Logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] | DDS topic namespace, DDS partition, topic family, or implementation grouping | | | Logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] | DDS topic namespace, DDS partition, topic family, or implementation grouping | |
| | Logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] class | Test output, captured message, provenance record, audit record, or configured evidence package | | | Logical [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] class | Test output, captured message, provenance record, audit record, or configured evidence package | |
| | Logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship | Trace matrix entry, metadata link, configuration reference, model relationship, or generated report | | | Logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship | Trace matrix entry, metadata link, configuration reference, model relationship, or generated report | |
| | |
| | |
| | ---- |
| | |
| | <WRAP centeralign> |
| | |
| | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| | |
| | </WRAP> |
| | |