dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-004

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-2-004 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-2-004 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-004 nick_didodido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-004 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P2-REQ-16-2-004 ====== ====== P2-REQ-16-2-004 ======
  
-[[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 ===== ===== Statement =====
  
-The Logical Architecture / PIM SHALL distinguish [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] from runtime deployments, implementation artefacts, deployment artefacts, execution mechanisms, and communication technologies.+The Logical Architecture / PIM SHALL distinguish [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] from runtime deployments, implementation artifacts, deployment artifacts, execution mechanisms, and communication technologies.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-The Logical Architecture is platform independent. Separating Logical Nodes from implementation and deployment concepts preserves architectural meaning while allowing multiple implementation approaches to realise the same logical participant.+The Logical Architecture is platform independent. Separating Logical Nodes from implementation and deployment concepts preserves architectural meaning while allowing multiple implementation approaches to realize the same logical participant.
  
 ===== Applies To ===== ===== Applies To =====
Line 32: Line 32:
 Verification activities should include review checks confirming that: Verification activities should include review checks confirming that:
  
-  * Logical Nodes are not defined as runtime artefacts;+  * Logical Nodes are not defined as runtime artifacts;
   * implementation technologies do not redefine Logical Nodes;   * implementation technologies do not redefine Logical Nodes;
   * deployment mechanisms do not redefine Logical Nodes; and   * deployment mechanisms do not redefine Logical Nodes; and
Line 39: Line 39:
 ===== Traceability ===== ===== Traceability =====
  
-This requirement supports traceability between Logical Nodes and the implementation artefacts that realise them.+This requirement supports traceability between Logical Nodes and the implementation artifacts that realize them.
  
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-2-001]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-001]] 
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-2-002]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-002]] 
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-2-003]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-2-003]] 
-  * [[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: Related source section:
  • dido/99_annexes/annex-d-requirements/part-02/p2-req-16-2-004.1783799866.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido