One of the few decent things out of MS is MS Press. Check out
Software Project Survival Guide.
To answer some of your questiosn:
- requirements doc - a description of what the software should do
(sometimes called the functional spec)
- detailed design doc - a description of the low level implementation
(sometimes called the technical spec)
-
traceability matrix - a document that pins test scenarios to items
in the requirements doc (ensure what's built is what's asked for)
Other docs - depends on the model being followed. But you could have
- Software Development Plans
- Schedules and estimates
- Interface Guidelines
- Qualtiy Assurance/Testing Plans
- Deployment Plans
- Architecture Plan
- User Manuals
- Change and Control Plan
And a whole lot more.
-derby