16.7 Logical Interaction Requirements

Go To Logical Requirements

This section identifies the normative requirements established for the Logical Interaction Model. The canonical requirement statements are maintained in Annex C: Requirements, Part 2, Section 16.7.

Table 16-6: Logical Interaction requirements.

Requirement ID	Statement
P2-REQ-16-7-001	The Logical Architecture / PIM SHALL define reusable Logical Interaction Patterns.
P2-REQ-16-7-002	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.
P2-REQ-16-7-003	Each Logical Interaction Pattern SHALL identify participating Logical Nodes or Logical Node Roles.
P2-REQ-16-7-004	Each Logical Interaction Pattern SHALL identify the Logical Communication Endpoints involved.
P2-REQ-16-7-005	Each Logical Interaction Pattern SHALL identify the Logical Data Structure Instances exchanged, recorded, or referenced.
P2-REQ-16-7-006	Each Logical Interaction Pattern SHALL identify the Logical Runtime Plane(s) involved.
P2-REQ-16-7-007	Each Logical Interaction Pattern SHALL identify Traceability expectations.
P2-REQ-16-7-008	Each Logical Interaction Pattern SHALL identify Evidence expectations for later deployment, testability, and Evidence planning.
P2-REQ-16-7-009	Logical Interaction Patterns SHALL remain independent of DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, or deployment mechanisms.