| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:10-conceptual-traceability-model:10-3-conceptual-element-to-logical-element-pim [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1 | fxdemo:01-part:10-conceptual-traceability-model:10-3-conceptual-element-to-logical-element-pim [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| | ====== 10.3 Conceptual Element to Logical Element / PIM ====== |
| | [[fxdemo:01-part:start | Go to Top ]] |
| | |
| | A Conceptual Element traces to a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Element / Platform Independent Model (PIM)]] when the logical architecture specializes the concept without binding it to a specific implementation technology. |
| | |
| | For example, the concept [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] may trace to a logical endpoint used for health reporting, work dispatch, transaction publication, validation results, policy decisions, or audit records. The logical endpoint remains [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent]]. It does not yet require DDS, REST, files, message queues, or another specific mechanism. |
| | |
| | This [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship helps reviewers confirm that the logical architecture preserves the conceptual meaning of the element it specializes. |
| | |
| | Examples include: |
| | |
| | Table 10.3-1: Examples of conceptual elements traced to logical elements |
| | |
| | ^ Conceptual Element ^ Logical Element / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] ^ |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] | Logical Node | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]] | Logical responsibility assigned to a Logical Node | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] | Logical endpoint or interaction point | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] | Logical information structure | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] | Logical message, record, event, assertion, or command instance | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] | Logical plane classification | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | Logical evidence claim or evidence class | |
| | | [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | Logical trace relationship | |
| | |
| | ---- |
| | |
| | <WRAP centeralign> |
| | |
| | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| | |
| | </WRAP> |
| |