Calahan Janik-Jones

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

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

Software engineering, systems software and programming languages · 2 · 1 since 2021

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
Empirical software engineering · 87% Software maintenance and evolution · 13%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › mining software repositories
developer communication analysis
0.512021
Locating Latent Design Information in Developer Discussions: A Study on Pull Requests · IEEE Trans. Software Eng. 2021
Empirical software engineering
mining software repositories
0.512021
Locating Latent Design Information in Developer Discussions: A Study on Pull Requests · IEEE Trans. Software Eng. 2021
Software maintenance and evolution
code review
0.112021
Locating Latent Design Information in Developer Discussions: A Study on Pull Requests · IEEE Trans. Software Eng. 2021

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

text classification · 0.5machine learning classifier · 0.5
YearPublicationVenuePosition
2021 Locating Latent Design Information in Developer Discussions: A Study on Pull Requests
abstract
A software system's design determines many of its properties, such as maintainability and performance. An understanding of design is needed to maintain system properties as changes to the system occur. Unfortunately, many systems do not have up-to-date design documentation and approaches that have been developed to recover design often focus on how a system works by extracting structural and behaviour information rather than information about the desired design properties, such as robustness or performance. In this paper, we explore whether it is possible to automatically locate where design is discussed in on-line developer discussions. We investigate and introduce a classifier that can locate paragraphs in pull request discussions that pertain to design with an average AUC score of 0.87. We show that this classifier, when applied to projects on which it was not trained, agrees with the identification of design points by humans with an average AUC score of 0.79. We describe how this classifier could be used as the basis of tools to improve such tasks as reviewing code and implementing new features.
Giovanni Viviani, Michalis Famelis, Xin Xia 0001, Calahan Janik-Jones, Gail C. Murphy
IEEE Trans. Software Eng.4
2018 What design topics do developers discuss?
abstract
When contributing code to a software system, developers are often confronted with the hard task of understanding and adhering to the system's design. This task is often made more difficult by the lack of explicit design information. Often, recorded design information occurs only embedded in discussions between developers. If this design information could be identified automatically and put into a form useful to developers, many development tasks could be eased, such as directing questions that arise during code review, tracking design changes that might affect desired system qualities, and helping developers understand why the code is as it is. In this paper, we take an initial step towards this goal, considering how design information appears in pull request discussions and manually categorizing 275 paragraphs from those discussions that contain design information to learn about what kinds of design topics are discussed.
Giovanni Viviani, Calahan Janik-Jones, Michalis Famelis, Xin Xia 0001, Gail C. Murphy
ICPC2