Differences
This shows you the differences between two versions of the page.
| 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] – ↷ Page moved and renamed from fxdemo:01-part:03-3-coverage-of-the-original-fx-demo-reference-architecture to fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-3-coverage-of-the-original-fx-demo-reference-architecture owen | fxdemo: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 ====== | ====== 3.3 Coverage of the Original FX Demo Reference Architecture ====== | ||
| - | The original FX Demo 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 | + | [[fxdemo: |
| - | Part 1 uses the original FX Demo Reference Architecture as source material for the conceptual architecture. Later parts carry forward the logical, implementation, | + | |
| - | Table 3-3: Normalised | + | The original FX Demo [[dido: |
| - | ^ Original FX Demo Reference Architecture material ^ Normalised | + | |
| + | Part 1 uses the original FX Demo [[dido: | ||
| + | |||
| + | Table 3-3: Normalized | ||
| + | |||
| + | ^ Original FX Demo Reference Architecture material ^ Normalized | ||
| | Architectural terms and conventions | Part 1 and Part 2 | | | Architectural terms and conventions | Part 1 and Part 2 | | ||
| - | | Node, Node Identity, and Communication Endpoint | Part 1 | | + | | [[dido: |
| - | | Data Structure Definition and Data Structure Instance | Part 1 and Part 2 | | + | | [[dido: |
| | Domain Event, Analytical Assertion, and State | Part 2 and Part 3 | | | 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 | | | Data in Motion and Data at Rest | Part 1, Part 2, and Part 3 | | ||
| - | | Data Plane, Control Plane, Health and Observability Plane, Policy and Release Plane, and Audit and Provenance Plane | Part 1, Part 2, and Part 3 | | + | | [[dido: |
| | IEF Policy Layer and policy-mediated release | Part 1, Part 2, Part 3, and Part 5 | | | IEF Policy Layer and policy-mediated release | Part 1, Part 2, Part 3, and Part 5 | | ||
| | QoS and QoS Profiles | Part 4 | | | QoS and QoS Profiles | Part 4 | | ||
| Line 17: | Line 21: | ||
| | Common Data Type Framework | Part 2 and Part 4 | | | Common Data Type Framework | Part 2 and Part 4 | | ||
| | Local Authoritative Ontology Framework | Part 2 and Part 3 | | | Local Authoritative Ontology Framework | Part 2 and Part 3 | | ||
| - | | Node Role Framework | Part 2 and Part 3 | | + | | [[dido: |
| | FX interaction sequences and use cases | Part 3 | | | FX interaction sequences and use cases | Part 3 | | ||
| | DDS, IDL, QoS, Python, and implementation mappings | Part 4 | | | DDS, IDL, QoS, Python, and implementation mappings | Part 4 | | ||
| - | | Kubernetes, K3s, Crucible, acceptance checks, runtime evidence, and deployment procedures | Part 5 | | + | | Kubernetes, K3s, Crucible, acceptance checks, runtime |
| | Scripts, repository structure, and developer conventions | Developer handbook or repository documentation | | | Scripts, repository structure, and developer conventions | Developer handbook or repository documentation | | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | |||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||