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-01:p1-req-13-4-006:start [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-01:p1-req-13-4-006:start to dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-006:start nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-006:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== P1-REQ-13-4-006 ====== ====== P1-REQ-13-4-006 ======
  
-[[dido:99_annexes:annex-c-requirements:part-01:start|Return to Part 1 Requirements]]+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
  
 ===== Statement ===== ===== Statement =====
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] SHALL identify a point of information exchange used by one or more [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]s.+A [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] SHALL identify a point of information exchange used by one or more [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]]s.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-A Communication Endpoint identifies where information exchange occurs in the architecture. It separates the architectural point of exchange from the information exchanged through that point and from the implementation mechanism that realises exchange.+A Communication Endpoint identifies where information exchange occurs in the architecture. It separates the architectural point of exchange from the information exchanged through that point and from the implementation mechanism that realizes exchange.
  
-This requirement supports clear modelling of communication relationships among Nodes without tying conceptual exchange to a specific protocol, topic, queue, service, or interface technology.+This requirement supports clear modeling of communication relationships among Nodes without tying conceptual exchange to a specific protocol, topic, queue, service, or interface technology.
  
 ===== Applies To ===== ===== Applies To =====
Line 48: Line 48:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-4-001:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-001:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-4-005:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-005:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-4-011:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-4-013:start]]+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-013:start]]
  
 ===== Status ===== ===== Status =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-4-006/start.1783799862.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido