14.6 Implementation Mapping Boundaries

Go To Top

Implementation mappings connect logical elements to implementation artefacts. They do not change the logical elements that they realise.

An Implementation Profile / PSM identifies:

• The logical element that the implementation artefact realises
• The selected implementation artefact
• The mapping rationale
• The communication, data representation, execution, or packaging mechanism involved
• Compatibility expectations
• Governance constraints
• The Traceability relationship to the logical model
• Evidence expectations that later deployment and testability plans satisfy

Implementation mappings remain bounded by the Logical Architecture / PIM. A technology selection does not create a new Logical Node, Logical Communication Endpoint, Logical Runtime Plane, or Logical Data Structure Definition unless the implementation profile explicitly identifies a required logical change and traces that change back to the appropriate logical and conceptual source.