dido:99_annexes:annex-d-requirements:part-03:p3-req-17-3-005

This is an old revision of the document!


P3-REQ-17-3-005

Each FX logical Node SHALL identify its FX logical Node Roles, responsibilities, Runtime Plane participation, Communication Endpoints, information structures, governance constraints, traceability relationships, and evidence expectations.

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.

A logical Node is an architectural construct rather than an implementation construct. Defining the architectural characteristics of each logical Node while explicitly distinguishing logical Nodes from implementation artefacts preserves platform independence and prevents architectural concepts from being confused with deployment technologies.

This requirement applies to every FX logical Node defined within the FX Demo Logical Profile.

It applies specifically to:

  • logical Node specifications;
  • Node Role definitions;
  • Runtime Plane assignments;
  • Communication Endpoint definitions;
  • logical information structures;
  • governance documentation; and
  • architectural reviews.

Verification SHALL confirm that every FX logical Node includes the required architectural characteristics and remains independent of implementation technologies.

Verification activities should include review checks confirming that:

  • Node Roles are identified;
  • responsibilities are documented;
  • Runtime Plane participation is defined;
  • Communication Endpoints are identified;
  • logical information structures are defined;
  • governance and traceability relationships are documented;
  • evidence expectations are documented; and
  • logical Nodes are not described as implementation artefacts.

This requirement establishes complete architectural definitions for FX logical Nodes while preserving separation between logical architecture and implementation.

Related requirement identifiers:

Related source section:

Draft


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-005.1784670943.txt.gz
  • Last modified: 2026/07/21 14:55
  • by owen