Added by Geoff Sauer on Sep 14, 2007.
Average rating: 3.00/5.00 (n=1)
 


Poorly written requirements are the single biggest point of failure in the development of new software systems. Requirements that are not carefully defined or are written in ambiguous terms result in an endless stream of re- working and budget overruns. Smart project managers these days are trying to solve the problem with the addition of professional communicators to their project teams to both elicit crisp requirements and express them in simple, accessible terms.
 
  View all 2240 works published by STC Proceedings  

Please share your rating/opinion of "Requirements: A Primer for Communicators".
 PoorExcellent 
The link to this work seems to be broken.

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