dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-002

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-002 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-002 [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P2-REQ-16-5-002 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define logical information categories, including [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_message|Logical Message]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_event|Logical Event]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_command|Logical Command]], Logical Acknowledgement, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_assertion|Logical Assertion]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_record|Logical Record]], and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_information_lineage|Logical Information Lineage]].
 +
 +===== Source =====
 +
 +Part 2, Section 16.5: Logical Information Requirements.
 +
 +===== Rationale =====
 +
 +Logical information categories classify information according to its architectural purpose rather than its implementation representation. Establishing these categories provides a consistent vocabulary for communication, governance, traceability, auditability, and later implementation mapping across all Domain Logical Profiles.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Information Model.
 +
 +It applies specifically to:
 +
 +  * Logical Messages;
 +  * Logical Events;
 +  * Logical Commands;
 +  * Logical Acknowledgements;
 +  * Logical Assertions;
 +  * Logical Records; and
 +  * Logical Information Lineage.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Information Model defines each required logical information category.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * each logical information category is explicitly defined;
 +  * each category has a distinct architectural purpose;
 +  * categories remain platform independent; and
 +  * Domain Logical Profiles preserve the inherited information categories.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Data Structure Instances and their architectural information categories.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-005]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-011]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-5-logical-information-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>