Differences
This shows you the differences between two versions of the page.
| 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] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Platform Specific Model (PSM) ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Platform Specific Model, or PSM, provides a technology-specific model of a system. It sits between the [[dido: | ||
| + | |||
| + | Within the FX Demo [[dido: | ||
| + | |||
| + | The PSM preserves the architectural meaning, information semantics, governance constraints, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //model of a system that specifies the use of features of a specific technological platform// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from OMG Model Driven Architecture terminology | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A PSM defines technology-specific structure, behavior, and constraints derived from a Platform Independent Model. | ||
| + | |||
| + | In the FX Demo Reference Architecture, | ||
| + | |||
| + | Implementation artifacts realize the PSM in executable, generated, configured, deployed, or operational form. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | 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 artifacts realize those PSM specifications as source code, generated code, configuration files, build scripts, deployment files, logs, tests, and runtime services. | ||