The difficulty of handling changing requirements within traditional development processes is described. The origins of changing user and organizational requirements are discussed and different types are classified. The author identifies a number of ways in which different approaches to design may help to deal with change as well as mechanisms which should underpin effective communication between users and designers. >
['Susan Harker', 'Ken Eason', 'John E. Dobson']
The change and evolution of requirements as a challenge to the practice of software engineering