September 2007
Intermediate to advanced
600 pages
20h 21m
English
Even the most accomplished developers sometimes jump in without writing anything down on paper first. Those same developers will tell you that in most instances, working this way turns out to be a mistake. Sooner or later you realize you forgot some feature your client was expecting. Without documents, whether you really forgot the feature—or whether your client simply didn’t mention it—can’t be proven. In short, it simply can’t hurt to put things down on paper.
At the very least, you should have some type of project specifications document that describes the application in plain English (or whatever) and lists all the critical elements or features. This document should also include approximations of ...
Read now
Unlock full access