Christian Donald Newman

Christian Donald Newman

Auto-generated profile, based on publicly available information

Christian Donald Newman

Rochester Institute of Technology, Rochester, USA

Research Focus & Metrics

Academic Career Length

16Years (2011-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
23 October 2021 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
APAnthony Peruma
Anthony Peruma
SSSteven Simmons
Steven Simmons
EAEman Abdullah AlOmar
Eman Abdullah AlOmar
CNChristian D. Newman
Christian D. Newman
MMMOHAMED WIEM MKAOUER
MOHAMED WIEM MKAOUER
AOAli Ouni
Ali Ouni

15 April 2024
Verified
Conference Paper
Open access
EAEman Abdullah AlOmar
Eman Abdullah AlOmar
AVAnushkrishna Venkatakrishnan
Anushkrishna Venkatakrishnan
MMMOHAMED WIEM MKAOUER
MOHAMED WIEM MKAOUER
CNChristian Newman
Christian Newman
AOAli Ouni
Ali Ouni
Large Language Models (LLMs), like ChatGPT, have gained widespread popularity and usage in various software engineering tasks, including refactoring, testing, code review, and program comprehension. Despite recent studies delving into refactoring documentation in commit messages, issues, and code review, little is known about how developers articulate their refactoring needs when interacting with ChatGPT. In this paper, our goal is to explore conversations between developers and ChatGPT related to refactoring to better understand how developers identify areas for improvement in code and how ChatGPT addresses developers' needs. Our approach relies on text mining refactoring-related conversations from 17,913 ChatGPT prompts and responses, and investigating developers' explicit refactoring intention. Our results reveal that (1) developer-ChatGPT conversations commonly involve generic and specific terms/phrases; (2) developers often make generic refactoring requests, while ChatGPT typically includes the refactoring intention; and (3) various learning settings when prompting ChatGPT in the context of refactoring. We envision that our findings contribute to a broader understanding of the collaboration between developers and AI models.

1 December 2020 in Journal of Systems and Software
Verified
Journal Article
Closed access
CNChristian D. Newman
Christian D. Newman
RAReem S. AlSuhaibani
Reem S. AlSuhaibani
MDMichael J. Decker
Michael J. Decker
APAnthony Peruma
Anthony Peruma
DKDishant Kaushik
Dishant Kaushik
EHEmily Hill
Emily Hill

4 September 2018
Verified
Conference Paper
Open access
APAnthony Peruma
Anthony Peruma
MMMohamed Wiem Mkaouer
Mohamed Wiem Mkaouer
MDMichael J. Decker
Michael J. Decker
CNChristian D. Newman
Christian D. Newman

1 November 2020 in Journal of Systems and Software
Verified
Journal Article
Closed access
APAnthony Peruma
Anthony Peruma
MMMohamed Wiem Mkaouer
Mohamed Wiem Mkaouer
MDMichael J. Decker
Michael J. Decker
CNChristian D. Newman
Christian D. Newman

30 September 2021 in Algorithms
Verified
Journal Article
Open access
PDF file
PSPriyadarshni Suresh Sagar
Priyadarshni Suresh Sagar
EAEman Abdulah AlOmar
Eman Abdulah AlOmar
MMMOHAMED WIEM MKAOUER
MOHAMED WIEM MKAOUER
AOAli Ouni
Ali Ouni
CNChristian D. Newman
Christian D. Newman
Understanding how developers refactor their code is critical to support the design improvement process of software. This paper investigates to what extent code metrics are good indicators for predicting refactoring activity in the source code. In order to perform this, we formulated the prediction of refactoring operation types as a multi-class classification problem. Our solution relies on measuring metrics extracted from committed code changes in order to extract the corresponding features (i.e., metric variations) that better represent each class (i.e., refactoring type) in order to automatically predict, for a given commit, the method-level type of refactoring being applied, namely Move Method, Rename Method, Extract Method, Inline Method, Pull-up Method, and Push-down Method. We compared various classifiers, in terms of their prediction performance, using a dataset of 5004 commits and extracted 800 Java projects. Our main findings show that the random forest model trained with code metrics resulted in the best average accuracy of 75%. However, we detected a variation in the results per class, which means that some refactoring types are harder to detect than others.