| Next revision | Previous revision |
| fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start [2026/07/03 14:27] – created owen | fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== 16.3 Logical Node Requirements ====== | ====== 16.3 Logical Node Requirements ====== |
| [[fxdemo:02-part:start | Go To Top ]] | [[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]] |
| |
| - The Logical Architecture / PIM SHALL define [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], [[fxdemo:99_part_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. | This section identifies the normative requirements established for the Logical Node Model. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.3]]. |
| - A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] SHALL represent a platform-independent participant in the distributed logical architecture. | |
| - A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]] SHALL uniquely distinguish a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] within the Logical Architecture / PIM. | <WRAP table-caption> |
| - A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Role]] SHALL identify a platform-independent responsibility assigned to or performed by a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]]. | **Table 16-2:** Logical Node requirements. |
| - A Logical Node Responsibility SHALL describe an obligation, function, or accountability associated with a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Role]]. | </WRAP> |
| - A Logical Node Boundary SHALL identify what the logical architecture treats as inside or outside a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] for responsibility, interaction, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], and review. | |
| - Logical Node Collaboration SHALL identify explicit logical cooperation among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] through [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]] and interaction patterns. | ^ Requirement ID ^ Statement ^ |
| - Logical Node Lifecycle State SHALL identify the logical operational condition associated with a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]]. | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001|P2-REQ-16-3-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001#statement&noheader&nofooter}} | |
| - The Logical Architecture / PIM SHALL distinguish a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] from a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, RPC endpoint, REST resource, DDS participant, and deployment artefact. | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-002|P2-REQ-16-3-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-002#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-003|P2-REQ-16-3-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-003#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-004|P2-REQ-16-3-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-004#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-005|P2-REQ-16-3-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-005#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-006|P2-REQ-16-3-006]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-006#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-007|P2-REQ-16-3-007]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-007#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-008|P2-REQ-16-3-008]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-008#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009|P2-REQ-16-3-009]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-009#statement&noheader&nofooter}} | |
| |
| ---- | ---- |