| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:02-part:02-relationship-to-part-0-and-part-1:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido | fxdemo:02-part:02-relationship-to-part-0-and-part-1:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| Part 0 provides the Document Set Overview and Reader’s Guide for the Financial Systems Archetype. It explains the purpose of the document set, the relationship to SDIS/SIP-RA, the layered document structure, the onion model, document responsibilities, layering rules, and navigation guidance. | Part 0 provides the Document Set Overview and Reader’s Guide for the Financial Systems Archetype. It explains the purpose of the document set, the relationship to SDIS/SIP-RA, the layered document structure, the onion model, document responsibilities, layering rules, and navigation guidance. |
| |
| Part 1 defines the Conceptual Architecture for the Financial Systems Archetype. It establishes the conceptual definitions, classification model, separation-of-concerns model, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] concepts, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] concepts, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concepts, and conceptual requirements that later parts preserve. | Part 1 defines the Conceptual Architecture for the Financial Systems Archetype. It establishes the conceptual definitions, classification model, separation-of-concerns model, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] concepts, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] concepts, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concepts, and conceptual requirements that later parts preserve. |
| |
| This part depends on both Part 0 and Part 1. It relies on Part 0 for the document-set map and layering rules. It relies on Part 1 for the conceptual foundation. | This part depends on both Part 0 and Part 1. It relies on Part 0 for the document-set map and layering rules. It relies on Part 1 for the conceptual foundation. |
| |
| Part 2 performs the second architectural role within the document set. It defines a single distributed, node-based Logical Architecture / PIM that conforms to Part 1. It specialises Part 1 concepts into platform-independent logical Nodes, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Roles]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definitions]], logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical traceability relationships. | Part 2 performs the second architectural role within the document set. It defines a single distributed, node-based Logical Architecture / PIM that conforms to Part 1. It specializes Part 1 concepts into platform-independent logical Nodes, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Logical Node Roles]], [[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, logical governance relationships, and logical traceability relationships. |
| |
| Table 2-1 summarises the relationship among Part 0, Part 1, and Part 2. | Table 2-1 summarises the relationship among Part 0, Part 1, and Part 2. |