| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:02-part:03-traceability-to-parent-and-source-architectures:03-1-traceability-to-sip-ra:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido | fxdemo:02-part:03-traceability-to-parent-and-source-architectures:03-1-traceability-to-sip-ra:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:02-part:start | Go To Top ]] | [[fxdemo:02-part:start | Go To Top ]] |
| |
| 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. | SIP-RA supplies the parent architecture discipline for structured information processing systems. This part specializes 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, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], governed processing, reviewability, and implementation independence. It applies those concerns by defining identifiable logical Nodes, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definitions]], logical Runtime Planes, logical interaction patterns, and logical traceability relationships. | The Logical Architecture / PIM preserves the SIP-RA emphasis on structured information, explicit interfaces, separation of concerns, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], governed processing, reviewability, and implementation independence. It applies those concerns by defining identifiable logical Nodes, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|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 | Table 3-1: SIP-RA concerns addressed by the Logical Architecture / PIM |
| |
| ^ SIP-RA concern ^ Part 2: logical treatment ^ | ^ SIP-RA concern ^ Part 2: logical treatment ^ |
| | Structured information processing | Defines [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|logical information structures]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_message|logical messages]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_event|logical events]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_command|logical commands]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_assertion|logical assertions]], and [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_record|logical records]]. | | | Structured information processing | Defines [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|logical information structures]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_message|logical messages]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_event|logical events]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_command|logical commands]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_assertion|logical assertions]], and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_record|logical records]]. | |
| | Explicit interfaces | Defines [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]] and logical interaction roles. | | | Explicit interfaces | Defines [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|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. | | | 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. | | | 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, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_policy_constraints|logical policy constraints]], and logical release interactions. | | | Governed processing across boundaries | Defines logical governance relationships, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_constraints|logical policy constraints]], and logical release interactions. | |
| | Audit and review | Defines logical audit, provenance, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]], replay, and reconstruction relationships. | | | Audit and review | Defines logical audit, provenance, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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. | | | 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. | |
| |