An Empirical Study of Architectural Decay in Open-Source Software

Le, Duc Minh; Link, Daniel; Shahbazian, Arman; Medvidović, Nenad

doi:10.1109/icsa.2018.00027

Cited by 63 publications

(70 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The problems which appear at this level are usually from the Interface-Based Smells category as defined in [8], [11]. Is not uncommon to find Ambiguous Interfaces or Concern Overload where a component performs a large amount of tasks and have a scarce number of interfaces.…”

Section: Discussionmentioning

confidence: 99%

“…The most problematic ones were the E-commerce and Firefox. In all the codebases excepting the Game, we find the Concern Overload and the Ambiguous Interfaces smells [8], [11]. D. View 1) Issues: In large projects, which do not have major architectural issues, the Controller objects configure the Views by directly passing the Model item as an argument.…”

Section: Discussionmentioning

confidence: 99%

“…The mentioned problem belongs to Co-change Coupling smells [11], an architectural issue which occurs frequently at this level. The coupling is predominantly done between the View and the Model layer.…”

Section: Discussionmentioning

confidence: 99%

“…In [9] and [10] 4 of the architectural smells are analysed in depth and shown on 2 industrial software systems. Other work has been done in [11] where the authors have analysed the architectural erosion of Open-Source Software projects.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Model View Controller in iOS mobile applications development

Dobrean¹,

Dioşan²

2019

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Due to the increased number of mobile applications and their popularity, many software developers have begun to focus on mobile platforms. While this focus has positive effects (e.g. a larger developer community, new open source projects, new tools), it also has a down side. With the migration of developers from different software development areas, where they have used other programming paradigms or architectural approaches, the topic of software architecture on mobile platforms become more trending and hype in the mobile development communities. Even though several new architectural solution were proposed for solving some of the issues which arise from using the classical architectural patterns popularised by the creators of the mobile platforms, we want to emphasise the principles of software architecture in mobile computing, why they have to be respected and how their adoption impacts the development process. Therefore, this paper focuses on showing that the Model View Controller (MVC) -one of the most common classical architectural patterns -can be used successfully for building mobile applications and the problems which might arise are by products of the wrong usage of the pattern rather than pattern issues. We show that by analysing the most common architectural misuses of the MVC pattern in both open-source and private projects and offers solutions to those problems.Index Terms-Apple's Model View Controller (MVC), Mobile Software Architecture, Architectural Smell, iOS.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Model View Controller in iOS mobile applications development

Dobrean¹,

Dioşan²

2019

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…Code smells are related to code entities, architectural smells are related to components. One does not automatically map to the other [21].…”

Section: Code Smells and Architectural Smellsmentioning

confidence: 99%

The Value of Software Architecture Recovery for Maintenance

Link¹,

Behnamghader²,

Moazeni

et al. 2019

Proceedings of the 12th Innovations in Software Engineering Conference (Formerly Known as India Software Engineering Conference

Self Cite

View full text Add to dashboard Cite

In order to maintain a system, it is beneficial to know its software architecture. In the common case that this architecture is unavailable, architecture recovery provides a way to recover an architectural view of the system. Many different methods and tools exist to provide such a view. While there have been taxonomies of different recovery methods and surveys of their results along with measurements of how these results conform to expert's opinions on the systems, there has not been a survey that goes beyond a simple automatic comparison. Instead, this paper seeks to answer questions about the viability of individual methods in given situations, the quality of their results and whether these results can be used to indicate and measure the quality and quantity of architectural changes. For our case study, we look at the results of recoveries of versions of Android, Apache Hadoop and Apache Chukwa obtained by running PKG, ACDC and ARC.

show abstract

On the relation between architectural smells and source code changes

Sas

Avgeriou

Pigazzini

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

Although architectural smells are one of the most studied type of architectural technical debt, their impact on maintenance effort has not been thoroughly investigated. Studying this impact would help to understand how much technical debt interest is being paid due to the existence of architecture smells and how this interest can be calculated. This work is a first attempt to address this issue by investigating the relation between architecture smells and source code changes. Specifically, we study whether the frequency and size of changes are correlated with the presence of a selected set of architectural smells. We detect architectural smells using the Arcan tool, which detects architectural smells by building a dependency graph of the system analyzed and then looking for the typical structures of the architectural smells. The findings, based on a case study of 31 open‐source Java systems, show that 87% of the analyzed commits present more changes in artifacts with at least one smell, and the likelihood of changing increases with the number of smells. Moreover, there is also evidence to confirm that change frequency increases after the introduction of a smell and that the size of changes is also larger in smelly artifacts. These findings hold true especially in Medium–Large and Large artifacts.

show abstract

An Empirical Study of Architectural Decay in Open-Source Software

Cited by 63 publications

References 33 publications

Model View Controller in iOS mobile applications development

Model View Controller in iOS mobile applications development

The Value of Software Architecture Recovery for Maintenance

On the relation between architectural smells and source code changes

Contact Info

Product

Resources

About