Differences

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

--- fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-6-logical-architecture-provides-the-basis-for-implementation-profiles [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1
+++ fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-6-logical-architecture-provides-the-basis-for-implementation-profiles [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== 12.6 Logical Architecture Provides the Basis for Implementation Profiles ======
+[[fxdemo:01-part:start | Go to Top ]]
+Implementation profiles use the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] as their source for technology mapping.
+For example, a later implementation profile may map:
+  * Logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] to a DDS Topic
+  * Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] to an IDL structure
+  * Logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] to a Python process or service
+  * Logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] to a topic namespace, partition, or configuration grouping
+  * Logical [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] class to a test output, captured message, audit record, or evidence package
+Those implementation mappings realize the logical architecture for a selected technology stack. They do not redefine the logical elements or the conceptual elements behind them.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>