====== P2-REQ-16-3-006 ====== [[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]] ===== Statement ===== A Logical Node Boundary SHALL identify what the logical architecture treats as inside or outside a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] for responsibility, interaction, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], and review. ===== Source ===== Part 2, Section 16.3: Logical Node Requirements. ===== Rationale ===== Logical Node Boundaries define the scope of a Logical Node and distinguish internal responsibilities from external interactions. Clear boundaries support architectural review, governance, traceability, implementation mapping, and evolution of the logical architecture. ===== Applies To ===== This requirement applies to Logical Node definitions and Logical Node modeling. It applies specifically to: * Logical Node Boundaries; * Responsibility allocation; * Logical interactions; and * Architectural review. ===== Verification ===== Verification SHALL confirm that each Logical Node Boundary clearly identifies what is considered inside and outside the Logical Node. Verification activities should include review checks confirming that: * Logical Node Boundaries are explicitly identified; * responsibilities are consistently allocated across boundaries; * logical interactions cross defined boundaries; and * boundaries support traceability and review. ===== Traceability ===== This requirement supports traceability between Logical Node Boundaries, Logical Nodes, and Logical Interactions. Related requirement identifiers: * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001]] * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-005]] * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-007]] Related source section: * [[fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start]] ===== Status ===== Draft ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.