| requirements creep | can be avoided by - using incremental development
- carefully documenting the problem boundaries at an early stage
- estimating the time any proposed requirement will take
- . deferring major changes to subsequent releases if possible
|  |
| has definition The tendency for the set of requirements to relentlessly increase in size during the course of development, resulting in a system that is more expensive and complex than originally intended | |
| is a subtopic of 4.9 - Managing Changing Requirements | |
| is a kind of process | |
| may result in very significant cost overruns in projects | |
| occurs when changes to a system are really enhancements in disguise | |
| process | see also process^2 | |
Object Oriented Software Engineering View all facts Glossary Help
