Optimized Assignment of Developers for Fixing Bugs

Decisions on “Who should fix this bug” have substantial impact on the duration of the process and its results. Expertise and related productivity level of developers might vary up to one order of magnitude. This is even more the case if we acknowledge that fixing a bug typically requires expertise in a number of components. In this paper, optimized strategies for the assignment of the “right” developers for doing the “right” task are studied and the results are compared to manual (called ad hoc) assignment. The quality of assignment is measured by the match between requested (from bugs) and available (from developers) competence profile. Different variants of Greedy search with varying parameter of look-ahead time are studied. The quality of the results has been evaluated for nine milestones of the open source Eclipse JDT project. The optimized strategies with largest look ahead time are demonstrated to be substantially better than the ad hoc solutions in terms of the quality of the assignment and the number of bugs which can be fixed within the given time interval.

[1]  Lorenzo Strigini Limiting the Dangers of Intuitive Decision Making , 1996, IEEE Softw..

[2]  Gail C. Murphy,et al.  Automatic bug triage using text categorization , 2004, SEKE.

[3]  Gail C. Murphy,et al.  Coping with an open bug repository , 2005, eclipse '05.

[4]  Lyndon Hiew,et al.  Assisted Detection of Duplicate Bug Reports , 2006 .

[5]  Andreas Zeller,et al.  Predicting component failures at design time , 2006, ISESE '06.

[6]  John Anvik,et al.  Automating bug report assignment , 2006, ICSE.

[7]  Gerardo Canfora,et al.  Supporting change request assignment in open source development , 2006, SAC.

[8]  Gail C. Murphy,et al.  Who should fix this bug? , 2006, ICSE.

[9]  Natalia Juristo Juzgado,et al.  Emphasizing human capabilities in software development , 2006, IEEE Software.

[10]  Rainer Kolisch,et al.  Experimental investigation of heuristics for resource-constrained project scheduling: An update , 2006, Eur. J. Oper. Res..

[11]  Per Runeson,et al.  Detection of Duplicate Defect Reports Using Natural Language Processing , 2007, 29th International Conference on Software Engineering (ICSE'07).

[12]  Andreas Zeller,et al.  How Long Will It Take to Fix This Bug? , 2007, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007).

[13]  Andrew Smith,et al.  Optimized staffing for product releases and its application at Chartwell Technology , 2008, J. Softw. Maintenance Res. Pract..

[14]  Ajitha Rajan,et al.  Proceedings of the 30th international conference on Software engineering , 2008 .

[15]  Nicholas Jalbert,et al.  Automated duplicate detection for bug tracking systems , 2008, 2008 IEEE International Conference on Dependable Systems and Networks With FTCS and DCC (DSN).

[16]  Thomas Zimmermann,et al.  Duplicate bug reports considered harmful … really? , 2008, 2008 IEEE International Conference on Software Maintenance.

[17]  Günther Ruhe,et al.  Optimized Resource Allocation for Software Release Planning , 2009, IEEE Transactions on Software Engineering.