full system documentation

You have now, with help of our System Analyst, made all decisions as to which features you wish your web application to have, how they will work, and may have revised or broken down the features into several stages of development.

The amount of documentation needed at this point is fairly minimal, as, for instance the time to actually create a feature in code using our proprietary code modules is usually way less than recording and specifying the code in detail on paper, the long way that another programmer would have to write it.

For this reason, we usually only further document those things for our programmers that could be ambiguous, and work directly from the system draft notes for the remainder. This allows our programmers to work efficiently and keep development time as short as possible. Our programmers know our programming techniques and proprietary code modules inside out, so re-explaining the wheel for every project, when we all know exactly what a certain type of wheel looks like, is a waste of the clients' time and money.

However if we were requested to create documentation for another programmer to do the work, it would be necessary to create explicit documentation for them not only for the project, but for the base assumptions underlying our proprietary coding methods. This can be very time consuming.

Your Next Step > PHP Programming