Proceedings of the 28th international conference on Software engineering
Predicting component failures at design time
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
How Long Will It Take to Fix This Bug?
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Optimized staffing for product releases and its application at Chartwell Technology
Journal of Software Maintenance and Evolution: Research and Practice - Search Based Software Engineering [SBSE]
Evaluation of optimized staffing for feature development and bug fixing
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Fuzzy set-based automatic bug triaging (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Selecting discriminating terms for bug assignment: a formal analysis
Proceedings of the 7th International Conference on Predictive Models in Software Engineering
Fuzzy set and cache-based approach for bug triaging
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
WhoseFault: automatic developer-to-fault assignment through fault localization
Proceedings of the 34th International Conference on Software Engineering
Towards understanding software change request assignment: a survey with practitioners
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Bug report assignee recommendation using activity profiles
Proceedings of the 10th Working Conference on Mining Software Repositories
Topic-based, time-aware bug assignment
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
Decisions on “Who should fix this bug” have substantial impact on the duration of the process and its results. 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.