Re: requirement documents?

[derby]

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

[markjugg]

I'm reading and enjoying ISBN by the same author as the above. It has good information on the various preparation stages of software construction that seem interesting.

OT: Hmm..according to preview The Amazon tag might not exist yet. :) I checked the conveniently linked "Writeup Formatting Tips", but I couldn't easily find a link to a page about "bracket" tags I can use from there.

Mark

[pfaut]

See What shortcuts can I use for linking to other information? for linking tips.

90% of every Perl application is already written. ⇒

dragonchild