HATARI: raising risk awareness
暂无分享,去创建一个
[1] Audris Mockus,et al. Predicting risk of software changes , 2000, Bell Labs Technical Journal.
[2] Audris Mockus,et al. Identifying reasons for software changes using historic databases , 2000, Proceedings 2000 International Conference on Software Maintenance.
[3] Harald C. Gall,et al. Populating a Release History Database from version control and bug tracking systems , 2003, International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings..
[4] Gail C. Murphy,et al. Hipikat: recommending pertinent software development artifacts , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..
[5] Andreas Zeller,et al. When do changes induce fixes? , 2005, ACM SIGSOFT Softw. Eng. Notes.
[6] Thomas Zimmermann,et al. Preprocessing CVS Data for Fine-Grained Analysis , 2004, MSR.
[7] N. Nagappan,et al. Use of relative code churn measures to predict system defect density , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..
[8] Taghi M. Khoshgoftaar,et al. EMERALD: software metrics and models on the desktop , 1996, Proceedings of the Fourth International Symposium on Assessment of Software Tools.
[9] Elaine J. Weyuker,et al. Where the bugs are , 2004, ISSTA '04.
[10] Stephen G. Eick,et al. Visualizing software systems , 1994, Proceedings of 16th International Conference on Software Engineering.