In Chapter 1, we introduced requirements elicitation as we grappled with the nuances of different types of requirements and how to distill those into a readable form. In this chapter, our goal is to transform those requirements into design decisions.
Before we delve into the meat of the design contents, let us examine the document structure. A good design document is not a purely technical record, nor is it purely a business or project-based one. A well-written design document is intended for many audiences, from the technical implementers on various teams right up to the CEO.
Let us take a moment to define what a design document is not. A design document is not written to