Far too often, documentation is left as an after-thought, to be performed once the application is developed and running. This can be a serious mistake.

We will have more to say regarding the user manual on the next slide.

Other design documentation should be maintained to record decisions made and, often just as important, decisions considered and rejected, and the reasons for the rejection. This will often save the time and effort of revisiting the same decision multiple times.

[audio] 32 [real] 32 Text to accompany slide 32, in Chapter 2 of An Introduction to Object-Oriented Programming