loading...
 
Abstract
 
Requirements Change: What?s the Alternative?
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Numerous studies have shown that a software project’s cost, schedule and defect density escalate as the rate of requirements change increases. Yet none of these studies have explored the effects of not making requirements changes in response to changes in user needs. This paper explains why a project incurs just as much, if not more, risk when requirements changes are suppressed.
Index Terms:
requirements engineering, requirements management, user needs, requirements change, requirements volatility, software risks
Citation:
Alan M. Davis, Nur Nurmuliani, Sooyong Park, Didar Zowghi, "Requirements Change: What?s the Alternative?," compsac,pp.635-638, 2008 32nd Annual IEEE International Computer Software and Applications Conference, 2008
Usage of this product signifies your acceptance of the Terms of Use.
     


Click here to go to beta feedback form