| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model to dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model nick_dido | dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Platform Specific Model (PSM) ====== | ====== Platform Specific Model (PSM) ====== |
| |
| [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] | [[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| Platform Specific Model, or PSM, provides a technology-specific model of a system. It sits between the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model]] and the implementation artefacts. | Platform Specific Model, or PSM, provides a technology-specific model of a system. It sits between the [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model]] and the implementation artifacts. |
| |
| Within the FX Demo [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]], the PSM maps technology-neutral architectural structures and obligations from the PIM to selected platform features. These include middleware constructs, interface definitions, topic definitions, message structures, quality-of-service settings, adapter patterns, persistence mechanisms, deployment patterns, generated artefacts, and technology-specific constraints. | Within the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]], the PSM maps technology-neutral architectural structures and obligations from the PIM to selected platform features. These include middleware constructs, interface definitions, topic definitions, message structures, quality-of-service settings, adapter patterns, persistence mechanisms, deployment patterns, generated artifacts, and technology-specific constraints. |
| |
| The PSM preserves the architectural meaning, information semantics, governance constraints, policy obligations, jurisdictional constraints, evidence requirements, and behavioural responsibilities defined by the PIM. It adds the platform-specific details required to realise those obligations using selected technologies. | The PSM preserves the architectural meaning, information semantics, governance constraints, policy obligations, jurisdictional constraints, evidence requirements, and behavioral responsibilities defined by the PIM. It adds the platform-specific details required to realize those obligations using selected technologies. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Note ===== | ===== Note ===== |
| |
| A PSM defines technology-specific structure, behaviour, and constraints derived from a Platform Independent Model. | A PSM defines technology-specific structure, behavior, and constraints derived from a Platform Independent Model. |
| |
| In the FX Demo Reference Architecture, DDS domains, DDS topics, IDL definitions, generated types, QoS settings, OpenDDS configuration, adapters, graph persistence mappings, code modules, repository structure, scripts, logs, build artefacts, containers, and deployment files are Platform Specific Model or implementation artefacts. | In the FX Demo Reference Architecture, DDS domains, DDS topics, IDL definitions, generated types, QoS settings, OpenDDS configuration, adapters, graph persistence mappings, code modules, repository structure, scripts, logs, build artifacts, containers, and deployment files are Platform Specific Model or implementation artifacts. |
| |
| Implementation artefacts realise the PSM in executable, generated, configured, deployed, or operational form. | Implementation artifacts realize the PSM in executable, generated, configured, deployed, or operational form. |
| |
| ===== Example ===== | ===== Example ===== |
| A PSM specifies a policy decision function using DDS topics, IDL message structures, OpenDDS QoS policies, generated types, and a selected implementation language. | A PSM specifies a policy decision function using DDS topics, IDL message structures, OpenDDS QoS policies, generated types, and a selected implementation language. |
| |
| The implementation artefacts realise those PSM specifications as source code, generated code, configuration files, build scripts, deployment files, logs, tests, and runtime services. | The implementation artifacts realize those PSM specifications as source code, generated code, configuration files, build scripts, deployment files, logs, tests, and runtime services. |