fxdemo:00-part:03-purpose:start

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:00-part:03-purpose:start [2026/06/24 15:16] – removed - external edit (Unknown date) 127.0.0.1fxdemo:00-part:03-purpose:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== 2. Purpose of the Document Set ======
 +[[fxdemo:00-part:start | Go to Top ]]
 +
 +The purpose of the Financial Systems Archetype document set is to provide a structured, reusable architecture for financial systems that follow the SDIS/SIP-RA discipline.
 +The Financial Systems Archetype also aligns with financial-domain interpretation guidance developed in FDIS-RA and preserves source material from the original FX Demo Reference Architecture. SIP-RA provides the parent with a structured information-processing discipline. FDIS-RA provides financial-domain precedent for governed interpretation, semantic traceability, validation, comparability, auditability, and evidence. The original FX Demo Reference Architecture provides source material that this document set normalizes across conceptual, logical, implementation, deployment, and evidence layers.
 +The document set supports the following objectives:
 +
 +  - Define the concepts of a stable financial system before selecting technologies.
 +  - Preserve separation between conceptual meaning, logical structure, implementation mapping, deployment mechanics, and evidence.
 +  - Support traceability from high-level concepts to deployed artifacts and observed evidence.
 +  - Provide a reusable foundation for financial domains such as Foreign Exchange, Commercial Paper, regulatory reporting, and other future financial-system profiles.
 +  - Allow implementation profiles to vary without redefining the conceptual or logical architecture.
 +  - Allow deployment profiles to vary across local, cloud, Kubernetes, air-gapped, or other environments without redefining the architecture.
 +  - Support evidence-based review, testing, and assurance.
 +
 +The document set prevents implementation choices from becoming the architecture. Later parts may discuss technologies such as DDS, IDL, Python, Kubernetes, Docker, RTI Connext DDS, and Crucible, but those technologies do not define the conceptual foundation.
 +
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>
 +