|
[1] J. Anvik. Automating Bug Report Assignment. In Proc. ICSE 2006, May 2006, pp. 937-940. [2] J. Anvik, L. Hiew and G. C. Murphy. Who Should Fix This Bug? In Proc. ICSE 2006, May 2006, pp. 361-370. [3] N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj and T. Zimmermann. What Makes a Good Bug Report? In Proc. ACM SIGSOFT 2008/FSE-16, November 2008, pp. 308-318. [4] G. Canfora and L. Cerulo. Where is Bug Resolution Knowledge Stored? In Proc. MSR 2006, May 2006, pp. 183-184. [5] Extreme Programming, June 2008. http://www.extremeprogramming.org/. [6] Hibernate, June 2008. http://www.hibernate.org/. [7] JIRA, June 2008. http://www.atlassian.com/software/jira/. [8] B. Kenmei, G. Antoniol and M. Di Penta. Trend Analysis and Issue Prediction in Large-Scale Open Source Systems. In Proc. CSMR 2008, April 2008, pp. 73-82. [9] C. Prause, M. Scholten, A. Zimmermann, R. Reiners and Markus Eisenhauer. Managing the Iterative Requirements Process in a Multi-National Project using an Issue Tracker. In Proc. IEEE ICGSE 2008, August 2008, pp. 151-159. [10] Spring, June 2008. http://www.springsource.org/. [11] M. Storey, J. Ryall, R. Bull, D. Myers and J. Singer. TODO or To Bug: Exploring How Task Annotations Play a Role in the Work Practices of Software Developers. In Proc. ICSE 2008, May 2008, pp. 252-260. [12] Struts, June 2008. http://struts.apache.org/. [13] D. Wahyudin, A. Schatten, D. Winkler, A. Tjoa and S. Biffl. Defect Prediction using Combined Product and Project Metrics: A Case Study from the Open Source Apache MyFaces Project Family. 34th Euromicro Conference Software Engineering and Advanced Applications, September 2008, pp. 207-215. [14] WebWork, June 2008. http://opensymphony.com. [15] C. Weiß, R. Premraj, T. Zimmermann and A. Zeller. How Long will it Take to Fix This Bug? In Proc. MSR 2007, May 2007, pp. 1-10. [16] XPlanner, June 2008. http://www.xplanner.org/. [17] A. Zeller. Why Programs Fail. Morgan Kaufmann, 2005.
|