A study to investigate the impact of requirements instability on software defects

ABSTRACT

Software development is a dynamic process and is characterized by change. Software projects often begin with unclear, ambiguous, and incomplete requirements which give rise to intrinsic volatility. Constant change in requirements is one of the main causes of software defects and a major issue faced by the software industry. This paper describes the findings of our research-based study that investigates the impact of both the pre-release and post-release requirements changes on overall defects by defining measures, collecting data against those measures and analyzing the collected data through statistical techniques. Our findings, based on industry data from 4 software projects consisting of 30 releases, all in e-commerce domain, indicate that there is a significant relationship between pre/post release change requests initiated by the client and software defects. In addition, our data analysis indicates that changes in the design of the system at the later stages of software development i.e., during coding, testing and after release have a significant impact on the high severity defects that affect the major functionality of the system. Also, we found that insufficient time spent on the design phase and inadequate communication with the client could be some of the causes of requirements changes and consequently software defects.

REFERENCES

• 1: Axel van Lamsweerde, Requirements engineering in the year 00: a research perspective, Proceedings of the 22nd international conference on Software engineering, p.5-19, June 04-11, 2000, Limerick, Ireland [doi>10.1145/337180.337184]
• 2: Hyatt, L. and Rosenberg, L. (1996): Software Metrics for Risk Assessment. International Academy of Astronautics (IAA) 29th Safety and Rescue Symposium, Risk Management and Assessment Session, Beijing, China.
• 3: Evelyn J. Barry , Tridas Mukhopadhyay , Sandra A. Slaughter, Software Project Duration and Effort: An Empirical Study, Information Technology and Management, v.3 n.1-2, p.113-136, January 2002 [doi>10.1023/A:1013168927238]
• 4: Didar Zowghi , N Nurmuliani, A Study of the Impact of Requirements Volatility on Software Project Performance, Proceedings of the Ninth Asia-Pacific Software Engineering Conference, p.3, December 04-06, 2002
• 5: Robert B. Grady , Deborah L. Caswell, Software metrics: establishing a company-wide program, Prentice-Hall, Inc., Upper Saddle River, NJ, 1987
• 6: Stephen H. Kan, Metrics and Models in Software Quality Engineering, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2002
• 7: Capers Capers Jones, Software Quality: Analysis and Guidelines for Success, Thomson Learning, 1997
• 8: Davis, A. (1993): Identifying and Measuring Quality in Software Requirements Specifications. In Proceedings of First International Software Metrics Symposium, Baltimore, pp. 141--152.
• 9: Pfahl, D. and Lebsanft, K. (2000): "Using Simulation to analyze the impact of Software Requirements Volatility on Project Performance", Information and Software Technology, 42, pp. 1001--1008.
• 10: Alan M. Davis, The Art of Requirements Triage, Computer, v.36 n.3, p.42-49, March 2003 [doi>10.1109/MC.2003.1185216]
• 11: Bonnie Collier , Tom DeMarco , Peter Fearey, A Defined Process For Project Postmortem Review, IEEE Software, v.13 n.4, p.65-72, July 1996 [doi>10.1109/52.526833]
• 12: Matthias Weber , Joachim Weisbrod, Requirements Engineering in Automotive Development - Experiences and Challenges, Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, p.331-340, September 09-13, 2002
• 13: Roger S. Pressman, Software Engineering: A Practitioner's Approach, McGraw-Hill Higher Education, 2001
• 14: Lam, W., Shankararaman, V. and Saward, G. (1999): Requirements Change: A Dissection of Management Issues, EUROMICRO'99 Workshop on Software Process and Product Improvement, Milan, Italy, pp. 2244--2251.
• 15: Lane, M. and Cavaye, A. (1998): Management of Requirements Volatility Enhances Software Development Productivity. In proceedings of the 3rd Australian Conference on Requirements Engineering (ACRE 98), Geelong, Australia.
• 16: Start, G., Skillicorn, A. and Ameele, R. (1998): An Examination of the Effects of requirements changes on software Releases. In CROSSTALK, The Journal of Defence Software Engineering.
• 17: Yashwant K. Malaiya , Jason Denton, Requirements Volatility and Defect Density, Proceedings of the 10th International Symposium on Software Reliability Engineering, p.285, November 01-04, 1999
• 18: Harker, S., Eason, K. and Dobson, J. (1993): The change and evolution of requirements as a challenge to the practice of software engineering. In proceedings of the IEEE International Symposium on Requirements Engineering, pp. 266--272, San Diego, California, USA, IEEE Computer Society Press.
• 19: Zowghi, D., Offen, R. and Nurmuliani, N. (2000): The Impact of Requirements Volatility on Software Development Lifecycle. In proceedings of the International Conference on Software, Theory and Practice (ICS2000), Beijing, China.
• 20: Zowghi, D. and Nurmuliani, N. (1998): Investigating Requirements Volatility During Software Development: Research in Progress. In proceedings of the 3rd Australian Conference on Requirements Engineering (ACRE98), Geelong, Australia.

INDEX TERMS

Keywords:
change request (CR's)¹, defects, high/medium/low change requests, pre/post release changes, requirements change, severity-1/severity-2 defects