DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-22T23:13:42+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-1-overview?rev=1784403224&do=diff 12.1 Overview Go to Top Part 1 defines the conceptual architecture for the Financial Systems Archetype. Part 2 defines the Logical Architecture / Platform Independent Model (PIM). The Logical Architecture / PIM uses the concepts defined in Part 1 to describe platform-independent relationships, responsibilities, constraints, information flows, and interaction patterns. It does not introduce implementation technologies, deployment mechanisms, product choices, runtime scripts, or text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-2-conceptual-elements-become-logical-elements?rev=1785852565&do=diff 12.2 Conceptual Elements Become Logical Elements Go to Top The Logical Architecture / PIM refines conceptual elements into platform-independent logical elements. For example, Part 1 defines Node as an architectural participant in a distributed Financial System. Part 2 may define Logical Nodes and describe the responsibilities, interactions, and constraints. text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-3-logical-architecture-preserves-conceptual-meaning?rev=1785852565&do=diff 12.3 Logical Architecture Preserves Conceptual Meaning Go to Top The Logical Architecture / PIM preserves the meaning of the conceptual elements defined in Part 1. A logical element may specialize, refine, constrain, or relate a conceptual element. It does not redefine the conceptual element. A Logical text/html 2026-07-11T18:15:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-4-logical-architecture-remains-platform-independent?rev=1783793713&do=diff 12.4 Logical Architecture Remains Platform Independent Go to Top The Logical Architecture / PIM remains independent of implementation technologies. Part 2 may identify logical interactions, message flows, roles, responsibilities, state relationships, validation responsibilities, policy interactions, audit relationships, and text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-5-logical-architecture-supports-domain-profiles?rev=1784403224&do=diff 12.5 Logical Architecture Supports Domain Profiles Go to Top Part 2 provides the reusable logical foundation for Domain profiles. A Domain profile, such as the FX Demo Logical Profile, specializes the Logical Architecture / PIM for a specific financial Domain. The Domain profile inherits the conceptual definitions from Part 1 and the platform-independent logical relationships from Part 2. text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-6-logical-architecture-provides-the-basis-for-implementation-profiles?rev=1785852565&do=diff 12.6 Logical Architecture Provides the Basis for Implementation Profiles Go to Top Implementation profiles use the Logical Architecture / PIM as their source for technology mapping. For example, a later implementation profile may map: Logical Communication Endpoint to a DDS TopicLogical Data Structure Definition to an IDL structure text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-7-traceability-from-part-1-to-part-2?rev=1785852565&do=diff 12.7 Traceability from Part 1 to Part 2 Go to Top Part 2 should maintain explicit Traceability to Part 1. Traceability from each major logical element to its conceptual source allows reviewers to verify that the logical architecture preserves the conceptual architecture and prepares a clear basis for implementation profiles, deployment profiles, and text/html 2026-07-11T18:15:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/12-8-boundary-between-part-1-and-part-2?rev=1783793713&do=diff 12.8 Boundary Between Part 1 and Part 2 Go to Top Part 1 defines conceptual meaning. Part 2 defines a Platform Independent Model (PIM) logical Structure. Part 2 may add logical relationships, constraints, interaction patterns, participation models, state relationships, and information-flow responsibilities. It does not change the definitions in Part 1. text/html 2026-07-04T00:14:28+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/12-relationship-to-the-logical-architecture-pim/start?rev=1783124068&do=diff 12. Relationship to the Logical Architecture / PIM Go to Top Contents 12-relationship-to-the-logical-architecture-pim index ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.