Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jacob Rendall

dblp:218/5408 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2018
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 50% Empirical software engineering · 50%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › mining software repositories
commit analysis
0.312018
Traceability in the wild: automatically augmenting incomplete trace links · ICSE 2018
Software maintenance and evolution › traceability
issue-commit link recovery
0.312018
Traceability in the wild: automatically augmenting incomplete trace links · ICSE 2018
Empirical software engineering
mining software repositories
0.312018
Traceability in the wild: automatically augmenting incomplete trace links · ICSE 2018
Software maintenance and evolution
traceability
0.312018
Traceability in the wild: automatically augmenting incomplete trace links · ICSE 2018

Methods — techniques the papers use, named apart from their topics

text classification · 0.3process feature extraction · 0.3
YearPublicationVenuePosition
2018 Traceability in the wild: automatically augmenting incomplete trace links
abstract
Software and systems traceability is widely accepted as an essential element for supporting many software development tasks. Today's version control systems provide inbuilt features that allow developers to tag each commit with one or more issue ID, thereby providing the building blocks from which project-wide traceability can be established between feature requests, bug fixes, commits, source code, and specific developers. However, our analysis of six open source projects showed that on average only 60% of the commits were linked to specific issues. Without these fundamental links the entire set of project-wide links will be incomplete, and therefore not trustworthy. In this paper we address the fundamental problem of missing links between commits and issues. Our approach leverages a combination of process and text-related features characterizing issues and code changes to train a classifier to identify missing issue tags in commit messages, thereby generating the missing links. We conducted a series of experiments to evaluate our approach against six open source projects and showed that it was able to effectively recommend links for tagging issues at an average of 96% recall and 33% precision. In a related task for augmenting a set of existing trace links, the classifier returned precision at levels greater than 89% in all projects and recall of 50%.
Michael Rath 0002, Jacob Rendall, Jin L. C. Guo, Jane Cleland-Huang, Patrick Mäder
ICSE2