Differences
This shows you the differences between two versions of the page.
| fxdemo:04-part:13-phase-0-qos-profile-model:13-2-qos-profile-purpose:start [2026/07/25 10:09] – created owen | fxdemo:04-part:13-phase-0-qos-profile-model:13-2-qos-profile-purpose:start [2026/07/25 10:14] (current) – owen | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Phase 0 uses QoS profiles to make communication behavior explicit. | Phase 0 uses QoS profiles to make communication behavior explicit. | ||
| - | A QoS profile identifies the communication behavior expected for a selected Runtime Plane or Topic family. It allows implementation participants to use consistent settings for reliability, | + | A QoS profile identifies the communication behavior expected for a selected |
| The QoS Profile Model supports: | The QoS Profile Model supports: | ||
| * Consistent DDS behavior across implementation participants; | * Consistent DDS behavior across implementation participants; | ||
| - | * Traceability from Runtime Plane purpose to communication behavior; | + | * [[dido: |
| * Review of Topic compatibility between publishers and subscribers; | * Review of Topic compatibility between publishers and subscribers; | ||
| * Repeatable configuration of DDS participants, | * Repeatable configuration of DDS participants, | ||
| * Later deployment and testability planning; and | * Later deployment and testability planning; and | ||
| - | * Evidence planning for communication behavior. | + | * [[dido: |
| The Phase 0 QoS Profile Model defines only the QoS discipline needed for the Phase 0 implementation baseline. Later development phases may extend, refine, supersede, or replace these profiles. | The Phase 0 QoS Profile Model defines only the QoS discipline needed for the Phase 0 implementation baseline. Later development phases may extend, refine, supersede, or replace these profiles. | ||