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:00-foreword:start [2026/06/24 15:15] – ↷ Page moved and renamed from fxdemo:00-part:00-foreword to fxdemo:00-part:00-foreword:start nick_didofxdemo:00-part:00-foreword:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ======Foreword ====== ======Foreword ======
 +[[fxdemo:00-part:start | Go to Top ]]
  
-The Financial Systems Archetype document set provides a layered architecture for applying structured information processing principles to financial systems. The document set separates conceptual architecture, logical architecture, domain profiles, implementation profiles, deployment profiles, testability, and evidence so authors, reviewers, implementers, and maintainers can develop, review, govern, and evolve each concern at the appropriate level.+The Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype]] document set provides a layered architecture for applying structured information processing principles to [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system]]. The document set separates conceptual architecture, logical architecture, domain profiles, implementation profiles, deployment profiles, testability, and evidence so authors, reviewers, implementers, and maintainers can develop, review, govern, and evolve each concern at the appropriate level.
  
 This part provides the reader’s guide for the document set. It explains the purpose of the document set, its relationship to SDIS/SIP-RA, the layered architecture, document responsibilities, and rules for preserving separation among conceptual, logical, implementation, deployment, and evidence concerns. This part provides the reader’s guide for the document set. It explains the purpose of the document set, its relationship to SDIS/SIP-RA, the layered architecture, document responsibilities, and rules for preserving separation among conceptual, logical, implementation, deployment, and evidence concerns.
  
 This part does not define the Financial Systems Archetype itself. It provides the map for reading the parts that do. This part does not define the Financial Systems Archetype itself. It provides the map for reading the parts that do.
 +
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>
 +
 +
  • fxdemo/00-part/00-foreword/start.1782339349.txt.gz
  • Last modified: 2026/06/24 15:15
  • by nick_dido