dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-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-7-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-7-002 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-7-002 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define the following Logical Interaction Patterns:
 +
 +  * Register Node;
 +  * Report Node Status;
 +  * Publish Domain Information;
 +  * Subscribe to Domain Information;
 +  * Issue Control Command;
 +  * Acknowledge Control Command;
 +  * Request Policy Decision;
 +  * Record Audit and Provenance; and
 +  * Replay or Reconstruct Information.
 +
 +===== Source =====
 +
 +Part 2, Section 16.7: Logical Interaction Requirements.
 +
 +===== Rationale =====
 +
 +These Logical Interaction Patterns establish the minimum set of reusable interactions required to support coordination, information exchange, governance, auditability, and operational continuity within the Logical Architecture. They provide a consistent architectural vocabulary that Domain Logical Profiles may specialize while preserving common architectural meaning.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Interaction Model.
 +
 +It applies specifically to:
 +
 +  * Logical Interaction Patterns;
 +  * Logical Nodes;
 +  * Domain Logical Profiles; and
 +  * Implementation Profiles.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each required Logical Interaction Pattern is explicitly defined.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * all required Logical Interaction Patterns are present;
 +  * each pattern has a distinct architectural purpose;
 +  * the patterns remain platform independent; and
 +  * Domain Logical Profiles preserve the inherited interaction patterns.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between the Logical Interaction Model and the standard interaction patterns defined by the Logical Architecture.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-003]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-7-logical-interaction-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>