fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-3-coverage-of-the-original-fx-demo-reference-architecture

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
fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-3-coverage-of-the-original-fx-demo-reference-architecture [2026/06/25 14:37] – removed - external edit (Unknown date) 127.0.0.1fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-3-coverage-of-the-original-fx-demo-reference-architecture [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== 3.3 Coverage of the Original FX Demo Reference Architecture ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +The original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] provides source material for many concepts and profiles in the Financial Systems Archetype document set. The new document set does not discard that material. It relocates each concern to the proper layer.
 +
 +Part 1 uses the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] as source material for the conceptual architecture. Later parts carry forward the logical, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] material.
 +
 +Table 3-3: Normalized coverage of original FX Demo Reference Architecture material
 +
 +^ Original FX Demo Reference Architecture material ^ Normalized location ^
 +| Architectural terms and conventions | Part 1 and Part 2 |
 +| [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] | Part 1 |
 +| [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] and [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] | Part 1 and Part 2 |
 +| Domain Event, Analytical Assertion, and State | Part 2 and Part 3 |
 +| Data in Motion and Data at Rest | Part 1, Part 2, and Part 3 |
 +| [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] | Part 1, Part 2, and Part 3 |
 +| IEF Policy Layer and policy-mediated release | Part 1, Part 2, Part 3, and Part 5 |
 +| QoS and QoS Profiles | Part 4 |
 +| Topic Framework | Part 2, Part 3, and Part 4 |
 +| Data Structure Framework | Part 2, Part 3, and Part 4 |
 +| Common Data Type Framework | Part 2 and Part 4 |
 +| Local Authoritative Ontology Framework | Part 2 and Part 3 |
 +| [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]] Framework | Part 2 and Part 3 |
 +| FX interaction sequences and use cases | Part 3 |
 +| DDS, IDL, QoS, Python, and implementation mappings | Part 4 |
 +| Kubernetes, K3s, Crucible, acceptance checks, runtime [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and deployment procedures | Part 5 |
 +| Scripts, repository structure, and developer conventions | Developer handbook or repository documentation |
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>
 +