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

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-001 [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-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-3-001 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Role]], Logical Node Responsibility, Logical Node Boundary, Logical Node Collaboration, and Logical Node Lifecycle State.
 +
 +===== Source =====
 +
 +Part 2, Section 16.3: Logical Node Requirements.
 +
 +===== Rationale =====
 +
 +The Logical Node Model provides the primary organizational structure for the Logical Architecture / PIM. Defining the Logical Node and its associated concepts establishes a consistent foundation for assigning responsibilities, identifying participants, modeling collaboration, and supporting governance and traceability throughout the logical architecture.
 +
 +Without these concepts, different Domain Logical Profiles and Implementation Profiles could interpret logical participants inconsistently, reducing interoperability, reviewability, and architectural consistency.
 +
 +===== Applies To =====
 +
 +This requirement applies to the definition, review, maintenance, interpretation, and specialization of the Logical Node Model.
 +
 +It applies specifically to:
 +
 +  * Logical Nodes;
 +  * Logical Node Identities;
 +  * Logical Node Roles;
 +  * Logical Node Responsibilities;
 +  * Logical Node Boundaries;
 +  * Logical Node Collaboration; and
 +  * Logical Node Lifecycle States.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Architecture / PIM defines each required Logical Node concept.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * each Logical Node concept is explicitly defined;
 +  * the definitions are consistent with the Part 1 Conceptual Architecture;
 +  * the concepts collectively support logical modeling and governance; and
 +  * the Logical Node Model provides a complete basis for later Domain Logical Profiles and Implementation Profiles.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from the Part 1 conceptual Node to the Logical Node Model defined by Part 2.
 +
 +Related requirement identifiers:
 +
 +  * [[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-003]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-004]]
 +  * [[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-006]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-007]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-008]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009]]
 +
 +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>