16.10 Profile and Implementation Boundary Requirements

Go To Top

1. A Domain Logical Profile SHALL preserve the Logical Architecture / PIM defined in this part.
2. A Domain Logical Profile SHALL specialise the Logical Architecture / PIM for a specific financial Domain.
3. A Domain Logical Profile SHALL identify the Part 2 logical elements it inherits unchanged.
4. A Domain Logical Profile SHALL identify the Part 2 logical elements it specialises.
5. A Domain Logical Profile SHALL NOT introduce implementation technologies, deployment artefacts, runtime scripts, product choices, or Evidence-capture procedures.
6. An Implementation Profile / PSM SHALL preserve the Logical Architecture / PIM defined in this part.
7. An Implementation Profile / PSM SHALL map logical elements to selected implementation artefacts without redefining the logical elements.
8. An Implementation Profile / PSM SHALL preserve Traceability from implementation artefacts to the logical elements they realise.
9. An Implementation Profile / PSM SHALL NOT use a technology selection to redefine a Logical Node, Logical Communication Endpoint, Logical Data Structure Definition, Logical Data Structure Instance, Logical Runtime Plane, Logical Interaction Pattern, Logical Governance relationship, or Logical Traceability relationship.
10. A Deployment, Testability, and Evidence Plan SHALL preserve Traceability to the Logical Architecture / PIM defined in this part.