dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006

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-4-006 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-006 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006 nick_didodido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P2-REQ-16-4-006 ====== ====== P2-REQ-16-4-006 ======
  
-[[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_communication_endpoint|Logical Communication Endpoints]] from DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, files, database handoffs, shared-memory locations, network routes, and deployment artefacts.+The Logical Architecture / PIM SHALL distinguish [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]] from DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, files, database handoffs, shared-memory locations, network routes, and deployment artifacts.
  
 ===== Source ===== ===== Source =====
Line 23: Line 23:
   * Logical Communication Endpoints;   * Logical Communication Endpoints;
   * Communication technology mappings;   * Communication technology mappings;
-  * Implementation artefacts; and +  * Implementation artifacts; and 
-  * Deployment artefacts.+  * Deployment artifacts.
  
 ===== Verification ===== ===== Verification =====
Line 35: Line 35:
   * communication technology selections are deferred to Implementation Profiles;   * communication technology selections are deferred to Implementation Profiles;
   * implementation mappings preserve the meaning of Logical Communication Endpoints; and   * implementation mappings preserve the meaning of Logical Communication Endpoints; and
-  * deployment artefacts do not redefine Logical Communication Endpoints.+  * deployment artifacts do not redefine Logical Communication Endpoints.
  
 ===== Traceability ===== ===== Traceability =====
  
-This requirement supports traceability between Logical Communication Endpoints and the implementation artefacts that realise them.+This requirement supports traceability between Logical Communication Endpoints and the implementation artifacts that realize them.
  
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-005]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005]] 
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-007]]+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007]]
   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-007]]   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-007]]
  
  • dido/99_annexes/annex-d-requirements/part-02/p2-req-16-4-006.1783799867.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido