This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-8-boundary-between-part-2-and-implementation-profiles:start [2026/07/03 13:59] – owen | fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-8-boundary-between-part-2-and-implementation-profiles:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| Part 2 defines the platform-independent logical architecture. Implementation profiles define technology-specific realisations. | Part 2 defines the platform-independent logical architecture. Implementation profiles define technology-specific realisations. |
| |
| Part 2 identifies logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|information structures]], Runtime Planes, interaction patterns, governance relationships, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships. It does not bind those logical elements to implementation technologies or deployment mechanisms. | 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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. This boundary allows different implementation profiles to realise the same Logical Architecture / PIM using different technologies while preserving the same logical relationships. | 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. |
| |
| ---- | ---- |