6.3 Phase 0 Developer Handbook [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.

====== 6.3 Phase 0 Developer Handbook ======

[[fxdemo:04-part:06-phase-0-implementation-preconditions:start | Go To Phase 0 Implementation Preconditions ]]

The Phase 0 Developer Handbook must be in place and approved before coding begins.

The Developer Handbook defines the development rules that implementation contributors must follow. It includes file-header conventions, generated-file markings, naming conventions, coding style, logging conventions, exception-handling patterns, repository workflow, review expectations, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] conventions, and script usage rules.

The handbook supports consistent implementation behavior. It prevents implementation files, generated artifacts, scripts, and configuration files from entering the repository without a common discipline in place.

Part 4 defines the implementation profile and the architectural implementation requirements. The Developer Handbook explains how developers apply those requirements in day-to-day implementation work.

----

<WRAP centeralign>

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

</WRAP>