| Next revision | Previous revision |
| fxdemo:02-part:05-logical-architecture-overview:05-2-logical-architecture-context:start [2026/07/02 15:38] – created owen | fxdemo:02-part:05-logical-architecture-overview:05-2-logical-architecture-context: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 ]] |
| |
| The Logical Architecture / PIM sits between the Part 1 Conceptual Architecture and later domain, implementation, deployment, testability, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers. | The Logical Architecture / PIM sits between the Part 1 Conceptual Architecture and later domain, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers. |
| |
| Part 1 defines the conceptual foundation. Part 2 specialises that foundation into platform-independent logical structures and relationships. Part 3 specialises this Logical Architecture for the FX Demo. Part 4 maps selected logical elements to implementation technologies. Part 5 defines deployment, testability, runtime operation, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection. | Part 1 defines the conceptual foundation. Part 2 specializes that foundation into platform-independent logical structures and relationships. Part 3 specializes this Logical Architecture for the FX Demo. Part 4 maps selected logical elements to implementation technologies. Part 5 defines deployment, testability, runtime operation, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection. |
| |
| The logical architecture, therefore, serves as the bridge between stable conceptual meaning and later choices of realisation. It provides enough structure to support design, review, specialisation, and implementation mapping while avoiding technology-specific commitments. | The logical architecture, therefore, serves as the bridge between stable conceptual meaning and later choices of realization. It provides enough structure to support design, review, specialization, and implementation mapping while avoiding technology-specific commitments. |
| |
| Figure 5-2 shows the position of Part 2 within the document-set layering model. | Figure 5-2 shows the position of Part 2 within the document-set layering model. |