13.10 QoS Boundaries and Non-Goals [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 13.10 QoS Boundaries and Non-Goals ======

[[fxdemo:04-part:13-phase-0-qos-profile-model:start | Go To Phase 0 QoS Profile Model ]]

The Phase 0 QoS Profile Model defines communication behavior for the Phase 0 implementation baseline. It does not define production-grade QoS for all future phases.

Phase 0 QoS profiles do not redefine [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], FX logical information structures, or FX logical interaction patterns. They realize selected communication behavior for the selected Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] implementation context.

Phase 0 QoS profiles also do not define deployment topology, network configuration, security policy, operational monitoring, runtime [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], or acceptance results. Part 5 defines deployment, testability, operation, observation, and evidence concerns for the selected Phase 0 implementation.

Later development phases may extend, refine, supersede, or replace the Phase 0 QoS profiles while preserving [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to applicable Runtime Planes, DDS Topics, implementation participants, and FX logical Communication Endpoints.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>