Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== P4-REQ-21-9-011 ====== [[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]] ===== Statement ===== Each QoS profile mapping SHALL identify the configuration artifact that defines the profile. ===== Source ===== Part 4, Section 21.9: QoS Profile Requirements. ===== Rationale ===== A QoS profile must be tied to a governed configuration artifact so that its selected behavior can be reviewed, reproduced, changed, and versioned consistently. Identifying the defining configuration artifact prevents QoS behavior from becoming an undocumented runtime choice. ===== Applies To ===== This requirement applies to: * QoS profile mappings; * configuration artifacts; * DDS configuration; * repository locations; and * implementation governance. ===== Verification ===== Verification SHALL confirm that each QoS profile mapping identifies the configuration artifact that defines the profile. Verification activities should include review checks confirming that: * the configuration artifact is identifiable; * the artifact resides in an approved repository location; * the defined profile matches the mapping; * changes are governed; and * the applicable configuration version is reviewable. ===== Traceability ===== This requirement connects each Phase 0 QoS profile mapping to its governed configuration source. Related requirement identifiers: * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-001]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-012]] Related source section: * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-9-qos-profile-requirements:start]] ===== Status ===== Draft ---- <WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP> dido/99_annexes/annex-d-requirements/part-04/p4-req-21-9-011.txt Last modified: 2026/08/07 14:01by owen