Abstract

Minimizing the impact of the requirement volatility in software development process is a critical issue for both researchers and practitioners. Requirement volatility is unavoidable; therefore we need to find correct solution to manage changing requirements. Despite having many methods and tools, that are available to manage the requirement change, we need to evolve a method that deals with the change in a way that minimizes the impact to the stakeholders. In this paper, we have proposed RVMIN framework that is incorporated in SDLC, in a way that it minimizes impact of change on the stakeholder in terms of time and cost. This framework is based on both an empirical study that we have conducted and our extensive literature review of Software Process Improvement (SPI) and Requirement Engineering (RE).

References

• www. ibm. com/developerworks/rational/library/4166. html
• The Standish Group, The CHAOS Report, 1995
• I. Jacobson, G. Booch, and J. Rumbaugh, "The Unified Process," IEEE Computer, vol. 16, pp. 96–102, 1999.
• Humphrey W. S. 1989. Managing The Software Process. SEI Series in Software Engineering, Addison-Wesley.
• Boehm Barry 1981. Software Engineering Economics. Prentice Hall.
• Somerville I. 2007. Software Engineering. Addison-Wesley.
• Ranjana Rajnish et al, "Improving Requirements Quality: An Approach to Reduce Impact of Requirements Volatility", International Journal of Emerging Technologies and Applications in Engineering Technology and Sciences (IJ-ETA-ETS) ISSN: 0974-3588
• Dr. Harsh Dev, Ranjana Rajnish and Rajnish Vyas, "Writing Quality Requirements (SRS): An Approach to Manage Requirements Volatility", Indian Journal of Computer Science and Engineering, June'2010, Vol 1, Issue 1, pg28-37, ISSN: 0976-5166
• T. Javed, M. Maqsood, and Q. Durrani, "A Study to Investigate the Impact of Requirements Instability on Software Defects", SIGSOFT Software. Eng. Notes, vol. 29(3), pp. 1 – 7, 2004.
• N. Nurmuliani, D. Zowghi, and S. Fowell, "Analysis of requirements volatility during software development life cycle," in Proceedings of the 2004 Australian Software Engineering Conference (ASWEC'04), IEEE Computer Society, 2004.
• S. Harker, K. Eason, and J. Dobson, "The Change and Evolution of Requirements as a Challenge to the Practice of Software Engineering", Proceedings of IEEE International Symposium on Requirements Engineering, (San Diego, CA, USA), pp. 266–272, 1993.
• J. Brier, L. Rapanotti, and J. Hall. 2006. Problem-Based Analysis of Organizational Change: A Real-World Example. In Proceedings of the International Workshop on Advances and Applications of Problem Frames.
• Mathisen E. , Ellingsen K. And Fallmyr T. 2009. Using Business Process Modeling to Reduce the Effects of Requirement Changes in Software Projects. 2nd International Conference on Adaptive Science & Technology.
• A. Blyth, "Modeling the business process to derive organizational requirements for information technology," SIGOIS Bull. , vol. 16(1), pp. 25–33, 1995.
• C. Ebert, "Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques," IEEE Software, vol. 23(3), pp. 19–25, 2006.
• B. Nuseibeh and S. Easterbrook. 2000. Requirements Engineering: A Roadmap. In Proceedings of the Conference on the Future of Software Engineering.
• K. Orr, "Agile Requirements: Opportunity or Oxymoron?", IEEE Software, vol. 21(3), pp. 71–73, 2004.
• S. Harker and K. Eason. 1999. The use of Scenarios for Organizational Requirements Generation. In Proceedings of the Thirty-Second Annual Hawaii International Conference on System Sciences.
• R. Kazman, G. Abowd, L. Bass, and P. Clements, "Scenario-based analysis of software architecture," IEEE Software, vol. 13(6), pp. 47–55, 1996.
• W. W. Royce, "Managing the development of large software systems. " in Proc. Wescon. , pp. 1–9, 1970.
• K. Beck, "Embracing change with extreme programming„" IEEE Computer. , pp. 70–77, 1999.