Requirements change: What's the alternative?

Publication Type:
Conference Proceeding
Proceedings - International Computer Software and Applications Conference, 2008, pp. 635 - 638
Issue Date:
Full metadata record
Files in This Item:
Filename Description Size
Thumbnail2008000737.pdf330.55 kB
Adobe PDF
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. © 2008 IEEE.
Please use this identifier to cite or link to this item: