fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-8-boundary-between-part-2-and-implementation-profiles:start

Differences

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

Link to this comparison view

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] – created owenfxdemo: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
Line 1: Line 1:
-14.8 Boundary Between Part 2 and Implementation Profiles+====== 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 defines the platform-independent logical architecture. Implementation profiles define technology-specific realisations.
-Part 2 identifies logical Nodes, endpoints, information structures, Runtime Planes, interaction patterns, governance relationships, and 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 traceability. This boundary allows different implementation profiles to realise the same Logical Architecture/PIM using different technologies while preserving the same logical relationships. 
  
 +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>
  • fxdemo/02-part/14-relationship-to-implementation-profiles-psm/14-8-boundary-between-part-2-and-implementation-profiles/start.1783112378.txt.gz
  • Last modified: 2026/07/03 13:59
  • by owen