6.4 Tool Installation Notes [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.4 Tool Installation Notes ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:06-prerequisites-and-tooling:start | Return to Prerequisites and Tooling ]]

The handbook should provide enough installation guidance for a developer to prepare the Phase 0 environment on a supported operating system. Installation notes should not attempt to replace vendor documentation, but they should identify the project-specific decisions that matter for Phase 0.

Installation notes should cover:

  - Where developers should obtain each required tool.
  - Which edition, package, or installer the team expects.
  - Which environment variables or path updates does the tool require?
  - Which setup scripts must developers run before using the tool?
  - Which commands should developers run to verify installation?
  - Which known installation issues affect Phase 0?

The team should document operating-system-specific differences where they matter. For example, shell scripts, path separators, executable names, line endings, Docker permissions, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] environment setup, and Python virtual environments may behave differently across macOS, Linux, and Windows.

Installation notes should support [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Repeatability]]. A developer should be able to follow the notes, run the prerequisite check, and know whether the environment satisfies the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

----

<WRAP centeralign>

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

</WRAP>