StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would use the requirement numbering scheme already in place rather than creating a new one. I would document the following items for each requirement:</p> <ol> <li><strong>Requirement Status</strong>: This can be phrased in many different ways but you are tyring to communicate if the requirement was completed as listed, completed in a modified variant of what was listed or was simply not able to be completed at all.</li> <li><strong>Requirement Comment</strong>: Describes the previously listed requirement status. This is the "why" that will explain those items that were not able to fully meet the requirements.</li> <li><strong>Date completed</strong>: This is mostly for future product planning but also servers as a historical reference.</li> </ol> <p>A couple of other points to remember:</p> <ol> <li>Requirements may be reviewed by the customer, especially if the customer was the source of the requirements. Hence, this document needs to be as accurate and as informative as possible. (It's also another reason you don't change the requirement numbering scheme unless you have to.)</li> <li>Your testing department (assuming you have one) should be using these documents for their test planning and they need to know what requirments were met, which ones weren't and most importantly which ones changed and how.</li> </ol> <p>Lastly, unless you're putting on a dog and pony show for someone you shouldn't need screenshots as part of requirement documentation. You also shouldn't need to provide "proof" of completion. The testing department will do that for you.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload