16.3 Logical Node Requirements

Go To Logical Requirements

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

Table 16-2: Logical Node requirements.

Requirement ID	Statement
P2-REQ-16-3-001	The Logical Architecture / PIM SHALL define Logical Node, Logical Node Identity, Logical Node Role, Logical Node Responsibility, Logical Node Boundary, Logical Node Collaboration, and Logical Node Lifecycle State.
P2-REQ-16-3-002	A Logical Node SHALL represent a platform-independent participant in the distributed logical architecture.
P2-REQ-16-3-003	A Logical Node Identity SHALL uniquely distinguish a Logical Node within the Logical Architecture / PIM.
P2-REQ-16-3-004	A Logical Node Role SHALL identify a platform-independent responsibility assigned to or performed by a Logical Node.
P2-REQ-16-3-005	A Logical Node Responsibility SHALL describe an obligation, function, or accountability associated with a Logical Node or Logical Node Role.
P2-REQ-16-3-006	A Logical Node Boundary SHALL identify what the logical architecture treats as inside or outside a Logical Node for responsibility, interaction, Traceability, and review.
P2-REQ-16-3-007	Logical Node Collaboration SHALL identify explicit logical cooperation among Logical Nodes through Communication Endpoints and interaction patterns.
P2-REQ-16-3-008	Logical Node Lifecycle State SHALL identify the logical operational condition associated with a Logical Node.
P2-REQ-16-3-009	The Logical Architecture / PIM SHALL distinguish a Logical Node from a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, RPC endpoint, REST resource, DDS participant, and deployment artifact.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.