Architecture information communication in two OSS projects: The why, who, when, and what

Bi, Tingting; Ding, Wei; Liang, Peng; Tang, Antony

doi:10.1016/j.jss.2021.111035

Cited by 9 publications

(5 citation statements)

References 52 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This indicates that fewer erosion symptoms were discussed during the code review process; as the two projects get mature and stable over time, so does their architecture. This is similar to the findings of Bi et al [38], who established that architectural discussions and changes decrease after several stable releases. One possible reason is that the architecture of the two projects tends to become stable after several major versions were released.…”

Section: B Rq2: Trend Of Identified Erosion Symptomssupporting

confidence: 92%

Symptoms of Architecture Erosion in Code Reviews: A Study of Two OpenStack Projects

Soliman

Liang

et al. 2022

2022 IEEE 19th International Conference on Software Architecture (ICSA)

Self Cite

View full text Add to dashboard Cite

The phenomenon of architecture erosion can negatively impact the maintenance and evolution of software systems, and manifest in a variety of symptoms during software development. While erosion is often considered rather late, its symptoms can act as early warnings to software developers, if detected in time. In addition to static source code analysis, code reviews can be a source of detecting erosion symptoms and subsequently taking action. In this study, we investigate the erosion symptoms discussed in code reviews, as well as their trends, and the actions taken by developers. Specifically, we conducted an empirical study with the two most active Open Source Software (OSS) projects in the OpenStack community (i.e., Nova and Neutron). We manually checked 21,274 code review comments retrieved by keyword search and random selection, and identified 502 code review comments (from 472 discussion threads) that discuss erosion. Our findings show that (1) the proportion of erosion symptoms is rather low, yet notable in code reviews and the most frequently identified erosion symptoms are architectural violation, duplicate functionality, and cyclic dependency; (2) the declining trend of the identified erosion symptoms in the two OSS projects indicates that the architecture tends to stabilize over time; and (3) most code reviews that identify erosion symptoms have a positive impact on removing erosion symptoms, but a few symptoms still remain and are ignored by developers. The results suggest that (1) code review provides a practical way to reduce erosion symptoms; and (2) analyzing the trend of erosion symptoms can help get an insight about the erosion status of software systems, and subsequently avoid the potential risk of architecture erosion.

show abstract

Section: B Rq2: Trend Of Identified Erosion Symptomssupporting

confidence: 92%

Symptoms of Architecture Erosion in Code Reviews: A Study of Two OpenStack Projects

Soliman

Liang

et al. 2022

2022 IEEE 19th International Conference on Software Architecture (ICSA)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Symptoms of architecture erosion in code reviews: A study of two OpenStack projects symptoms were discussed during the code review process; as the two projects get mature and stable over time, so does their architecture. This is similar to the findings of Bi et al (Bi et al, 2021), who established that architectural discussions and changes decrease after several stable releases. One possible reason is that the architecture of the two projects tends to become stable after several major versions were released.…”

Section: Rq2: Trend Of Identified Erosion Symptomssupporting

confidence: 92%

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

“…Making Information Architecture. Contains a database as a datastore from the application system (Bi et al, 2021). The database in its storage should not have duplication, and database relations are also made to be efficient in save and load operations.…”

Section: Methodology Explanationmentioning

confidence: 99%

Sustainability of Implementing Enterprise Architecture in the Solar Power Generation Manufacturing Industry

Hindarto

Indrajit

Dazki

2021

SinkrOn

View full text Add to dashboard Cite

In recent years, Solar power plants are currently developed rapidly, where solar power plants don't cause environmental damage. This generator utilizes sunlight as its input source which environmentally friendly, when sunlight is converted into direct current and voltage that can be stored in batteries. Therefore, the solar energy industry needs to have high efficiency, competitive pricing, and durability. With the right information technologies and developing application systems, it can help to optimize business processes and integrating information systems. But the fact there are many industries that do not apply information technology correctly into their business. In this research, provide to the best solution for applying the enterprise architecture framework correctly. The purpose of this paper is to design a manufacturing industry information system that is in accordance with the business model canvas and enterprise architecture. The design also discusses the development of a large and integrated information system with other systems. The study of Business Model Canvas is a business model that can explain and focus on nine business aspects with a solid strategy. Studies of the ArchiMate core Framework is the framework used to classify elements of the ArchiMate core language. These two methods are expected to be able to design an enterprise information system architecture consisting of business architecture, application architecture, information architecture and technology architecture as a result of the study. The result is a more complete system design to meet system requirements for users, integrated with existing system modules and no system duplication occurs.

show abstract

Architecture information communication in two OSS projects: The why, who, when, and what

Cited by 9 publications

References 52 publications

Symptoms of Architecture Erosion in Code Reviews: A Study of Two OpenStack Projects

Symptoms of Architecture Erosion in Code Reviews: A Study of Two OpenStack Projects

Understanding, Analysis, and Handling of Software Architecture Erosion

Sustainability of Implementing Enterprise Architecture in the Solar Power Generation Manufacturing Industry

Contact Info

Product

Resources

About