Abstract:

In this very competitive software industry, many software managers tend to agree on the software project, without having the full knowledge of the project and what are its requirements. They failed to access what it needed to be built exactly and bid for the software project. They agree on software project by just having a rough idea. They allow using this approach for every new project because they want to get more and more clients, and get settle in this competitive market. The software firm mostly concern about making profit by delivering as many as projects possible in the short span of time. The main focus of this paper will be telling on how the software success and quality get affected, when requirements gets changed or fresh requirements comes during the software development life cycle(SDLC). What happens to the software development team when they have to do a lot of work in limited span of time and financial plan. There can be negative impacts in the life of developer if they do work for long hours for most of their time. This also leave a bad image of the company in the views of customers, as well as for current employees and future potential employees. It should be noted that efforts to reduce change requests is necessary in every project because it has an important factor in determining the project outcomes. It also reduces the effort of rework and save a lot of time and energy working on change requests. It has also been noted that many software projects have failed because of defects in software requirements phase.