An Initial Study on the Association Between Architectural Smells and Degradation

Herold, Sebastian

doi:10.1007/978-3-030-58923-3_13

Cited by 10 publications

(4 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…JabRef is a mature and active project created in 2003 (migrated to GitHub in 2014), with 15.7k commits, 42 releases, 337 contributors, 2.7k closed issues, and 4.1k closed pull requests. JabRef has also been frequently investigated in scientific studies [32,33,34,35,36]. We chose JabRef as our case study because of these characteristics and because we have access to the project's contributors.…”

Section: Methodsmentioning

confidence: 99%

Can I Solve it? Identifying the APIs required to complete OSS tasks

2021

View full text Add to dashboard Cite

Open Source Software projects add labels to open issues to help contributors choose tasks. However, manually labeling issues is time-consuming and error-prone. Current automatic approaches for creating labels are mostly limited to classifying issues as a bug/non-bug. In this paper, we investigate the feasibility and relevance of labeling issues with the domain of the APIs required to complete the tasks. We leverage the issues' description and the project history to build prediction models, which resulted in precision up to 82% and recall up to 97.8%. We also ran a user study (n=74) to assess these labels' relevancy to potential contributors. The results show that the labels were useful to participants in choosing tasks, and the API-domain labels were selected more often than the existing architecturebased labels. Our results can inspire the creation of tools to automatically label issues, helping developers to find tasks that better match their skills.

show abstract

Section: Methodsmentioning

confidence: 99%

Can I Solve it? Identifying the APIs required to complete OSS tasks

2021

View full text Add to dashboard Cite

show abstract

“…As an indicator of potential architectural problems, 11 this metaphor has been used to pinpoint refactoring opportunities for evolving software architecture, 8,12 including microservice boundaries. Various topics pertinent to AS have been explored, for example, defining and cataloging ASes, 35‐38 detecting ASes, 14,19‐21,36,39 and empirically studying ASes 40‐43 . In particular, in defining and cataloging ASes, Garcia et al 35 introduced the notion of AS and described four representative ASes that emerged in two industrial systems, namely Connector Envy , Scattered Parasitic Functionality , Ambiguous Interfaces , and Extraneous Adjacent Connector .…”

Section: Background and Related Workmentioning

confidence: 99%

“…Sultana et al 42 explored the relationship between ASes and security weaknesses with regard to software vulnerabilities and found no significant relationship between them. Herold et al 43 studied in a single system the association between three ASes and the existence of architecture‐violating dependencies, and observed that Cyclic Dependency and Unstable Dependency have a larger risk of including architectural violations.…”

Section: Background and Related Workmentioning

confidence: 99%

Impacts, causes, and solutions of architectural smells in microservices: An industrial investigation

et al. 2022

View full text Add to dashboard Cite

As a recently predominant architecture style, MicroService Architecture (MSA) is likely to suffer the issues of poor maintainability due to inappropriate microservice boundaries. Architectural Smell (AS), as a metaphor for potential architectural issues that may have negative impacts on software maintenance, can be used to pinpoint refactoring opportunity for evolving microservice boundary. However, existing studies mostly focus on AS detection with little further investigation on the possible impacts, causes, and solutions of AS, which does little help in addressing the bad smells in architecture. Our goal in this study is to bridge this gap by investigating the possible impacts, causes, and solutions of AS in MSA-based systems. An industrial case study is carried out to collect repository data and practitioners' views on six typical ASes in a real MSA-based telecommunication system. Statistical Analysis and Coding techniques are used in the analyses of quantitative and qualitative data respectively.The results show that AS influences the modularity, modifiability, analyzability, and testability of the MSA-based system, which further induce extra cross-team communication, change-and fault-prone microservices. To explore the causes for AS, a five-aspect conceptual classification with technology, project, organization, business, and professional is proposed, in which the business and organization aspects take the major roles. Both technical and non-technical solutions are distilled to deal with ASes despite potential constraints. These results and their comparison to current literature are discussed, which provide practical implications in coping with AS in microservices.

show abstract

“…In the past decades, a wide variety of studies are concerned with the architecture erosion phenomenon, which has been extensively discussed and described with various terms Avgeriou, 2021b, 2022), such as architecture decay (Hassaine et al, 2012;Le et al, 2018), degradation (Lenhard et al, 2019;Herold, 2020), degeneration (Hochstein and Lindvall, 2005).…”

Section: Architecture Erosion and Related Symptomsmentioning

confidence: 99%

Understanding, Analysis, and Handling of Software Architecture Erosion

View full text Add to dashboard Cite

Architecture erosion reflects the tendency of an implemented architecture of a software system to gradually diverge from the intended architecture. Empirical evidence from numerous studies has demonstrated that architecture erosion significantly impacts various aspects of software development, maintenance, and evolution. This is because, architecture erosion often tends to occur imperceptibly and accumulates over time, making its repair challenging, costly, and sometimes even impossible. Therefore, timely detection and remediation of architecture erosion become crucial.One way to manage architecture erosion is by identifying its early symptoms, such as lack of modularity and various architectural smells. By identifying and managing these symptoms and their evolution, developers can gain insights into the software system's health and take proactive measures like architecture refactoring. This early warning mechanism not only aids in repairing eroded architecture, but also helps in understanding, identifying, analyzing, and optimizing software architecture, ultimately improving software product quality. However, despite several research studies investigating the architecture erosion phenomenon, the current state of the art has certain shortcomings. Specifically, there is a lack of comprehensive understanding of the nature of architecture erosion, it is unclear which symptoms of architecture erosion are the most common, and there is a lack of effective methods to identify these symptoms. Hence, the main research objective of this thesis is to establish a landscape of architecture erosion, investigate common erosion symptoms, and propose feasible approaches to identify and handle architecture erosion.To achieve the stated objective, we first need to obtain a landscape of the architecture erosion phenomenon and its current state of research in the literature. To this end, we conducted a systematic mapping study that covers the literature spanning te meten. Door middel van een reeks experimenten hebben we deze methoden afzonderlijk geëvalueerd en vergeleken met de basisbenadering (RevFinder). De resultaten toonden aan dat de gangbare gelijkenisdetectiemethoden acceptabele prestatiescores vertoonden en RevFinder overtroffen bij het aanbevelen van code reviewers voor architectuurschendingen. Bovendien ontdekten we dat de samplingtechnieken die worden gebruikt bij het aanbevelen van code reviewers, invloed hebben op de prestaties van reviewer aanbevelingsbenaderingen.

show abstract

An Initial Study on the Association Between Architectural Smells and Degradation

Cited by 10 publications

References 16 publications

Can I Solve it? Identifying the APIs required to complete OSS tasks

Can I Solve it? Identifying the APIs required to complete OSS tasks

Impacts, causes, and solutions of architectural smells in microservices: An industrial investigation

Understanding, Analysis, and Handling of Software Architecture Erosion

Contact Info

Product

Resources

About