Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== P2-REQ-16-10-004 ====== [[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]] ===== Statement ===== A Domain Logical Profile SHALL identify the Part 2 logical elements it specializes. ===== Source ===== Part 2, Section 16.10: Profile and Implementation Boundary Requirements. ===== Rationale ===== Explicit identification of specialized logical elements enables reviewers to distinguish new domain behavior from inherited architecture while preserving governance and traceability. ===== Applies To ===== This requirement applies to Domain Logical Profiles. It applies specifically to: * Specialized logical elements; * Domain Logical Profiles; and * Logical Architecture / PIM. ===== Verification ===== Verification SHALL confirm that specialized Part 2 logical elements are explicitly identified. Verification activities should include review checks confirming that: * specialized elements are documented; * specialisations preserve inherited meaning; * changes are justified; and * traceability is maintained. ===== Traceability ===== This requirement supports traceability between specialized logical elements and their inherited Part 2 definitions. 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-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> dido/99_annexes/annex-d-requirements/part-02/p2-req-16-10-004.txt Last modified: 2026/07/18 12:33by 127.0.0.1