dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start

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-01:p1-req-13-4-002:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-4-002 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] as an architectural participant in a distributed [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]].
 +
 +===== Source =====
 +
 +Part 1, Section 13.4: Core Conceptual Element Requirements.
 +
 +===== Rationale =====
 +
 +A Node represents an architectural participant in a distributed Financial System. Distinguishing a Node at the conceptual level prevents confusion between an architectural participant and implementation-specific artifacts such as processes, containers, services, executables, or deployment units.
 +
 +This requirement preserves the conceptual role of a Node across logical, implementation, and deployment refinement.
 +
 +===== Applies To =====
 +
 +This requirement applies to all references to Nodes within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Architectural participants
 +  * Distributed Financial System participants
 +  * Node definitions
 +  * Node descriptions
 +  * Node-related conceptual diagrams
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture distinguishes a Node as an architectural participant in a distributed Financial System.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Node references identify architectural participants
 +  * Node references do not depend on implementation technology
 +  * Node references do not substitute for containers, processes, or services
 +  * Later profiles map implementation artifacts to Nodes without redefining Node meaning
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-4-core-conceptual-element-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-003:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-004:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>