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. The Financial Systems Archetype specialises in financial systems. SIP-RA addresses structured information processing across domains where organisations must process structured artefacts, interpret data, govern meaning, support traceable transformations, and preserve auditability and review. The Financial Systems Archetype carries those concerns into the Finance ecosphere while preserving platform independence and implementation neutrality. Part 1 preserves the following SIP-RA concerns at the conceptual level.
Table 3-1: SIP-RA concerns addressed by the Conceptual Architecture
| SIP-RA concern | Part 1 treatment |
|---|---|
| Separation of data, structure, semantics, and interpretation | Defines separation of concerns as a conceptual principle. |
| Governed processing across boundaries | Defines runtime planes, traceability, evidence, and governance of meaning. |
| Explicit architectural roles and responsibilities | Defines core conceptual elements, including Node, Node Role, Communication Endpoint, Data Structure Definition, Runtime Plane, and Evidence. |
| Traceable interpretation | Defines traceability as a conceptual element and architectural principle. |
| Platform independence | Keeps DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, and Crucible out of the conceptual layer. |
| Audit and review | Treats evidence, auditability, and provenance as architectural concerns. |
| Evolvability without loss of comparability | Preserves conceptual separation so later parts can evolve implementation and deployment profiles without redefining meaning. |