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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|