Using version control data to evaluate the impact of software tools: a case study of the Version Editor
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Software tools can improve the quality and maintainability of software, but are expensive to acquire, deploy, and maintain, especially in large organizations. We explore how to quantify the effects of a software tool once it has been deployed in a development environment. We present an effort-analysis method that derives tool usage statistics and developer actions from a project's change history (version control system) and uses a novel effort estimation algorithm to quantify the effort savings attributable to tool usage. We apply this method to assess the impact of a software tool called VE, a version-sensitive editor used in Bell Labs. VE aids software developers in coping with the rampant use of certain preprocessor directives (similar to #if/#endif in C source files). Our analysis found that developers were approximately 40 percent more productive when using VE than when using standard text editors.
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
Software Engineering Economics
Boehm, B. W. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_5 · Cited by 5,981
Cited by
Learning from Experience in Software Development: A Multilevel Analysis
Fong Boh, W., Slaughter, S. A., & Espinosa, J. A. (2007) · Management Science · doi:10.1287/mnsc.1060.0687 · Cited by 341
(2015) · doi:10.1007/s10664-013-9279-3 · Cited by 273
“Some researchers perform these studies, but rarely make quantitative comparisons of the results (see Atkins et al. 2002 for a rare example of a study that does).”
BackgroundSoftware Dependencies, Work Dependencies, and Their Impact on Failures
Cataldo, M., Mockus, A., Roberts, J. A., & Herbsleb, J. D. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.42 · Cited by 271
Self-citationUsing software trails to reconstruct the evolution of software
German, D. M. (2004) · Journal of Software Maintenance and Evolution: Research and Practice · doi:10.1002/smr.301 · Cited by 49
Song, F., Agarwal, A., & Wen, W. (2024) · arXiv · doi:10.48550/arxiv.2410.02091 · Cited by 30
Metadata
- Authors
- Atkins, D. L., Ball, T., Graves, T. L., & Mockus, A.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2002-07
- Volume
- 28
- Issue
- 7
- Pages
- 625-637
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2133494720
- Cited by
- 82
- References
- 1
- FWCI
- 8.98
- 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.