P4-REQ-21-11-004

The Developer Handbook SHALL define naming conventions.

Part 4, Section 21.11: Developer Handbook Requirements.

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.

This requirement applies to:

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

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; and
  • script and configuration naming is addressed.

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

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-04/p4-req-21-11-004.txt
  • Last modified: 2026/08/07 14:16
  • by owen