This is very much a hands-on and how-to description of ways to organize and present documentation of automated systems. While intended for technical writers, the book offers value to others. The text emphasizes that documenation should take a strong customer/reader orientation. Both developers and testers would be well advised to follow the methods the authors suggest for understanding customer needs.

In addition, the book describes a standard which should guide developers/writers in creating documentation and guide quality/testing specialists in evaluating the documentation. The book balances sections on writing style with ones on management of the publication process. "Good" and "bad" examples are included.