Added by Geoff Sauer on May 21, 2006.
Average rating: 3.67/5.00 (n=3, std dev: 0.58)
 


Your requirements document needs to focus on the user’s goals. They should not be marketing’s list of features 'we’ve got to have' because the competition has these features. They should not be a list of things the programmers think ought to be included 'because we can add those things for very little cost.' Feature bloat does not benefit the user.
 
  View all ten works by Ferlazzo, Ellen Lawson  
  View all 13 works published by Sprezzatura Systems  

Please share your rating/opinion of "Goal Oriented 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