dido:99_annexes:annex-d-requirements:part-04:p4-req-21-4-006

P4-REQ-21-4-006

Each implementation node artefact SHALL preserve traceability to the relevant Part 3 FX logical Node definition.

Part 4, Section 21.4: Logical Node Mapping Requirements.

Implementation node artefacts must remain tied to the logical Node definitions that justify their existence and responsibilities.

Preserving this traceability enables reviewers to move from implementation back to the authoritative logical definition and confirm that implementation behavior remains consistent with the FX Demo Logical Profile.

This requirement applies to:

  • implementation node artefacts;
  • file-header metadata;
  • node mapping records;
  • implementation traceability records; and
  • review records.

Verification SHALL confirm that every implementation node artefact preserves traceability to the relevant Part 3 FX logical Node definition.

Verification activities should include review checks confirming that:

  • the applicable Part 3 Node is identifiable;
  • traceability records agree with implementation mappings;
  • source-file or associated metadata preserves the relationship; and
  • reviewers can navigate from implementation artefact to logical source.

This requirement establishes backward traceability from implementation node artefacts to their authoritative Part 3 FX logical Node definitions.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-04/p4-req-21-4-006.txt
  • Last modified: 2026/08/06 16:03
  • by owen