dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-003

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-3-003 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-003 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-3-003 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +A [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]] SHALL uniquely distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] within the Logical Architecture / PIM.
 +
 +===== Source =====
 +
 +Part 2, Section 16.3: Logical Node Requirements.
 +
 +===== Rationale =====
 +
 +Logical Node Identity provides the basis for uniquely identifying Logical Nodes within the Logical Architecture / PIM. Unique identification supports communication, governance, traceability, compatibility assessment, operational review, and implementation mapping.
 +
 +Without unique identities, logical interactions and responsibilities could not be unambiguously attributed to individual Logical Nodes.
 +
 +===== Applies To =====
 +
 +This requirement applies to the definition, maintenance, interpretation, and use of Logical Node Identities.
 +
 +It applies specifically to:
 +
 +  * Logical Node identification;
 +  * Logical interaction modeling;
 +  * Governance relationships;
 +  * Traceability relationships; and
 +  * Implementation mappings.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each Logical Node can be uniquely distinguished by its Logical Node Identity.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * each Logical Node has a unique Logical Node Identity;
 +  * identities distinguish Logical Nodes within the Logical Architecture;
 +  * Logical Node Identities support traceability and governance; and
 +  * implementation mappings preserve Logical Node Identity.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Node Identity and the Logical Nodes identified within the Logical Architecture.
 +
 +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-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-004]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>