Analysis of Refactoring Techniques and Tools for Source Code Quality Improvement

2016 ◽  
Vol 6 (4) ◽  
pp. 137-150
Author(s):  
Doohwan Kim ◽  
◽  
YooJin Jung ◽  
Jang-Eui Hong
Keyword(s):  
Quality Improvement ◽  
Source Code ◽  
Code Quality

Why Do Developers Reject Refactorings in Open-Source Projects?

2022 ◽  
Vol 31 (2) ◽  
pp. 1-23
Author(s):  
Jevgenija Pantiuchina ◽  
Bin Lin ◽  
Fiorella Zampetti ◽  
Massimiliano Di Penta ◽  
Michele Lanza ◽  
...  
Keyword(s):  
Open Source ◽  
Software Quality ◽  
Good Practice ◽  
Source Code ◽  
Code Review ◽  
Code Quality ◽  
Shed Light

Refactoring operations are behavior-preserving changes aimed at improving source code quality. While refactoring is largely considered a good practice, refactoring proposals in pull requests are often rejected after the code review. Understanding the reasons behind the rejection of refactoring contributions can shed light on how such contributions can be improved, essentially benefiting software quality. This article reports a study in which we manually coded rejection reasons inferred from 330 refactoring-related pull requests from 207 open-source Java projects. We surveyed 267 developers to assess their perceived prevalence of these identified rejection reasons, further complementing the reasons. Our study resulted in a comprehensive taxonomy consisting of 26 refactoring-related rejection reasons and 21 process-related rejection reasons. The taxonomy, accompanied with representative examples and highlighted implications, provides developers with valuable insights on how to ponder and polish their refactoring contributions, and indicates a number of directions researchers can pursue toward better refactoring recommenders.

A Framework for Measuring and Evaluating Program Source Code Quality

2007 ◽  
pp. 284-299 ◽  
Author(s):  
Hironori Washizaki ◽  
Rieko Namiki ◽  
Tomoyuki Fukuoka ◽  
Yoko Harada ◽  
Hiroyuki Watanabe
Keyword(s):  
Source Code ◽  
Code Quality

An Investigation on Quality Perspective of Software Functional Artifacts

2020 ◽  
pp. 109-133
Author(s):  
Vimaladevi M. ◽  
Zayaraz G.
Keyword(s):  
Quality Improvement ◽  
Source Code ◽  
Quality Analysis ◽  
Complex Nature ◽  
Design Development ◽  
Software Products ◽  
Intelligent Software ◽  
Software Engineering Process ◽  
Automated Technique ◽  
The Cost

Software engineering process and practices paramount the crisis of cost, quality, and schedule constraints in developing software products. This chapter surveys the quality improvement techniques for the two fundamental artifacts of software product development, namely the architecture design and the source code. The information from top level research databases are compiled and an overall picture of quality enhancement in current software trends during the design, development, and maintenance phases are presented. This helps both the software developers and the quality analysts to gain understanding of the current state of the art for quality improvement of design and source code and the usage of various practices. The results indicate the need for more realistic, precise, automated technique for architectural quality analysis. The complex nature of the current software products requires the system developed to be beyond robust and resilient and building intelligent software that is anti-fragile and self-adaptive is favored. Innovative proposals that reduce the cost and time are invited.

A Case Study Using CBR-Insight to Visualize Source Code Quality

2020 ◽  
Author(s):  
Jeremy Ludwig ◽  
Devin Cline ◽  
Aaron Novstrup
Keyword(s):  
Source Code ◽  
Code Quality

scholarly journals An Expert Judgment in Source Code Quality Research Domain—A Comparative Study between Professionals and Students

2020 ◽  
Vol 10 (20) ◽  
pp. 7088
Author(s):  
Luka Pavlič ◽  
Marjan Heričko ◽  
Tina Beranič
Keyword(s):  
Experimental Data ◽  
Software Engineering ◽  
Research Evidence ◽  
Source Code ◽  
Scientific Research ◽  
Controlled Experiments ◽  
Quality Research ◽  
Professional Responses ◽  
Code Quality ◽  
Research Domain

In scientific research, evidence is often based on empirical data. Scholars tend to rely on students as participants in experiments in order to validate their thesis. They are an obvious choice when it comes to scientific research: They are usually willing to participate and are often themselves pursuing an education in the experiment’s domain. The software engineering domain is no exception. However, readers, authors, and reviewers do sometimes question the validity of experimental data that is gathered in controlled experiments from students. This is why we will address this difficult-to-answer question: Are students a proper substitute for experienced professional engineers while performing experiments in a typical software engineering experiment. As we demonstrate in this paper, it is not a “yes or no” answer. In some aspects, students were not outperformed by professionals, but in others, students would not only give different answers compared to professionals, but their answers would also diverge. In this paper we will show and analyze the results of a controlled experiment in the source code quality domain in terms of comparing student and professional responses. We will show that authors have to be careful when employing students in experiments, especially when complex and advanced domains are addressed. However, they may be a proper substitution in cases, where non-advanced aspects are required.

Sign in / Sign up

Export Citation Format

Share Document