This is an old revision of the document!
3.1 Traceability to SIP-RA
SIP-RA supplies the parent architecture discipline for structured information processing systems. This part specialises that discipline into a distributed, node-based Logical Architecture for financial systems.
The Logical Architecture / PIM preserves the SIP-RA emphasis on structured information, explicit interfaces, separation of concerns, Traceability, governed processing, reviewability, and implementation independence. It applies those concerns by defining identifiable logical Nodes, Logical Communication Endpoints, Logical Data Structure Definitions, logical Runtime Planes, logical interaction patterns, and logical traceability relationships.
Table 3-1: SIP-RA concerns addressed by the Logical Architecture / PIM
| SIP-RA concern | Part 2: logical treatment |
|---|---|
| Structured information processing | Defines logical information structures, logical messages, logical events, logical commands, logical assertions, and logical records. |
| Explicit interfaces | Defines Logical Communication Endpoints and logical interaction roles. |
| Separation of concerns | Defines logical Runtime Planes and separates control, data, health, policy/release, and audit/provenance concerns. |
| Traceable interpretation | Defines logical traceability relationships between concepts and logical elements, and between logical interactions and evidence expectations. |
| Governed processing across boundaries | Defines logical governance relationships, logical policy constraints, and logical release interactions. |
| Audit and review | Defines logical audit, provenance, evidence, replay, and reconstruction relationships. |
| Implementation independence | Avoids binding logical elements to DDS, REST, RPC, Protocol Buffers, IDL, Python, Kubernetes, K3S, Docker, RTI Connext DDS, Crucible, or other implementation mechanisms. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.