P3-REQ-17-3-006

Return to Requirements

The FX Demo Logical Profile SHALL distinguish FX logical Nodes from processes, services, containers, pods, virtual machines, serverless functions, threads, tasks, libraries, subroutines, RPC endpoints, REST resources, DDS participants, and deployment artefacts.

Part 3, Section 17.3: FX Logical Node Requirements.

FX logical Nodes are architectural constructs that define logical responsibilities, interactions, governance, traceability, and evidence expectations within the Foreign Exchange Domain. They are intentionally independent of any implementation technology or deployment strategy.

Distinguishing logical Nodes from implementation artefacts preserves the platform-independent nature of the FX Demo Logical Profile and maintains the separation of concerns established by Parts 1 and 2. This separation enables multiple Implementation Profiles to realize the same logical architecture using different technologies while preserving architectural consistency, interoperability, governance, and traceability.

This requirement applies to the definition, review, maintenance, interpretation, and evolution of the FX Demo Logical Profile.

It applies specifically to:

• logical Node definitions;
• architectural modeling activities;
• logical architecture reviews;
• Implementation Profile development;
• deployment planning; and
• architectural conformance assessments.

Verification SHALL confirm that the FX Demo Logical Profile clearly distinguishes logical Nodes from implementation artefacts.

Verification activities should include review checks confirming that:

• logical Nodes are described as architectural constructs rather than implementation constructs;
• processes, services, containers, pods, virtual machines, serverless functions, threads, tasks, libraries, and subroutines are not identified as logical Nodes;
• RPC endpoints, REST resources, DDS participants, and other communication technologies are not defined as logical Nodes;
• deployment artefacts are not represented as logical Nodes; and
• the separation between logical architecture and implementation is consistently maintained throughout the FX Demo Logical Profile.

This requirement preserves the architectural separation between the platform-independent Logical Profile defined by Part 3 and the implementation-specific concerns addressed by subsequent Implementation Profiles and deployment models.

Related requirement identifiers:

• P3-REQ-17-3-001
• P3-REQ-17-3-003
• P3-REQ-17-3-005

Related source section:

• 17.3 FX Logical Node Requirements

Draft