Impact analysis of change requests on source code based on interaction and commit histories
Abstract
The paper presents an approach to perform impact analysis (IA) of an incoming change request on source code. The approach is based on a combination of interaction (e.g., Mylyn) and commit (e.g., CVS) histories. The source code entities (i.e., files and methods) that were interacted or changed in the resolution of past change requests (e.g., bug fixes) were used. Information retrieval, machine learning, and lightweight source code analysis techniques were employed to form a corpus from these source code entities. Additionally, the corpus was augmented with the textual descriptions of the previously resolved change requests and their associated commit messages. Given a textual description of a change request, this corpus is queried to obtain a ranked list of relevant source code entities that are most likely change prone. Such an approach that combines information from interactions and commits for IA at the change request level was not previously investigated. Furthermore, the approach requires only the entities that were interacted and/or committed in the past, which differs from the previous solutions that require indexing of a complete snapshot (e.g., a release).
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Cited by
Sorted by citations
Work fragmentation in developer interaction data
Cruz, L. C., Sanchez, H., González, V. M., & Robbes, R. (2017) · Journal of Software: Evolution and Process · doi:10.1002/smr.1839 · Cited by 6 · see citing works
- Authors
- Zanjani, M. B., Swartzendruber, G., & Kagdi, H.
- Affiliations
- Wichita State University (US)
- Venue
- Proceedings of the 11th Working Conference on Mining Software Repositories
- Publisher
- ACM
- Published
- 2014-05-31
- Pages
- 162-171
- OpenAlex
- W2086106475
- Cited by
- 47
- References
- 0
- Citations by year
- 2024: 1 · 2023: 1 · 2022: 2 · 2021: 3 · 2020: 2 · 2019: 4 · 2018: 4 · 2017: 18 · 2016: 6 · 2015: 6
- FWCI
- 8.53
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- International Conference on Mining Software Repositories (MSR) (publishedVersion)
- 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
- impact analysis, change requests, source code, interaction history, commit history, CVS, bug fixes, information retrieval, commit messages
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