Toward a Catalogue of Architectural Bad Smells

Garcia, Joshua; Popescu, Dorin; Edwards, George; Medvidović, Nenad

doi:10.1007/978-3-642-02351-4_10

Cited by 100 publications

(97 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…While the accessible systems consist of about 100 and 50 classes, respectively, the systems investigated in this article consist of more than 500 and 700 classes each. Largely based on the same systems, the authors also investigated if, and confirmed that, groups of code anomalies "flocking together" are more correlated with higher level design problems (such as "fat interface" or "overused interface") than single code anomalies (Oizumi et al 2016;Garcia et al 2009). …”

Section: Related Workmentioning

confidence: 99%

Exploring the suitability of source code metrics for indicating architectural inconsistencies

2018

View full text Add to dashboard Cite

Software architecture degradation is a phenomenon that frequently occurs during software evolution. Source code anomalies are one of the several aspects that potentially contribute to software architecture degradation. Many techniques for automating the detection of such anomalies are based on source code metrics. It is, however, unclear how accurate these techniques are in identifying the architecturally relevant anomalies in a system. The objective of this paper is to shed light on the extent to which source code metrics on their own can be used to characterize classes contributing to software architecture degradation. We performed a multi-case study on three open-source systems for each of which we gathered the intended architecture and data for 49 different source code metrics taken from seven different code quality tools. This data was analyzed to explore the links between architectural inconsistencies, as detected by applying reflexion modeling, and metric values indicating potential design problems at the implementation level. The results show that there does not seem to be a direct correlation between metrics and architectural inconsistencies. For many metrics, however, classes more problematic as indicated by their metric value seem significantly more likely to contribute to inconsistencies than less problematic classes. In particular, the fan-in, a classes' public API, and method counts seem to be suitable indicators. The fan-in metric seems to be a particularly interesting indicator, as class size does not seem to have a confounding effect on this metric. This finding may be useful for focusing code restructuring efforts on architecturally relevant metrics in case the intended architecture is not explicitly specified and to further improve architecture recovery and consistency checking tool support.

show abstract

Section: Related Workmentioning

confidence: 99%

Exploring the suitability of source code metrics for indicating architectural inconsistencies

2018

View full text Add to dashboard Cite

show abstract

“…However, mixing communication styles can decreases the benefits of each individual style [10]. Consider the example in Figure 1.…”

Section: Categorizing Distributed Event-based Systemsmentioning

confidence: 98%

Impact analysis for distributed event-based systems

Popescu

Garcia

Bierhoff

et al. 2012

Proceedings of the 6th ACM International Conference on Distributed Event-Based Systems

Self Cite

View full text Add to dashboard Cite

Distributed event-based (DEB) systems contain highly-decoupled components that interact by exchanging messages via implicit invocation, thus allowing flexible system composition and adaptation. At the same time, these inherently desirable properties render a DEB system more difficult to understand and evolve since, in the absence of explicit dependency information, an engineer has to assume that any component in the system may potentially interact with, and thus depend on, any other component. Software analysis techniques that have been used successfully in traditional, explicit invocation-based systems are of little use in this domain. In order to aid the understandability of, and assess the impact of changes in, DEB systems, we propose Helios, a technique that combines component-level (1) control-flow and (2) state-based dependency analysis with system-level (3) structural analysis to produce a complete and accurate message dependence graph for a system. We have applied Helios to applications constructed on top of four different message-oriented middleware platforms. We summarize the results of several such applications. We demonstrate that Helios enables effective impact analysis and quantify its improvements over existing alternatives.

show abstract

“…Code smells are code-level symptoms indicating the expected presence of an anti-pattern (also called ‗Design Flaw' [27]). Architectural bad smells are also presented by different authors [28,29,30]. A review on product line based architectural bad smells is presented by Vale et al [31].…”

Section: Stat Of the Artmentioning

confidence: 99%

A Lightweight Approach for Specification and Detection of SOAP Anti-Patterns

Sabir¹,

Rasool²,

Yousaf³

2017

ijacsa

View full text Add to dashboard Cite

Abstract-Web-services have become a governing technology for Service Oriented Architectures due to reusability of services and their dependence on other services. The evolution in service based systems demands frequent changes to provide quality of service to customers. It is realised by different researchers that evolution in service based systems may degrade design and quality of service and may generate poor solutions known as antipatterns. The detection of anti-patterns from web services is an important research realm and it is continuously getting the attention of researchers. There are a number of techniques and tools presented for detection of anti-patterns from object oriented software applications but only few approaches are presented for detection of anti-patterns from SOA. The state of the art anti-pattern detection approaches presented for detection of anti-patterns from SOA are not flexible enough and they are limited to detection of only a few anti-patterns. We present a flexible approach supplemented with a tool support to detect 10 anti-patterns from different SOA-based applications. We compare results of our approach with two representative state of the art approaches.

show abstract

Toward a Catalogue of Architectural Bad Smells

Cited by 100 publications

References 14 publications

Exploring the suitability of source code metrics for indicating architectural inconsistencies

Exploring the suitability of source code metrics for indicating architectural inconsistencies

Impact analysis for distributed event-based systems

A Lightweight Approach for Specification and Detection of SOAP Anti-Patterns

Contact Info

Product

Resources

About