The DOI matches its Crossref record; 8 of the 8 references it cites were found in a registry or an index.
How Long Will It Take to Fix This Bug?
Abstract
Predicting the time and effort for a software problem has long been a difficult task. We present an approach that automatically predicts the fixing effort, i.e., the person-hours spent on fixing an issue. Our technique leverages existing issue tracking systems: given a new issue report, we use the Lucene framework to search for similar, earlier reports and use their average time as a prediction. Our approach thus allows for early effort estimation, helping in assigning issues and scheduling stable releases. We evaluated our approach using effort data from the JBoss project. Given a sufficient number of issues reports, our automatic predictions are close to the actual effort; for issues that are bugs, we are off by only one hour, beating naive predictions by a factor of four.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Estimating software project effort using analogies
Shepperd, M., & Schofield, C. (1997) · IEEE Transactions on Software Engineering · doi:10.1109/32.637387 · Cited by 954
Anvik, J., Hiew, L., & Murphy, G. C. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134336 · Cited by 924
Gospodnetić, O., Hatcher, E., & Cutting, D. (2005) · No Category · Cited by 604
Software development cost estimation approaches — A survey
Boehm, B., Abts, C., & Chulani, S. (2000) · Annals of Software Engineering · doi:10.1023/a:1018991717352 · Cited by 588
A simulation study of the model evaluation criterion mmre
Foss, T., Stensrud, E., Kitchenham, B., & Myrtveit, I. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1245300 · Cited by 480
What accuracy statistics really measure
Kitchenham, B. A., Pickard, L. M., MacDonell, S. G., & Shepperd, M. J. (2001) · IEE Proceedings - Software · doi:10.1049/ip-sen:20010506 · Cited by 437
Coping with an open bug repository
Anvik, J., Hiew, L., & Murphy, G. C. (2005) · Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange - eclipse '05 · doi:10.1145/1117696.1117704 · Cited by 252
Software defect association mining and defect correction effort prediction
Song, Q., Shepperd, M., Cartwright, M., & Mair, C. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.1599417 · Cited by 205
Cited by
Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., & Zimmermann, T. (2008) · Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering · doi:10.1145/1453101.1453146 · Cited by 617
Self-citationImproving bug triage with bug tossing graphs
Jeong, G., Kim, S., & Zimmermann, T. (2009) · Proceedings of the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering · doi:10.1145/1595696.1595715 · Cited by 455
Self-citationAn Empirical Study on Learning Bug-Fixing Patches in the Wild via Neural Machine Translation
Tufano, M., Watson, C., Bavota, G., Penta, M. D., White, M., & Poshyvanyk, D. (2019) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3340544 · Cited by 370
Zimmermann, T., Premraj, R., Bettenburg, N., Just, S., Schroter, A., & Weiss, C. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.63 · Cited by 337
Self-citationLe, X. B. D., Lo, D., & Le Goues, C. (2016) · 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2016.76 · Cited by 332
A systematic study of automated program repair: Fixing 55 out of 105 bugs for $8 each
Le Goues, C., Dewey-Vogt, M., Forrest, S., & Weimer, W. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227211 · Cited by 326
Hooimeijer, P., & Weimer, W. (2007) · Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering · doi:10.1145/1321631.1321639 · Cited by 317
It's not a bug, it's a feature: How misclassification impacts bug prediction
Herzig, K., Just, S., & Zeller, A. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606585 · Cited by 294
Self-citationReducing the effort of bug report triage: Recommenders for development-oriented decisions
Anvik, J., & Murphy, G. C. (2011) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2000791.2000794 · Cited by 281
Automated duplicate detection for bug tracking systems
Jalbert, N., & Weimer, W. (2008) · 2008 IEEE International Conference on Dependable Systems and Networks With FTCS and DCC (DSN) · doi:10.1109/dsn.2008.4630070 · Cited by 279
Duplicate bug reports considered harmful … really?
Bettenburg, N., Premraj, R., Zimmermann, T., & Kim, S. (2008) · 2008 IEEE International Conference on Software Maintenance · doi:10.1109/icsm.2008.4658082 · Cited by 278
Self-citationCharacterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows
Guo, P. J., Zimmermann, T., Nagappan, N., & Murphy, B. (2010) · Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1 · doi:10.1145/1806799.1806871 · Cited by 265
Self-citationBoa: A language and infrastructure for analyzing ultra-large-scale software repositories
Dyer, R., Nguyen, H. A., Rajan, H., & Nguyen, T. N. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606588 · Cited by 255
Code review quality: how developers see it
Kononenko, O., Baysal, O., & Godfrey, M. W. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884840 · Cited by 183
Impact analysis of change requests on source code based on interaction and commit histories
Zanjani, M. B., Swartzendruber, G., & Kagdi, H. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597096 · Cited by 47
Software estimation: towards prescriptive analytics
Pospieszny, P. (2017) · Proceedings of the 27th International Workshop on Software Measurement and 12th International Conference on Software Process and Product Measurement · doi:10.1145/3143434.3143459 · Cited by 14
Metadata
- Authors
- Weiss, C., Premraj, R., Zimmermann, T., & Zeller, A.
- Venue
- Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)
- Publisher
- IEEE
- Published
- 2007-05
- Pages
- 1-1
- OpenAlex
- W2139410856
- Cited by
- 375
- References
- 8
- FWCI
- 13.33
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.