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

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-008 [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-008 [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P2-REQ-16-5-008 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +A Logical Acknowledgement SHALL represent a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]] reporting receipt, acceptance, rejection, completion, failure, or outcome.
 +
 +===== Source =====
 +
 +Part 2, Section 16.5: Logical Information Requirements.
 +
 +===== Rationale =====
 +
 +Logical Acknowledgements communicate the outcome of previously initiated logical interactions. They provide a consistent, platform-independent means of reporting receipt and execution status while supporting accountability, operational coordination, and traceability.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Information Model.
 +
 +It applies specifically to:
 +
 +  * Logical Acknowledgements;
 +  * Logical Data Structure Instances;
 +  * Logical Interaction Patterns; and
 +  * Logical Control Plane interactions.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each Logical Acknowledgement represents a Logical Data Structure Instance reporting receipt, acceptance, rejection, completion, failure, or outcome.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * Logical Acknowledgements are explicitly identified;
 +  * acknowledgement outcomes are clearly defined;
 +  * Logical Acknowledgements remain platform independent; and
 +  * implementation technologies do not redefine Logical Acknowledgements.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Acknowledgements, the interactions they acknowledge, and the resulting operational outcomes.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-5-007]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-006]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-007]]
 +
 +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>