fxdemo:02-part:16-logical-requirements:16-10-profile-and-implementation-boundary-requirements:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
fxdemo:02-part:16-logical-requirements:16-10-profile-and-implementation-boundary-requirements:start [2026/07/03 14:40] – created owenfxdemo:02-part:16-logical-requirements:16-10-profile-and-implementation-boundary-requirements:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== 16.10 Profile and Implementation Boundary Requirements ====== ====== 16.10 Profile and Implementation Boundary Requirements ======
-[[fxdemo:02-part:start | Go To Top ]]+[[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]]
  
-  - A Domain Logical Profile SHALL preserve the Logical Architecture / PIM defined in this part. +This section identifies the normative requirements established for Domain Logical Profiles, Implementation Profiles, and the boundary between the Logical Architecture / PIM and later architectural artifactsThe canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.10]]
-  - A Domain Logical Profile SHALL specialise the Logical Architecture / PIM for a specific financial Domain. + 
-  A Domain Logical Profile SHALL identify the Part 2 logical elements it inherits unchanged+<WRAP table-caption> 
-  A Domain Logical Profile SHALL identify the Part 2 logical elements it specialises. +**Table 16-9:** Profile and implementation boundary requirements. 
-  A Domain Logical Profile SHALL NOT introduce implementation technologies, deployment artefacts, runtime scripts, product choices, or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]-capture procedures. +</WRAP> 
-  An Implementation Profile / PSM SHALL preserve the Logical Architecture / PIM defined in this part+ 
-  An Implementation Profile / PSM SHALL map logical elements to selected implementation artefacts without redefining the logical elements.  +^ Requirement ID ^ Statement ^ 
-  An Implementation Profile / PSM SHALL preserve [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from implementation artefacts to the logical elements they realise. +[[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001|P2-REQ-16-10-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001#statement&noheader&nofooter}} | 
-  An Implementation Profile / PSM SHALL NOT use a technology selection to redefine a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definition]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]], Logical Runtime Plane, Logical Interaction Pattern, Logical Governance relationship, or Logical Traceability relationship. +[[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-002|P2-REQ-16-10-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-002#statement&noheader&nofooter}} | 
-  - A Deployment, Testability, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] Plan SHALL preserve [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the Logical Architecture / PIM defined in this part.+[[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-003|P2-REQ-16-10-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-003#statement&noheader&nofooter}} | 
 +| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-004|P2-REQ-16-10-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-004#statement&noheader&nofooter}} 
 +[[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-005|P2-REQ-16-10-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-005#statement&noheader&nofooter}} | 
 +| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-006|P2-REQ-16-10-006]] | {{section>fxdemo:99_part_annexes:annex-c-requirements:part-02:p2-req-16-10-006#statement&noheader
  
  
Line 17: Line 20:
  
 <WRAP centeralign> <WRAP centeralign>
 +
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 </WRAP> </WRAP>
 +
  • fxdemo/02-part/16-logical-requirements/16-10-profile-and-implementation-boundary-requirements/start.1783114816.txt.gz
  • Last modified: 2026/07/03 14:40
  • by owen