"is it really a defect?": an empirical study on measuring and improving the process of software defect reporting

ISCAS OpenIR

	"is it really a defect?": an empirical study on measuring and improving the process of software defect reporting
	Wang Dandan; Wang Qing; Yang Ye; Li Qi; Wang Haitao; Yuan Feng
	2011
会议名称	2011 5th International Symposium on Empirical Software Engineering and Measurement, ESEM 2011
会议录名称	Proceedings - 2011 5th International Symposium on Empirical Software Engineering and Measurement, ESEM 2011
页码	434-443
会议日期	September
会议地点	Banff, AB, Canada
收录类别	EI
ISBN	9780769546049
部门归属	(1) Laboratory for Internet Software Technologies Institute of Software Chinese Academy of Sciences China; (2) Graduate University Chinese Academy of Sciences China; (3) University of Southern California United States; (4) National Fundamental Software of China Ltd. Beijing 100190 China
摘要	Testing is one of the most labor-intensive activities in software development life cycle and consumes between 30% and 50% of total development costs according to many studies. The communication gap between testers and developers that is caused by unclear or even invalid defect reporting usually makes the testing schedule delay, and contributes large amount of testing effort to rework and re-communication. Defect reporting's efficiency directly influences testing efficiency and effectiveness. From our observation and improvement practices on a software product with recent 4 increments: 1) the percentage of unclear defect reports is around 23%, but more than 82% testers, more or less, reported unclear defect reports,; 2) the percentage of invalid defect reports is around 26%, but more than 35% testers reported invalid defect reports. Improvement practices that we took on training testers on how to report defect in a clearer and more efficient way further bridged the communication gap between testers and developers, and it can reduce 15.7% unclear defect reports and 19.53% invalid defect reports, which finally led to the improvement of testing efficiency. © 2011 IEEE.; Testing is one of the most labor-intensive activities in software development life cycle and consumes between 30% and 50% of total development costs according to many studies. The communication gap between testers and developers that is caused by unclear or even invalid defect reporting usually makes the testing schedule delay, and contributes large amount of testing effort to rework and re-communication. Defect reporting's efficiency directly influences testing efficiency and effectiveness. From our observation and improvement practices on a software product with recent 4 increments: 1) the percentage of unclear defect reports is around 23%, but more than 82% testers, more or less, reported unclear defect reports,; 2) the percentage of invalid defect reports is around 26%, but more than 35% testers reported invalid defect reports. Improvement practices that we took on training testers on how to report defect in a clearer and more efficient way further bridged the communication gap between testers and developers, and it can reduce 15.7% unclear defect reports and 19.53% invalid defect reports, which finally led to the improvement of testing efficiency. © 2011 IEEE.
关键词	Communication Efficiency Personnel Training Software Design Software Testing
主办者	Microsoft Research; Alberta Innovates; Siemens; University of Calgary; RIM
语种	英语
内容类型	会议论文
URI标识	http://ir.iscas.ac.cn/handle/311060/16275
专题	中国科学院软件研究所
推荐引用方式 GB/T 7714	Wang Dandan,Wang Qing,Yang Ye,et al. "is it really a defect?": an empirical study on measuring and improving the process of software defect reporting[C],2011:434-443.