dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_boundary

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-b-terms-and-definitions:l:logical_node_boundary [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_node_boundary to dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_boundary nick_didodido:99_annexes:annex-b-terms-and-definitions:l:logical_node_boundary [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Logical Node Boundary ====== ====== Logical Node Boundary ======
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]+[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
  
 ===== Discussion ===== ===== Discussion =====
Line 7: Line 7:
 Logical Node Boundary identifies what the Logical Architecture treats as inside or outside a Logical Node for purposes of responsibility, interaction, traceability, and review. Logical Node Boundary identifies what the Logical Architecture treats as inside or outside a Logical Node for purposes of responsibility, interaction, traceability, and review.
  
-A Logical Node Boundary separates the Logical Node from other Logical Nodes, external participants, Communication Endpoints, and implementation artefacts. It helps reviewers understand which responsibilities belong to the Logical Node and which interactions cross the Node boundary.+A Logical Node Boundary separates the Logical Node from other Logical Nodes, external participants, Communication Endpoints, and implementation artifacts. It helps reviewers understand which responsibilities belong to the Logical Node and which interactions cross the Node boundary.
  
-Logical Node Boundary does not imply a process, network, security, container, machine, or organisational boundary. Implementation and deployment profiles align those boundaries when alignment supports the selected realisation. They may also realise several Logical Nodes within a single runtime artefact, or realise a single Logical Node across multiple runtime artefacts, when the implementation or deployment design requires that structure.+Logical Node Boundary does not imply a process, network, security, container, machine, or organizational boundary. Implementation and deployment profiles align those boundaries when alignment supports the selected realization. They may also realize several Logical Nodes within a single runtime artifact, or realize a single Logical Node across multiple runtime artifacts, when the implementation or deployment design requires that structure.
  
 ===== Definition ===== ===== Definition =====
Line 17: Line 17:
 ===== Source ===== ===== Source =====
  
-Specialisation of Node, Communication Endpoint, and Traceability from Part 1, Sections 7.2, 7.6, and 7.10; informed by the distributed node material in the original FX Demo Reference Architecture.+Specialization of Node, Communication Endpoint, and Traceability from Part 1, Sections 7.2, 7.6, and 7.10; informed by the distributed node material in the original FX Demo Reference Architecture.
  
 ===== Note ===== ===== Note =====
Line 29: Line 29:
 ---- ----
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]+[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]
  • dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_boundary.1783793678.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido