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

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-006 [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-006 [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P2-REQ-16-5-006 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +A [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_event|Logical Event]] SHALL represent a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]] reporting an occurrence, observation, state change, decision, or result.
 +
 +===== Source =====
 +
 +Part 2, Section 16.5: Logical Information Requirements.
 +
 +===== Rationale =====
 +
 +Logical Events communicate that something has occurred within the architecture. They provide a consistent, platform-independent representation of observations, state changes, decisions, and results while remaining independent of event-processing technologies and messaging infrastructures.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Information Model.
 +
 +It applies specifically to:
 +
 +  * Logical Events;
 +  * Logical Data Structure Instances;
 +  * Logical Interaction Patterns; and
 +  * Domain Logical Profiles.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each Logical Event represents a Logical Data Structure Instance reporting an occurrence, observation, state change, decision, or result.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * Logical Events are explicitly identified;
 +  * each event reports a defined occurrence or result;
 +  * Logical Events remain platform independent; and
 +  * implementation technologies do not redefine Logical Events.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Events, the occurrences they report, and the Logical Interaction Patterns that exchange them.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-005]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-003]]
 +
 +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>