Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| fxdemo:00-part:03-purpose:start [2026/07/07 11:38] – owen | fxdemo:00-part:03-purpose:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| 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 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, | + | 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, |
| The document set supports the following objectives: | The document set supports the following objectives: | ||
| - Define the concepts of a stable financial system before selecting technologies. | - Define the concepts of a stable financial system before selecting technologies. | ||
| - Preserve separation between conceptual meaning, logical structure, implementation mapping, deployment mechanics, and evidence. | - Preserve separation between conceptual meaning, logical structure, implementation mapping, deployment mechanics, and evidence. | ||
| - | - Support traceability from high-level concepts to deployed | + | - Support traceability from high-level concepts to deployed |
| - Provide a reusable foundation for financial domains such as Foreign Exchange, Commercial Paper, regulatory reporting, and other future financial-system profiles. | - 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 implementation profiles to vary without redefining the conceptual or logical architecture. | ||