| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-6-implementation-mapping-boundaries:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido | fxdemo:02-part:14-relationship-to-implementation-profiles-psm:14-6-implementation-mapping-boundaries:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:02-part:start | Go To Top ]] | [[fxdemo:02-part:start | Go To Top ]] |
| |
| Implementation mappings connect logical elements to implementation artefacts. They do not change the logical elements that they realise. | Implementation mappings connect logical elements to implementation artifacts. They do not change the logical elements that they realize. |
| |
| An Implementation Profile / PSM identifies: | An Implementation Profile / PSM identifies: |
| * The logical element that the implementation artefact realises | * The logical element that the implementation artifact realizes |
| * The selected implementation artefact | * The selected implementation artifact |
| * The mapping rationale | * The mapping rationale |
| * The communication, data representation, execution, or packaging mechanism involved | * The communication, data representation, execution, or packaging mechanism involved |
| * [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|Compatibility]] expectations | * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|Compatibility]] expectations |
| * Governance constraints | * Governance constraints |
| * The [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship to the logical model | * The [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship to the logical model |
| * [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations that later deployment and testability plans satisfy | * [[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 [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]], Logical Runtime Plane, or [[fxdemo: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. | 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. |
| |
| ---- | ---- |