3. Traceability to Parent and Source Architectures [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.
====== 3. Traceability to Parent and Source Architectures ======
[[fxdemo:01-part:start | Go to Top ]]

The Financial Systems Archetype preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to three architectural sources.

First, it traces to **SIP-RA** as the parent structured-information processing [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture (RA)]]. SIP-RA provides the cross-domain discipline for structured information processing, including separation of [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]], [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]], [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]], [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]], and implementation-independent processing.

Second, it aligns with **FDIS-RA** as a financial-domain interpretation architecture. FDIS-RA provides precedent for treating semantic [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], validation, comparability, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], auditability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as architectural concerns in financial and regulated reporting environments.

Third, it normalizes source material from the original **FX Demo Reference Architecture**. The original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture (RA)]] combined conceptual definitions, logical architecture, DDS-oriented implementation concerns, Quality of Service (QoS), topics, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]s, common data types, ontology concerns, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]s, use cases, and catalogs. The Financial Systems Archetype document set separates those concerns into conceptual, logical, profile, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers.

===== Contents =====

{{indexmenu>fxdemo:01-part:04-traceability-to-parent-and-source-architectures#1|js navbar nocookie maxjs#1 id#fxdemo_01_part_04_nav}}

----

<WRAP centeralign>

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

</WRAP>