Requirement Change Management with respect to Different Models

Abstract

Changes in the requirements can be proposed by the clients continuously during the whole development cycle of the software. Those changes in requirements causes very major errors on development, cost and time etc. Because at very initial level, requirements are engineers before actual implementation. The effective approach is to handle these changes very efficiently by keeping all things and effects of that change in mind. There are different process models that tells how to handle these changes. This paper suggests different process models to handle those requirements changes. The difference between the process models and also suggest the good approach and good model to handle all these changes. Because its very important to understand, thousands of projects are flopped due to changes. In every system, a stage must come, at which you have to update your software. Some changes are come with the passage of time, and some will come immediately by the customer.