Cited by 98Software Engineering ResearchSoftware Engineering Techniques and PracticesSoftware Testing and Debugging Techniques

Improving code completion with program history

Robbes, Romain, Lanza, Michele·2010·Automated Software Engineering

Integrity signals

Registry

Crossref · 10.1007/s10515-010-0064-x

Cites

19 of 19 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Other effect size measures such as the common language effect size or A12 may slightly alter the discussion.

    “Other effect size measures such as the common language effect size [44] or A 12 [45] may slightly alter the discussion.”

    From Work fragmentation in developer interaction data (2017) · cites this paper as [44]

Cites

Flagged first, then by citations

1 of the 20 references couldn’t be matched to a known paper.

Cited by

Sorted by citations

Authors
Robbes, R., & Lanza, M.
Affiliations
  • University of Chile (CL)
  • Università della Svizzera italiana (CH)
Corresponding author
Robbes, Romain
Venue
Automated Software Engineering
Published
2010-02-12
Volume
17
Issue
2
Pages
181-212
ISSN
  • 0928-8910 (ISSN-L)
  • 1573-7535
OpenAlex
W2059556545
Cited by
95
References
20
Citations by year
2026: 1 · 2025: 7 · 2024: 8 · 2023: 10 · 2022: 5 · 2021: 6 · 2020: 4 · 2019: 3 · 2018: 5 · 2017: 8 · 2016: 6 · 2015: 10 · 2014: 6 · 2013: 7 · 2012: 7
FWCI
13.56
Type
journal article
Language
en
Open access
closed
Locations
  • Automated Software Engineering (publishedVersion)
  • Universidad de Chile (submittedVersion)
  • Open Research (University of Surrey) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
Keywords
code completion, program history, change history, completion algorithm, benchmarking, developer productivity

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