Background Software companies need to manage and refactor Technical Debt issues.
Therefore, it is necessary to understand if and when refactoring of Technical Debt should be …

The recognition of the need for high-quality software architecture is evident from the
increasing trend in investigating architectural smells. Detection of architectural smells is …

With the adoption of microservices architectural styles, practitioners started noticing
increasing pitfalls in managing and maintaining such architectures, with the risk of …

Architectural smells can negatively impact on different software qualities and can represent
a relevant source of architectural debt. Several architectural smells have been defined by …

Background: Various works investigated microservice anti-patterns and bad smells in the
past few years. We identified seven secondary publications that summarize these, but they …

Architecture is the set of principal design decisions about a software system. In practice, new
architectural decisions are added and existing ones reversed or modified throughout a …

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 …

Architectural technical debt can have a huge impact on software maintainability and
evolution. Hence, different architectural violations, detected as architectural smells, need to …

In large-scale software systems, error-prone or change-prone files rarely stand alone. They
are typically architecturally connected and their connections usually exhibit architecture …

Background. Architectural smells and code smells are symptoms of bad code or design that
can cause different quality problems, such as faults, technical debt, or difficulties with …