dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start

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-002:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-The Conceptual Architecture SHALL distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] as an architectural participant in a distributed [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]].+The Conceptual Architecture SHALL distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] as an architectural participant in a distributed [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]].
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-A Node represents an architectural participant in a distributed Financial System. Distinguishing a Node at the conceptual level prevents confusion between an architectural participant and implementation-specific artefacts such as processes, containers, services, executables, or deployment units.+A Node represents an architectural participant in a distributed Financial System. Distinguishing a Node at the conceptual level prevents confusion between an architectural participant and implementation-specific artifacts such as processes, containers, services, executables, or deployment units.
  
 This requirement preserves the conceptual role of a Node across logical, implementation, and deployment refinement. This requirement preserves the conceptual role of a Node across logical, implementation, and deployment refinement.
Line 38: Line 38:
   * Node references do not depend on implementation technology   * Node references do not depend on implementation technology
   * Node references do not substitute for containers, processes, or services   * Node references do not substitute for containers, processes, or services
-  * Later profiles map implementation artefacts to Nodes without redefining Node meaning+  * Later profiles map implementation artifacts to Nodes without redefining Node meaning
  
 ===== Traceability ===== ===== Traceability =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-4-002/start.1783799875.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido