3.3 Traceability to Part 1 Conceptual Architecture
Part 1 defines the conceptual foundation for the Financial Systems Archetype. This part builds outward from that foundation by specializing the concepts from Part 1 into platform-independent logical elements.
This part does not redefine the concepts in Part 1. It gives those concepts logical structure, relationships, responsibilities, constraints, and interaction patterns.
Table 3-3: Part 1 concepts specialized by the Logical Architecture / PIM
| Part 1 concept | Part 2: logical treatment |
|---|---|
| Node | Logical Node |
| Node Identity | Logical Node Identity |
| Node Role | Logical Node Role |
| Runtime Plane | Logical Runtime Plane |
| Communication Endpoint | Logical Communication Endpoint |
| Data Structure Definition | Logical Data Structure Definition |
| Data Structure Instance | Logical Data Structure Instance |
| Evidence | Logical evidence expectation or logical evidence class |
| Traceability | Logical traceability relationship |
| Classification Path | Logical scope inherited by profiles and logical models |
| Separation of Concerns | Logical separation of runtime, information, governance, traceability, and evidence concerns |
The Traceability from Part 1 to Part 2 allows reviewers to confirm that the Logical Architecture / PIM preserves the conceptual foundation while adding logical specificity.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.