P4-REQ-21-4-003 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== P4-REQ-21-4-003 ======

[[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]

===== Statement =====

Each implementation node artefact SHALL identify the FX logical Node Role or Roles it performs.

===== Source =====

Part 4, Section 21.4: Logical Node Mapping Requirements.

===== Rationale =====

Node Roles identify the logical responsibilities performed within or by an FX logical Node. Recording the applicable Node Roles makes the allocation of implementation responsibility explicit.

This prevents implementation modules from acquiring responsibilities that cannot be traced to the FX Demo Logical Profile.

===== Applies To =====

This requirement applies to:

  * implementation node artefacts;
  * implementation responsibilities;
  * supporting modules; and
  * FX logical Node Role mappings.

===== Verification =====

Verification SHALL confirm that each implementation node artefact identifies the FX logical Node Role or Roles it performs.

Verification activities should include review checks confirming that:

  * applicable Node Roles are explicitly identified;
  * performed responsibilities correspond to those Node Roles;
  * multiple Node Roles are recorded where applicable; and
  * no ungoverned Node Role is introduced by implementation code.

===== Traceability =====

This requirement connects Phase 0 implementation responsibilities to the FX logical Node Roles defined in Part 3.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-4-001]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-4-002]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-4-010]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-4-logical-node-mapping-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>