Platform Specific Model (PSM)

Return to Terms and Definitions

Platform Specific Model, or PSM, provides a technology-specific model of a system. It sits between the platform_independent_model and the implementation artefacts.

Within the FX Demo 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.

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.

model of a system that specifies the use of features of a specific technological platform

Adapted from OMG Model Driven Architecture terminology

A PSM defines technology-specific structure, behaviour, 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.

Implementation artefacts realise the PSM in executable, generated, configured, deployed, or operational form.

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.