This is an old revision of the document!
16.3 Logical Node Requirements
-
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.
-
A Logical Node SHALL represent a platform-independent participant in the distributed logical architecture.
-
A Logical Node Identity SHALL uniquely distinguish a Logical Node within the Logical Architecture / PIM.
-
A Logical Node Role SHALL identify a platform-independent responsibility assigned to or performed by a Logical Node.
-
A Logical Node Responsibility SHALL describe an obligation, function, or accountability associated with a Logical Node or Logical Node Role.
-
A Logical Node Boundary SHALL identify what the logical architecture treats as inside or outside a Logical Node for responsibility, interaction, Traceability, and review.
-
Logical Node Collaboration SHALL identify explicit logical cooperation among Logical Nodes through Communication Endpoints and interaction patterns.
-
Logical Node Lifecycle State SHALL identify the logical operational condition associated with a Logical Node.
-
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 artefact.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.