====== P2-REQ-16-10-001 ======

[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]

===== Statement =====

A Domain Logical Profile SHALL preserve the Logical Architecture / PIM defined in this part.

===== Source =====

Part 2, Section 16.10: Profile and Implementation Boundary Requirements.

===== Rationale =====

A Domain Logical Profile extends the Logical Architecture for a specific financial domain while preserving the architectural meaning established by Part 2. Preserving the inherited Logical Architecture ensures consistency, interoperability, governance, and traceability across all domain specialisations.

===== Applies To =====

This requirement applies to Domain Logical Profiles.

It applies specifically to:

  * Domain Logical Profiles;
  * Logical Architecture / PIM; and
  * Domain specialisations.

===== Verification =====

Verification SHALL confirm that every Domain Logical Profile preserves the Logical Architecture / PIM defined in Part 2.

Verification activities should include review checks confirming that:

  * inherited logical elements remain unchanged unless explicitly specialized;
  * architectural meaning is preserved;
  * governance relationships remain valid; and
  * traceability to Part 2 is maintained.

===== Traceability =====

This requirement supports traceability between the Logical Architecture / PIM and Domain Logical Profiles.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-002]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-012]]

Related source section:

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

===== Status =====

Draft

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>