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

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.