The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Managing software evolution through semantic history slicing
Abstract
Software change histories are results of incremental updates made by developers. As a side-effect of the software development process, version history is a surprisingly useful source of information for understanding, maintaining and reusing software. However, traditional commit-based sequential organization of version histories lacks semantic structure and thus are insufficient for many development tasks that require high-level, semantic understanding of program functionality, such as locating feature implementations and porting hot fixes. In this work, we propose to use well-organized unit tests as identifiers for corresponding software functionalities. We then present a family of automated techniques which analyze the semantics of historical changes and assist developers in many everyday practical settings. For validation, we evaluate our approaches on a benchmark of developer-annotated version history instances obtained from real-world open source software projects on GitHub.
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
Topological sorting of large networks
Kahn, A. B. (1962) · Communications of the ACM · doi:10.1145/368996.369025 · Cited by 769
A survey on tree edit distance and related problems
Bille, P. (2005) · Theoretical Computer Science · doi:10.1016/j.tcs.2004.12.030 · Cited by 751
How We Refactor, and How We Know It
Murphy-Hill, E., Parnin, C., & Black, A. P. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.41 · Cited by 547
Using Data Fusion and Web Mining to Support Feature Location in Software
Revelle, M., Dit, B., & Poshyvanyk, D. (2010) · 2010 IEEE 18th International Conference on Program Comprehension · doi:10.1109/icpc.2010.10 · Cited by 105
Early Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82
Research works printed but not linked: 22
- 10.1109/ASE.2011.6100097 · doi:10.1109/ase.2011.6100097
- zeller, 1999, Proceedings of the ESEC/FSE09, 253
- 10.1007/978-3-662-54494-5_4 · DOI
- 10.1109/ICSE.2004.1317478 · DOI · Paper page
- 10.1109/MSR.2013.6624018 · DOI · Paper page
- 10.1109/ICSM.2012.6405336 · DOI
- 10.1109/32.536955 · DOI
- 10.1007/978-3-642-05415-0_18 · doi:10.1007/978-3-642-05415-0_18
- 10.1109/ASE.2015.53 · DOI
- 10.1145/2362536.2362558 · doi:10.1145/2362536.2362558
- kung, 1994, Proc of ICSM'94 IEEE Computer Society, 202
- arnold, 1996, Software Change Impact Analysis
- 10.1145/1028976.1029012 · DOI · Paper page
- 10.1109/ICSE.2003.1201210 · doi:10.1109/icse.2003.1201210
- 0, Apache Subversion (SVN) version control system
- 0, GIT Version Control System
- 10.1109/ICSM.2011.6080769 · DOI
- 10.1109/ASE.2015.47 · DOI
- 10.1145/2970276.2970336 · DOI
- 10.1109/TSE.2017.2664824 · DOI
- 10.1109/MSR.2017.49 · DOI
- 10.1145/3106195.3106216 · DOI
Metadata
- Authors
- Li, Y.
- Venue
- 2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE)
- Publisher
- IEEE
- Published
- 2017-10
- Pages
- 1014-1017
- Cited by
- 3
- References
- 5
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.