Refactoring for software architecture smells

Splicing Community and Software Architecture Smells in Agile Teams: An industrial Study

“…-agile teams have a known prowess in developing software [8,9], but nobody has addressed yet whether the organisational structures behind agile teams exhibit known community smells [5] which could be potentially corrected for further organisational improvement; (2) to what extent do community smells in agile organisational structures reflect good software quality outputs? -as a proxy to software quality we consider software architecture smells [10,11] that is, known patterns that may cause nasty software maintenance and evolution issues [11] and which may cause technical debt [12,13].…”

Understanding How Developers Identify Design Problems in Practice

“…Refactoring is defined as a program transformation intended at preserving the observable behavior of the software system while improving its internal structure (84,21). Often, refactoring operations are applied to repair deteriorated code (25), which may happen by removing design problems (22,23,24). Refactoring is a complex code transformation, which includes a type and a goal, both associated with what the developer intends to do.…”

“…A refactoring operation is a program transformation used for improving the design structure of a system (21). Thus, there is a close relation between a design problem and refactoring: while the former has a negative e ect on non-functional requirements, the latter can have a positive e ect on them (22,23,24). Indeed, refactoring is commonly applied to repair a program with deteriorated design (25).…”

Extending maintainability analysis beyond code smells

“…Along the similar lines, despite the presence of a large body of work for smell detection, the existing research has supported detection of mainly implementation and some design smells. The research on architecture smells and their detection is still in a budding stage [GPEM09,SSS16], and requires a serious attention from the community, given their importance and impact on the quality of software systems. The relationship (such as correlation and collocation) among smells at various granularities has not been explored in detail.…”

“…The term code smells is an umbrella term; depending upon the granularity, scope, and impact, code smells can be classified as implementation, design, and architecture smells [SSS16].…”