Subscribe
Issue No.04 - July/August (2010 vol.27)
pp: 58-64
Hongyu Zhang , Tsinghua University, Beijing
Sunghun Kim , Hong Kong University of Science and Technology, Hong Kong
ABSTRACT
Quality control charts, especially c-charts, can help monitor software quality evolution for defects over time. c-charts of the Eclipse and Gnome systems showed that for systems experiencing active maintenance and updates, quality evolution is complicated and dynamic. The authors identify six quality evolution patterns and describe their implications. Quality assurance teams can use c-charts and patterns to monitor quality evolution and prioritize their efforts.
INDEX TERMS
maintenance management, software quality, software quality assurance, quality evolution, statistical process control, software engineering
CITATION
Hongyu Zhang, Sunghun Kim, "Monitoring Software Quality Evolution for Defects", IEEE Software, vol.27, no. 4, pp. 58-64, July/August 2010, doi:10.1109/MS.2010.66
REFERENCES
1. M. Lehman and L. Belady, Program Evolution: Processes of Software Changes, Academic Press, 1985.
2. M. Lehman and J.F. Ramil, "Software Evolution," Software Evolution and Feedback: Theory and Practice, N. Madhavji et al., eds. John Wiley & Sons, 2006, pp. 7–40.
3. S. Kim et al., "Predicting Bugs from Cached History," Proc. 29th Int'l Conf. Software Eng. (ICSE 07), IEEE CS Press, 2007, pp. 489–498.
4. S. Vaucher et al., "Tracking Design Smells: Lessons from a Study of God Classes," Proc. 16th Working Conf. Reverse Eng. (WCRE 09), IEEE CS Press, 2009, pp. 145–154.
5. E. Grant, and R. Leavenworth, Statistical Quality Control, McGraw-Hill, 1998.
6. S. Kan, Metrics and Models in Software Quality Engineering, Addison-Wesley, 2003.
7. T. Mens, J.F. Ramil, and S. Degrandsart, "The Evolution of Eclipse," Proc. 23rd Int'l Conf. Software Maintenance (ICSM 08), IEEE CS Press, 2008, pp. 386–395.