project documentation

I'm a little new to web development, so there's a lot of things that are 
foreign to me including the buzz word.  Thankfully, I have very forgiving 
clients and business partners.  And that I'm learning fast.

There's one thing that I can't stand to let go any longer though.  It's 
project documentation.  There are RFP, project specs, Design Documents, etc, 
etc.  What are all the forms of documentation that are necessary throughout 
the life of a project?

Here's my understanding....

There's the RFP... a document requesting companies to submit proposals on 
work that needs to be done.

Project Specs...  A document that is much more useful than an RFP because it 
generally has the technical detail necessary for making an accurate bid.

Design Document...  The document that details the target audience, their 
needs, the sites goals, desired features, how those features will be 
implimented, etc. etc.

... And that's all I know.

During the course of the development, I assume that the Design Document will 
mutate from "what we want it to do" into "what we developed."  Sort of a 
Post-Development recap of what work was done.  This document would serve as 
the blue prints of the site in the same way as the blue prints serve a house.

I apologize if my question is not clear.  If you need elaboration, don't 
hesitate to email me.
++Dan

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA