Get Thinking
A detailed discussion of these questions can be found in the "Appendix A" section on page 544.
Mull It Over
Is a poor specification better than no specification at all?
How detailed does a good specification have to be?
Is it important that all the documents in a company/project have a common presentation style?
How should you store documents? Should you provide an index of them (by type or by project), for example?
How should you conduct a specification review?
Does self-documenting code render all specifications useless? Specific ones?
How can a document be collaborated on by more than one author?
Getting Personal
Who decides on the contents of your documents?
Consider your current project. Do you have:
A requirements specification?
An architecture ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access