The DOI matches its Crossref record; 19 of the 19 references it cites were found in a registry or an index.
Mining version histories to guide software changes
Abstract
We apply data mining to version histories in order to guide programmers along related changes: "Programmers who changed these functions also changed...." Given a set of existing changes, the mined association rules 1) suggest and predict likely further changes, 2) show up item coupling that is undetectable by program analysis, and 3) can prevent errors due to incomplete changes. After an initial change, our ROSE prototype can correctly predict further locations to be changed; the best predictive power is obtained for changes to existing software. In our evaluation based on the history of eight popular open source projects, ROSE's topmost three suggestions contained a correct location with a likelihood of more than 70 percent.
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
Fast algorithms for mining association rules
Agrawal, R., & Srikant, R. (1998) · Cited by 11,307
Fast Algorithms for Mining Association Rules in Large Databases
Agrawal, R., & Srikant, R. (1994) · Very Large Data Bases · Cited by 9,419
Mining generalized association rules
Srikant, R., & Agrawal, R. (1997) · Future Generation Computer Systems · doi:10.1016/s0167-739x(97)00019-8 · Cited by 1,618
Śliwerski, J., Zimmermann, T., & Zeller, A. (2005) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/1082983.1083147 · Cited by 805
Self-citationMining association rules with item constraints
Srikant, R., Vu, Q., & Agrawal, R. (1997) · Cited by 766
Predicting fault incidence using software change history
Graves, T. L., Karr, A. F., Marron, J. S., & Siy, H. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.859533 · Cited by 753
Predicting source code changes by mining change history
Ying, A. T. T., Murphy, G. C., Ng, R., & Chu-Carroll, M. C. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.52 · Cited by 571
Identifying reasons for software changes using historic databases
Mockus, & Votta (2000) · Proceedings 2000 International Conference on Software Maintenance · doi:10.1109/icsm.2000.883028 · Cited by 472
Detection of logical coupling based on product release history
Gall, H., Hajek, K., & Jazayeri, M. (2002) · Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272) · doi:10.1109/icsm.1998.738508 · Cited by 447
Śliwerski, J., Zimmermann, T., & Zeller, A. (2005) · Proceedings of the 2005 international workshop on Mining software repositories - MSR '05 · doi:10.1145/1083142.1083147 · Cited by 395
Self-citationHipikat: recommending pertinent software development artifacts
Čubranić, D., & Murphy, G. C. (2003) · doi:10.5555/776816.776866 · Cited by 317
CVS release history data for detecting logical couplings
Gall, H., Jazayeri, M., & Krajewski, J. (2004) · Sixth International Workshop on Principles of Software Evolution, 2003. Proceedings. · doi:10.1109/iwpse.2003.1231205 · Cited by 291
Preprocessing CVS data for fine-grained analysis
Zimmermann, T. (2004) · "International Workshop on Mining Software Repositories (MSR 2004)" W17S Workshop - 26th International Conference on Software Engineering · doi:10.1049/ic:20040466 · Cited by 214
Self-citationHipikat: recommending pertinent software development artifacts
Cubranic, D., & Murphy, G. C. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201219 · Cited by 174
Software evolution observations based on product release history
Gall, H. C., Jazayeri, M., KLÖSCH, R. R., & Trausmuth, G. (1997) · International Conference on Software Maintenance · doi:10.1109/icsm.1997.624242 · Cited by 150
Raghavan, V. V., Grosky, W. I., Wu, Z., & Gudivada, V. N. (2004) · Chapman & Hall/CRC computer and information science series · doi:10.1201/9780203507223.pt2 · Cited by 89
Mining the maintenance history of a legacy software system
Shirabad, J. S., Lethbridge, T. C., & Matwin, S. (2004) · International Conference on Software Maintenance · doi:10.1109/icsm.2003.1235410 · Cited by 86
Detecting and Visualizing Refactorings from Software Archives
Görg, C., & Weißgerber, P. (2005) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/wpc.2005.18 · Cited by 49
Data-mining in Support of Detecting Class Co-evolution.
Xing, Z., & Stroulia, E. (2004) · Cited by 29
Cited by
Mining metrics to predict component failures
Nagappan, N., Ball, T., & Zeller, A. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134349 · Cited by 782
Self-citationThe promises and perils of mining GitHub
Kalliamvakou, E., Gousios, G., Blincoe, K., Singer, L., German, D. M., & Damian, D. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597074 · Cited by 770
Classifying Software Changes: Clean or Buggy?
Kim, S., Whitehead, & Zhang, Y. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.70773 · Cited by 672
Change Distilling:Tree Differencing for Fine-Grained Source Code Change Extraction
Fluri, B., Wursch, M., PInzger, M., & Gall, H. (2007) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.70731 · Cited by 607
Predicting Faults from Cached History
Kim, S., Zimmermann, T., Whitehead Jr., E. J., & Zeller, A. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.66 · Cited by 486
Self-citation
Metadata
- Authors
- Zimmermann, T., Zeller, A., Weissgerber, P., & Diehl, S.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2005-06
- Volume
- 31
- Issue
- 6
- Pages
- 429-445
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- 2326-3881
- OpenAlex
- W2141558501
- Cited by
- 856
- References
- 19
- FWCI
- 170.21
- Type
- journal article
- 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.