Requirements Volatility in Software Development Process
M. P. Singh1, Rajnish Vyas2

1Dr. M.P. Singh, Principal/Director, N.I.E.T, Alwar, Rajasthan, India
2Rajnish Vyas, Research Scholar, Singhania University, Rajasthan, India.
Manuscript received on September 01, 2012. | Revised Manuscript received on September 02, 2012. | Manuscript published on September 05, 2012. | PP: 259-264 | Volume-2 Issue-4, September 2012. | Retrieval Number: D0960082412/2012©BEIESP
Open Access | Ethics and Policies | Cite
© The Authors. Published By: Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC BY-NC-ND license (

Abstract: Changes in requirements do occur during the software development life cycle. The changes may take place from the initial design phase up to the implementation phase. These change that creep during the development process pose risk to cost and quality of the product, but at the same time provide an opportunity to add value. This paper discusses the requirement, volatility in requirements, causes of requirement volatility and then the impact of requirement volatility on Project Schedule, Project Cost, Project Performance, Software Quality and Software Maintenance. We also try to explore the positive implications (if any) of the requirement changes. The purpose of this paper is to discuss aspects related to requirement volatility. 
Keywords: Requirements change; requirements management; project management; card sorting; software evolution; development; maintenance.