Research Article
Requirements Volatility in Software Maintenance
@INPROCEEDINGS{10.1007/978-3-642-27317-9_15, author={D. Kavitha and Ananthi Sheshasaayee}, title={Requirements Volatility in Software Maintenance}, proceedings={Advances in Computer Science and Information Technology. Computer Science and Information Technology. Second International Conference, CCSIT 2012, Bangalore, India, January 2-4, 2012. Proceedings, Part III}, proceedings_a={CCSIT PART III}, year={2012}, month={11}, keywords={Software maintenance requirement volatility types of requirement change reason for requirement change and sources of requirement change}, doi={10.1007/978-3-642-27317-9_15} }- D. Kavitha
Ananthi Sheshasaayee
Year: 2012
Requirements Volatility in Software Maintenance
CCSIT PART III
Springer
DOI: 10.1007/978-3-642-27317-9_15
Abstract
Requirements volatility is a common phenomenon present in most software development projects. Change Management dealing with requirement changes is an important function of project managers. If the changes are not handled effectively, then there will be huge difference in efforts, cost, and quality of the Product which results in project delay or project may be failed. Taxonomy of requirements change consists of three components: Change Type, Reason, and Sources. Changes in requirements are additions, deletion or modifications of requirements. These changes to the requirements after the basic set has been agreed to by both clients and maintainers are known as requirement’s volatility. Requirements volatility cannot be avoided, but we have to understand the requirements volatility problems to deal with the impact. In this paper we have reviewed the requirement volatility, identified the reasons and sources of changes, and introduced few guidelines to managing changes effectively.