Code smells indicate problems in design or code which makes software hard to change and
maintain. It has become a sign of software systems that cause complications in maintaining …

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 …

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 …

Software maintenance is an expensive activity that consumes a major portion of the cost of
the total project. Various activities carried out during maintenance include the addition of …

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 …

Context: Code smells are assumed to indicate bad design that leads to less maintainable
code. However, this assumption has not been investigated in controlled studies with …

Antipatterns are poor design choices that are conjectured to make object-oriented systems
harder to maintain. We investigate the impact of antipatterns on classes in object-oriented …

Code smells are a well-known metaphor to describe symptoms of code decay or other
issues with code quality which can lead to a variety of maintenance problems. Even though …

Code smells are manifestations of design flaws that can degrade code maintainability. As
such, the existence of code smells seems an ideal indicator for maintainability assessments …

Code smells are indicators of issues with source code quality that may hinder evolution.
While previous studies mainly focused on the effects of individual code smells on …