14.8 Boundary Between Part 2 and Implementation Profiles [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 14.8 Boundary Between Part 2 and Implementation Profiles ======
[[fxdemo:02-part:start | Go To Top ]]

Part 2 defines the platform-independent logical architecture. Implementation profiles define technology-specific realisations.

Part 2 identifies logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|information structures]], Runtime Planes, interaction patterns, governance relationships, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships. It does not bind those logical elements to implementation technologies or deployment mechanisms.

An Implementation Profile / PSM provides the technology-specific mapping while preserving logical meaning and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. This boundary allows different implementation profiles to realize the same Logical Architecture / PIM using different technologies while preserving the same logical relationships.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>