Using benchmarking to advance research: a challenge to software engineering
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Benchmarks have been used in computer science to compare the performance of computer systems, information retrieval algorithms, databases, and many other technologies. The creation and widespread use of a benchmark within a research area is frequently accompanied by rapid technical progress and community building. These observations have led us to formulate a theory of benchmarking within scientific disciplines. Based on this theory, we challenge software engineering research to become more scientific and cohesive by working as a community to define benchmarks. In support of this challenge, we present a case study of the reverse engineering community, where we have successfully used benchmarks to advance the state of research.
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
The Structure of Scientific Revolutions
Kuhn, T. S. (1996) · doi:10.7208/chicago/9780226458106.001.0001 · Cited by 7,281
Cited by
Evaluating defect prediction approaches: a benchmark and an extensive comparison
D’Ambros, M., Lanza, M., & Robbes, R. (2012) · Empirical Software Engineering · doi:10.1007/s10664-011-9173-9 · Cited by 626
A Systematic Survey of Program Comprehension through Dynamic Analysis
Cornelissen, B., Zaidman, A., van Deursen, A., Moonen, L., & Koschke, R. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.28 · Cited by 420
Benchmarking homogenization algorithms for monthly data
Venema, V. K. C., Mestre, O., Aguilar, E., Auer, I., Guijarro, J. A., Domonkos, P., Vertacnik, G., Szentimrey, T., Stepanek, P., Zahradnicek, P., et al. (2012) · Climate of the Past · doi:10.5194/cp-8-89-2012 · Cited by 368
The ManyBugs and IntroClass benchmarks for automated repair of C programs
Le Goues, C., Holtschulte, N., Smith, E. K., Brun, Y., Devanbu, P., Forrest, S., & Weimer, W. (2015) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2015.2454513 · Cited by 326
Toward Benchmarking in Catalysis Science: Best Practices, Challenges, and Opportunities
Bligaard, T., Bullock, R. M., Campbell, C. T., Chen, J. G., Gates, B. C., Gorte, R. J., Jones, C. W., Jones, W. D., Kitchin, J. R., & Scott, S. L. (2016) · ACS Catalysis · doi:10.1021/acscatal.6b00183 · Cited by 285
Improving code completion with program history
Robbes, R., & Lanza, M. (2010) · Automated Software Engineering · doi:10.1007/s10515-010-0064-x · Cited by 95
Thorne, P. W., Willett, K. M., Allan, R. J., Bojinski, S., Christy, J. R., Fox, N., Gilbert, S., Jolliffe, I., Kennedy, J. J., Kent, E., et al. (2011) · Bulletin of the American Meteorological Society · doi:10.1175/2011bams3124.1 · Cited by 76
Conference v2.0: An Uncertain Version of the OAEI Conference Benchmark
Cheatham, M., & Hitzler, P. (2014) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-11915-1_3 · Cited by 40
“addition, there are more general papers on the qualities of a good benchmark, such as “Good Benchmarks are Hard to Find” [3], “The Art of Building a Good Benchmark” [7], and “Using Benchmarking to Advance Research” [16].”
BackgroundBenchmarking as Empirical Standard in Software Engineering Research
Hasselbring, W. (2021) · Evaluation and Assessment in Software Engineering · doi:10.1145/3463274.3463361 · Cited by 40
GitBug-Java: A Reproducible Benchmark of Recent Java Bugs
Silva, A., Saavedra, N., & Monperrus, M. (2024) · Proceedings of the 21st International Conference on Mining Software Repositories · doi:10.1145/3643991.3644884 · Cited by 23
Metadata
- Authors
- Sim, S. E., Easterbrook, S., & Holt, R. C.
- Venue
- 25th International Conference on Software Engineering, 2003. Proceedings.
- Publisher
- IEEE
- Published
- 2003
- Pages
- 74-83
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W4229596932
- Cited by
- 149
- References
- 1
- FWCI
- 3.73
- 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.