9.5 Type Generation Workflow

Go To Top

Return to DDS / IDL / Type Generation

The type generation Workflow should transform governed IDL source files into language-specific DDS implementation Artifacts. Developers should run type generation through the approved script or documented command, not through undocumented local generator invocations.

The recommended Workflow is:

Architecture / Catalogue Definitions
        ↓
IDL Source Files
        ↓
Approved DDS Type Generator
        ↓
Language-Specific Generated Artifacts
        ↓
Node Implementation Uses Generated Types
        ↓
Runtime Topics Carry Typed Instances

The generation Workflow should identify:

1. IDL source files used as input.
2. DDS vendor or type-generation tool.
3. Generator version.
4. Target language or languages.
5. Output directory.
6. Command or script used to perform generation.
7. Expected generated Artifacts.
8. Validation checks run after generation.
9. Evidence produced by the generation process, where applicable.

The team should route type generation through a script such as generateTypes when practical. The script should validate required inputs, check tool availability, write outputs to approved generated directories, and fail clearly when generation cannot complete.