Systems must evolve to cope with new stakeholders requirements, or to fix existing
problems. These changes are complex due to several factors, including the need of …

When a system evolution is not planned, developers can take decisions that degrade the
system quality. To cope with this problem, refactoring can be applied to the source code …

Context: Architecture of a software system represents the key design decisions and therefore
its quality plays an important role to keep the software maintainable. Code smells are …

Code smells indicate possible flaws in software design, that could negatively affect system's
maintainability. Interactions among smells located in the same classes (ie, collocated …

Code smells, ie, symptoms of poor design and implementation choices applied by
programmers during the development of a software project [2], represent an important factor …

Context: software architects often decide on strategies before incorporating an asset (eg,
components) in software systems. At the same time, they are responsible for preventing …

Code smells are poor implementation choices applied by developers during software
evolution that often lead to critical flaws or failure. Much in the same way, community smells …

Code smells are poor code structures that might harm the software quality and evolution.
However, previous studies has shown that only individual occurrences of smells may not be …

Previous studies demonstrated how code smells (ie, symptoms of the presence of system
degradation) impact the software maintainability. However, few studies have investigated …

To assist maintenance and evolution teams, work needs to be done at the onset of software
development. One such facilitation is refactoring the code, making it easier to read …