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 …

Context: The interest in the intersection between cloud computing and sustainability is
naturally growing as the popularity of the former makes it in many cases the default model …

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 …

Architectural technical debt in software-intensive systems is a metaphor used to describe the
“big” design decisions (eg, choices regarding structure, frameworks, technologies …

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 …

Background: Using a microservices architecture is a popular strategy for software
organizations to deliver value to their customers fast and continuously. However, scientific …

Architectural technical debt in a software-intensive system is driven by design decisions
about its structure, frameworks, technologies, languages, etc. Unlike code-level technical …

The metaphor of “technical debt” is used in software engineering to describe technical
solutions that may be pragmatic in the near‐term but may have a negative long‐term impact …

Architectural smells (AS) are notorious for their long-term impact on the Maintainability and
Evolvability of software systems. The majority of research work has investigated this topic by …

Given the current transformative potential of research that sits at the intersection of Deep
Learning (DL) and Software Engineering (SE), an NSF-sponsored community workshop was …