Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-3-009 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009 nick_dido
+++ dido: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-c-requirements:part-02:start| Return to Requirements]]
+[[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 artefact.
+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 =====
@@ Line 13: / Line 13: @@
 ===== Rationale =====
-Maintaining a clear distinction between Logical Nodes and implementation artefacts preserves platform independence and architectural stability. This separation allows different implementation approaches to realise the same Logical Node without altering its architectural meaning or responsibilities.
+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 =====
@@ Line 28: / Line 28: @@
 ===== Verification =====
-Verification SHALL confirm that Logical Nodes remain distinct from implementation and deployment artefacts.
+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 artefacts;
+  * Logical Nodes are not defined as implementation artifacts;
   * implementation mappings preserve Logical Node meaning;
-  * deployment artefacts do not redefine Logical Nodes; and
+  * 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 artefacts that realise them.
+This requirement supports traceability from platform-independent Logical Nodes to the implementation artifacts that realize them.
 Related requirement identifiers:
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-3-001]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001]]
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-3-002]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-002]]
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-2-005]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-005]]
 Related source section: