P2-REQ-16-3-009

Return to Requirements

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.

Part 2, Section 16.3: Logical Node Requirements.

Maintaining a clear distinction between Logical Nodes and implementation artifacts preserves platform independence and architectural stability. This separation allows different implementation approaches to realize the same Logical Node without altering its architectural meaning or responsibilities.

This requirement applies to the Logical Architecture / PIM and all Implementation Profiles derived from it.

It applies specifically to:

• Logical Nodes;
• Implementation mappings;
• Deployment mappings; and
• Technology-specific realisations.

Verification SHALL confirm that Logical Nodes remain distinct from implementation and deployment artifacts.

Verification activities should include review checks confirming that:

• Logical Nodes are not defined as implementation artifacts;
• implementation mappings preserve Logical Node meaning;
• deployment artifacts do not redefine Logical Nodes; and
• platform independence is maintained throughout the Logical Architecture.

This requirement supports traceability from platform-independent Logical Nodes to the implementation artifacts that realize them.

Related requirement identifiers:

• P2-REQ-16-3-001
• P2-REQ-16-3-002
• P2-REQ-16-2-005

Related source section:

• 16.3 Logical Node Requirements

Draft