dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009

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-3-009 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-3-009 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|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.
 +
 +===== Source =====
 +
 +Part 2, Section 16.3: Logical Node Requirements.
 +
 +===== Rationale =====
 +
 +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.
 +
 +===== Applies To =====
 +
 +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 =====
 +
 +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.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from platform-independent Logical Nodes to the implementation artifacts that realize them.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-005]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>