This is an old revision of the document!
16.10 Profile and Implementation Boundary Requirements
This section identifies the normative requirements established for Domain Logical Profiles, Implementation Profiles, and the boundary between the Logical Architecture / PIM and later architectural artefacts. The canonical requirement statements are maintained in Annex C: Requirements, Part 2, Section 16.10.
Table 16-9: Profile and implementation boundary requirements.
| Requirement ID | Statement |
|---|---|
| P2-REQ-16-10-001 |
A Domain Logical Profile SHALL preserve the Logical Architecture / PIM defined in this part. |
| P2-REQ-16-10-002 |
A Domain Logical Profile SHALL specialize the Logical Architecture / PIM for a specific financial Domain. |
| P2-REQ-16-10-003 |
A Domain Logical Profile SHALL identify the Part 2 logical elements it inherits unchanged. |
| P2-REQ-16-10-004 |
A Domain Logical Profile SHALL identify the Part 2 logical elements it specializes. |
| P2-REQ-16-10-005 |
A Domain Logical Profile SHALL NOT introduce implementation technologies, deployment artifacts, runtime scripts, product choices, or Evidence-capture procedures. |
| P2-REQ-16-10-006 |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.