====== P2-REQ-16-10-002 ======

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

===== Statement =====

A Domain Logical Profile SHALL specialize the Logical Architecture / PIM for a specific financial Domain.

===== Source =====

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

===== Rationale =====

Domain Logical Profiles exist to refine the common Logical Architecture for a particular financial domain. Specialization adds domain-specific behavior and definitions while preserving the architectural meaning inherited from Part 2.

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

This requirement applies to Domain Logical Profiles.

It applies specifically to:

  * Domain Logical Profiles;
  * Financial Domains; and
  * Logical Architecture / PIM.

===== Verification =====

Verification SHALL confirm that Domain Logical Profiles specialize the Logical Architecture for their intended financial domain.

Verification activities should include review checks confirming that:

  * domain-specific specialisations are identified;
  * inherited logical meaning is preserved;
  * domain additions remain consistent with Part 2; and
  * specialisations are traceable.

===== Traceability =====

This requirement supports traceability between the Logical Architecture and its domain-specific specialisations.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-003]]

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>