Investigating instability architectural smells evolution: an exploratory case study

Darius Sas, Paris Avgeriou, Francesca Arcelli Fontana

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

20 Citations (Scopus)
359 Downloads (Pure)

Abstract

Architectural smells may substantially increase maintenance effort and thus require extra attention for potential refactoring. While we currently understand this concept and have identified different types of such smells, we have not yet studied their evolution in depth. This is necessary to inform their prioritisation and refactoring. This study analyses the evolution of individual architectural smell instances over time, and the characteristics that define these instances. Three different types of architectural smells are taken into consideration and mined from a total of 524 versions across 14 different projects. The results show how different smell types differ in multiple aspects, such as their growth rate, the importance of the affected elements over time in the dependency network of the system, and the time each instance affects the system. They also cast valuable insights on what aspects are the most important to consider during prioritisation and refactoring activities.
Original languageEnglish
Title of host publication35th International Conference on Software Maintenance and Evolution
PublisherIEEE
Pages557-567
Number of pages11
ISBN (Electronic)9781728130941
DOIs
Publication statusPublished - 5-Dec-2019
Event35th International Conference on Software Maintenance and Evolution - Cleveland, OH, United States
Duration: 30-Sept-20194-Oct-2019

Conference

Conference35th International Conference on Software Maintenance and Evolution
Country/TerritoryUnited States
CityCleveland, OH
Period30/09/201904/10/2019

Keywords

  • architectural smells
  • technical debt
  • software architecture
  • empirical study

Fingerprint

Dive into the research topics of 'Investigating instability architectural smells evolution: an exploratory case study'. Together they form a unique fingerprint.

Cite this