The quality of a software system is mostly defined by its source code. Software evolves
continuously, it gets modified, enhanced, and new requirements always arise. If we do not …

Software systems undergo modifications, improvements and enhancements to cope with
evolving requirements. This maintenance can cause their quality to decrease. Various …

It is very common in various fields that there is a gap between theoretical results and their
practical applications. This is true for code refactoring as well, which has a solid theoretical …

Refactoring has been widely used to improve software design. Refactoring is applied when
a bad smell is detected. Several bad smells might be present in the code. In this paper, we …

Methods and tools for refactoring of software have been extensively studied during the last
decades, and we argue that there is now a need for additional studies of the effects of …

Refactoring aims at improving the internal structure of a software system without changing its
external behavior. Previous studies empirically assessed, on the one hand, the benefits of …

Refactoring is often treated as the main remedy against the unavoidable code erosion
happening during software evolution. Studies show that refactoring is indeed an elemental …

Refactorings are behavior-preserving source code transformations. While tool support exists
for (semi) automatically identifying refactoring solutions, applying or not a recommended …

Refactorings are-as defined by Fowler-behavior preserving source code transformations.
Their main purpose is to improve maintainability or comprehensibility, or also reduce the …

Refactoring is one of the means of managing technical debt and maintaining a healthy
software structure through enforcing best design practices, or coping with design defects …