Part 4 occupies the implementation-profile layer of the Financial Systems Archetype document set. It follows the document-set structure defined in Part 0, preserves the conceptual foundation defined in Part 1, realizes the logical architecture defined in Part 2, and maps selected FX logical profile elements defined in Part 3.
Part 0 provides the Document Set Overview and Reader's Guide. It explains the layered document structure, document responsibilities, separation rules, and navigation guidance. This part follows those rules by keeping implementation-profile concerns separate from conceptual, logical, deployment, testability, and evidence concerns.
Part 1 defines the Conceptual Architecture for the Financial Systems Archetype. It establishes the conceptual definitions, classification model, Runtime Plane concepts, traceability concepts, evidence concepts, and separation-of-concerns model that later parts preserve. This part does not redefine those concepts. It maps implementation artifacts to logical and conceptual sources, enabling reviewers to trace Phase 0 implementation choices back to the conceptual architecture.
Part 2 defines the Distributed Node-Based Logical Architecture (Platform-Independent Model (PIM)). It specializes the Part 1 conceptual foundation into reusable platform-independent logical Nodes, logical Node Roles, logical Communication Endpoints, logical information structures, logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical traceability relationships. This part realizes selected Part 2 logical architecture concepts through the Phase 0 implementation profile, as specialized by Part 3.
Part 3 defines the FX Demo Logical Profile. It specializes the Part 2 Logical Architecture / PIM for the Foreign Exchange Domain. It identifies FX logical Nodes, FX logical Node Roles, FX logical Communication Endpoints, FX logical information structures, FX Runtime Planes, FX interaction patterns, FX governance relationships, FX traceability relationships, and FX logical requirements. This Part maps selected elements of the Part 3 FX logical profile to Phase 0 implementation technologies and implementation artifacts.
Part 4 defines a phase-specific implementation profile. The Phase 0 Implementation Profile / Platform-Specific Model (PSM) establishes the Phase 0 implementation baseline. Later development phases may define additional implementation profiles that extend, refine, supersede, or replace this profile while preserving traceability to the applicable conceptual, logical, and domain logical profile elements.
Table 2-1: Relationship among Parts 0, 1, 2, 3, and 4.
| Part | Role | Relationship to this part |
|---|---|---|
| Part 0 | Document Set Overview and Reader's Guide | Provides the document-set structure, layering rules, and separation-of-concerns discipline that Part 4 follows. |
| Part 1 | Conceptual Architecture | Provides the conceptual foundation that Phase 0 implementation artifacts preserve through traceability. |
| Part 2 | Distributed Node-Based Logical Architecture / PIM | Provides the reusable logical architecture that this implementation profile realizes for Phase 0. |
| Part 3 | FX Demo Logical Profile | Provides the FX-specific logical profile that this implementation profile maps to Phase 0 implementation artifacts. |
| Part 4 | Phase 0 Implementation Profile / PSM | Defines the selected Phase 0 implementation mappings, technologies, implementation artifacts, conventions, and traceability relationships. |
Part 4, therefore, does not stand alone. It depends on the conceptual, logical, and FX logical profile layers that precede it. It also prepares Part 5 by identifying the implementation artifacts that Part 5 deploys, tests, observes, operates, and collects evidence for.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.