17.12 Implementation Boundary Requirements
Go To FX Demo Logical Requirements
This section identifies the normative requirements governing the architectural boundary between the FX Demo Logical Profile, subsequent Implementation Profiles, and Deployment, Testability, and Evidence Plans. The canonical requirement statements are maintained in Annex D: Requirements, Part 3, Section 17.12.
Table 17-11: Implementation boundary requirements.
| Requirement ID | Statement |
|---|---|
| P3-REQ-17-12-001 |
The FX Demo Logical Profile SHALL remain platform-independent. |
| P3-REQ-17-12-002 |
An Implementation Profile / PSM SHALL preserve the FX Demo Logical Profile defined in this part. |
| P3-REQ-17-12-003 |
An Implementation Profile / PSM SHALL map FX logical elements to selected implementation artefacts without redefining them. |
| P3-REQ-17-12-004 |
An Implementation Profile / PSM SHALL preserve traceability from implementation artefacts to the FX logical elements they realise. |
| P3-REQ-17-12-005 |
An Implementation Profile / PSM SHALL NOT use a technology selection to redefine an FX logical Node, FX logical Node Role, FX logical Communication Endpoint, FX logical information structure, FX Runtime Plane, FX logical interaction pattern, FX logical governance relationship, or FX logical traceability relationship. |
| P3-REQ-17-12-006 |
A Deployment, Testability, and Evidence Plan SHALL preserve traceability to the FX Demo Logical Profile defined in this part. |
| P3-REQ-17-12-007 |
A Deployment, Testability, and Evidence Plan SHALL NOT redefine FX logical elements through deployment topology, runtime packaging, test tooling, monitoring tooling, evidence-capture tooling, repository structure, or runtime scripts. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.