Added by Geoff Sauer on Apr 28, 2006.
Average rating: 3.00/5.00 (n=3, std dev: 2.00)
 


Errors in requirements specifications translate into poor designs, code that does the wrong thing, and unhappy customers. Requirements documentation should be inspected early and often. Anything you can do to prevent requirements errors from propagating downstream will save you time and money. Karl Wiegers shows you how.
 
  View all five works by Wiegers, Karl E.  
  View all 11 works published by StickyMinds  

Please share your rating/opinion of "Inspecting Requirements".
 PoorExcellent 
click this box if you find the link above broken or out-of-date.

Copyright © 2001-17 by the EServer. All rights reserved.Add a Work | Discussion Forum | Habitués