P4-REQ-21-11-004

Return to Requirements

Statement

The Developer Handbook SHALL define naming conventions.

Source

Part 4, Section 21.11: Developer Handbook Requirements.

Rationale

Naming conventions provide consistent identification across source files, modules, IDL structures, generated types, DDS Topics, QoS profiles, configuration files, scripts, and traceability artifacts.

Consistent naming improves readability, reviewability, and traceability across the Phase 0 implementation baseline.

Applies To

This requirement applies to:

repository directories;source files and modules;IDL structures and generated types;DDS Topics and QoS profiles;configuration files; andscripts and traceability artifacts.

Verification

Verification SHALL confirm that the Developer Handbook defines naming conventions for applicable Phase 0 artifact categories.

Verification activities should include review checks confirming that:

directory naming is addressed;source and module naming is addressed;IDL and generated-type naming is addressed;DDS Topic and QoS naming is addressed; andscript and configuration naming is addressed.

Traceability

This requirement establishes the naming discipline used throughout the Phase 0 implementation baseline.

Related requirement identifiers:

Related source section:

Status

Draft

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