4. Layered Document Structure

Go to Top

The Financial Systems Archetype uses a layered document structure. Financial Systems Archetype

• Part 0: Document Set Overview and Reader’s Guide
• Part 1: Conceptual Architecture
• Part 2: Logical Architecture / PIM
• Part 3: FX Demo Logical Profile
• Part 4: Phase 0 Implementation Profile / PSM
• Part 5: Phase 0 Deployment, Testability, and Evidence Plan

Later work may add more parts for additional financial domains, implementation profiles, deployment profiles, or evidence packages. Later work may also add phase-specific extension profiles that introduce additional architectural planes or governance capabilities after the initial executable baseline has been established. For example, a later Phase 2 profile may introduce a Policy / Governance Plane and Release Plane to support policy-governed information sharing, authorized release, data sovereignty, data residency, metadata and aggregate views, and evidence for cross-boundary release. Such later profiles should trace back to the Conceptual Architecture and Logical Architecture / PIM rather than redefining them. For example: Part 3A: Commercial Paper Logical Profile Part 4A: Commercial Paper Implementation Profile / PSM Part 5A: Commercial Paper Deployment, Testability, and Evidence Plan The structure allows the Financial Systems Archetype to grow without turning one document into a mixed collection of concepts, implementation details, scripts, and test evidence.