Code Craft

Get Thinking

A detailed discussion of these questions can be found in the "Appendix A" section on page 544.

Mull It Over

1. Is a poor specification better than no specification at all?

2. How detailed does a good specification have to be?

3. Is it important that all the documents in a company/project have a common presentation style?

4. How should you store documents? Should you provide an index of them (by type or by project), for example?

5. How should you conduct a specification review?

6. Does self-documenting code render all specifications useless? Specific ones?

7. How can a document be collaborated on by more than one author?

Getting Personal

1. Who decides on the contents of your documents?

2. Consider your current project. Do you have:

   1. A requirements specification?

   2. An architecture ...