Cost Risks Due to changing requirements during Software Development Lifecycle

By Sumit Bhatia on July 16, 2015


The IT software development deals with various process and models to develop the software as per the initial requirements. The basic and the widely used in earlier days is Waterfall model.

The waterfall model is very rigid in accepting the changes during development due to which it becomes very unpopular these days as IT requirements changes on daily basis. With such rapid changes in the requirement, the best model to work on is either Spiral or Prototyping model, which is widely used these days.

With these two models the change in requirements from the client can be gathered very easily during development phase and revised software structure can be developed with no complexity. But with change in features, during the development phase sometimes introduces major challenges for development teams. With more complex software structure and interdependent nature of software, modules affect the functionality of other modules or sometimes software flow and thus introduce lot of bugs. The incorporation of such changes during spiral and prototype model not thus increased the development cycle of software as well as teams misses the timeline and milestones, which affects the organizations in achieving the targets.

So as per the current market scenario there should be a process, which calculates the risk, involved incorporating each and every change during the development phase of a software application. The organizations needs to audit properly the process, they follow while developing the software and risk involved in terms of missing deadlines and overhead cost in applying the requirement changes during development phase.

Sumit Bhatia


Sumit Bhatia

Director Aedifico Tech Pvt Ltd / Yash Computers