Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Proceedings of the 28th international conference on Software engineering
Fine grained indexing of software repositories to support impact analysis
Proceedings of the 2006 international workshop on Mining software repositories
Supporting change request assignment in open source development
Proceedings of the 2006 ACM symposium on Applied computing
A Linguistic Analysis of How People Describe Software Problems
VLHCC '06 Proceedings of the Visual Languages and Human-Centric Computing
Detection of Duplicate Defect Reports Using Natural Language Processing
ICSE '07 Proceedings of the 29th international conference on Software Engineering
How Long Will It Take to Fix This Bug?
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Predicting Eclipse Bug Lifetimes
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Which warnings should I fix first?
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Predicting accurate and actionable static analysis warnings: an experimental approach
Proceedings of the 30th international conference on Software engineering
An approach to detecting duplicate bug reports using natural language and execution information
Proceedings of the 30th international conference on Software engineering
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Towards a simplification of the bug report form in eclipse
Proceedings of the 2008 international working conference on Mining software repositories
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Is it a bug or an enhancement?: a text-based approach to classify change requests
CASCON '08 Proceedings of the 2008 conference of the center for advanced studies on collaborative research: meeting of minds
Towards the next generation of bug tracking systems
VLHCC '08 Proceedings of the 2008 IEEE Symposium on Visual Languages and Human-Centric Computing
The secret life of bugs: Going past the errors and omissions in software repositories
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Does distributed development affect software quality? An empirical case study of Windows Vista
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Improving bug triage with bug tossing graphs
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Fair and balanced?: bias in bug-fix datasets
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Software debugging, testing, and verification
IBM Systems Journal
Information needs in bug reports: improving cooperation between developers and users
Proceedings of the 2010 ACM conference on Computer supported cooperative work
Linux kernel developer responses to static analysis bug reports
USENIX'09 Proceedings of the 2009 conference on USENIX Annual technical conference
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
ACM Transactions on Software Engineering and Methodology (TOSEM)
Empirical software engineering at Microsoft Research
Proceedings of the ACM 2011 conference on Computer supported cooperative work
"Not my bug!" and other reasons for software bug report reassignments
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Empirical evaluation of reliability improvement in an evolving software product line
Proceedings of the 8th Working Conference on Mining Software Repositories
Bug-fix time prediction models: can we do better?
Proceedings of the 8th Working Conference on Mining Software Repositories
Using automatic persistent memoization to facilitate data analysis scripting
Proceedings of the 2011 International Symposium on Software Testing and Analysis
Are change metrics good predictors for an evolving software product line?
Proceedings of the 7th International Conference on Predictive Models in Software Engineering
Empirical validation of human factors in predicting issue lead time in open source projects
Proceedings of the 7th International Conference on Predictive Models in Software Engineering
Who tested my software? Testing as an organizationally cross-cutting activity
Software Quality Control
Developer prioritization in bug repositories
Proceedings of the 34th International Conference on Software Engineering
Characterizing and predicting which bugs get reopened
Proceedings of the 34th International Conference on Software Engineering
Factors characterizing reopened issues: a case study
Proceedings of the 8th International Conference on Predictive Models in Software Engineering
Issue ownership activity in two large software projects
ACM SIGSOFT Software Engineering Notes
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Studying the impact of social interactions on software quality
Empirical Software Engineering
Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers
International Journal of Open Source Software and Processes
It's not a bug, it's a feature: how misclassification impacts bug prediction
Proceedings of the 2013 International Conference on Software Engineering
Categorizing bugs with social networks: a case study on four open source software communities
Proceedings of the 2013 International Conference on Software Engineering
Predicting bug-fixing time: an empirical study of commercial software projects
Proceedings of the 2013 International Conference on Software Engineering
Will my patch make it? and how fast?: case study on the Linux kernel
Proceedings of the 10th Working Conference on Mining Software Repositories
Bug resolution catalysts: identifying essential non-committers from bug repositories
Proceedings of the 10th Working Conference on Mining Software Repositories
The economics of static analysis tools
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
International Journal of Open Source Software and Processes
Topic-based, time-aware bug assignment
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
We performed an empirical study to characterize factors that affect which bugs get fixed in Windows Vista and Windows 7, focusing on factors related to bug report edits and relationships between people involved in handling the bug. We found that bugs reported by people with better reputations were more likely to get fixed, as were bugs handled by people on the same team and working in geographical proximity. We reinforce these quantitative results with survey feedback from 358 Microsoft employees who were involved in Windows bugs. Survey respondents also mentioned additional qualitative influences on bug fixing, such as the importance of seniority and interpersonal skills of the bug reporter. Informed by these findings, we built a statistical model to predict the probability that a new bug will be fixed (the first known one, to the best of our knowledge). We trained it on Windows Vista bugs and got a precision of 68% and recall of 64% when predicting Windows 7 bug fixes. Engineers could use such a model to prioritize bugs during triage, to estimate developer workloads, and to decide which bugs should be closed or migrated to future product versions.