Refactoring and smells have been well researched by the software-engineering research
community these past decades. Several secondary studies have been published on code …

Background: Code smells indicate suboptimal design or implementation choices in the
source code that often lead it to be more change-and fault-prone. Researchers defined …

Code smells were defined as symptoms of poor design choices applied by programmers
during the development of a software project [2]. They might hinder the comprehensibility …

Code smells are symptoms of poor design and implementation choices weighing heavily on
the quality of produced source code. During the last decades several code smell detection …

Several code smell detection tools have been developed providing different results,
because smells can be subjectively interpreted, and hence detected, in different ways. In this …

Context Smells in software systems impair software quality and make them hard to maintain
and evolve. The software engineering community has explored various dimensions …

Technical debt is a metaphor introduced by Cunningham to indicate “not quite right code
which we postpone making it right”. One noticeable symptom of technical debt is …

Co** with evolution in automated production systems implies a cross-disciplinary
challenge along the system's life-cycle for variant-rich systems of high complexity. The …

In past and recent years, the issues related to managing technical debt received significant
attention by researchers from both industry and academia. There are several factors that …

The metaphor of technical debt was introduced to express the trade off between productivity
and quality, ie, when developers take shortcuts or perform quick hacks. More recently, our …