====== 14.6 Implementation Mapping Boundaries ======
[[fxdemo:02-part:start | Go To Top ]]

Implementation mappings connect logical elements to implementation artifacts. They do not change the logical elements that they realize.

An Implementation Profile / PSM identifies:
  * The logical element that the implementation artifact realizes
  * The selected implementation artifact
  * The mapping rationale
  * The communication, data representation, execution, or packaging mechanism involved
  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|Compatibility]] expectations
  * Governance constraints
  * The [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship to the logical model
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]], Logical Runtime Plane, or [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|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.

----

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