The DOI matches its Crossref record.
The evolution and impact of code smells: A case study of two open source systems
Abstract
Code smells are design flaws in object-oriented designs that may lead to maintainability issues in the further evolution of the software system. This study focuses on the evolution of code smells within a system and their impact on the change behavior (change frequency and size). The study investigates two code smells, God Class and Shotgun Surgery, by analyzing the historical data over several years of development of two large scale open source systems. The detection of code smells in the evolution of those systems was performed by the application of an automated approach using detection strategies. The results show that we can identify different phases in the evolution of code smells during the system development and that code smell infected components exhibit a different change behavior. This information is useful for the identification of risk areas within a software system that need refactoring to assure a future positive evolution.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
An exploratory study of the impact of antipatterns on class change- and fault-proneness
Khomh, F., Penta, M. D., Guéhéneuc, Y.-G., & Antoniol, G. (2012) · Empirical Software Engineering · doi:10.1007/s10664-011-9171-y · Cited by 395
Quantifying the Effect of Code Smells on Maintenance Effort
Sjoberg, D. I. K., Yamashita, A., Anda, B. C. D., Mockus, A., & Dyba, T. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.89 · Cited by 316
Abbes, M., Khomh, F., Gueheneuc, Y.-G., & Antoniol, G. (2011) · 2011 15th European Conference on Software Maintenance and Reengineering · doi:10.1109/csmr.2011.24 · Cited by 309
Palomba, F., Bavota, G., Penta, M. D., Fasano, F., Oliveto, R., & Lucia, A. D. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9535-z · Cited by 305
Detecting code smells using machine learning techniques: Are we there yet?
Di Nucci, D., Palomba, F., Tamburri, D. A., Serebrenik, A., & De Lucia, A. (2018) · 2018 IEEE 25th International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2018.8330266 · Cited by 305
Metadata
- Authors
- Olbrich, S., Cruzes, D. S., Basili, V., & Zazworka, N.
- Venue
- 2009 3rd International Symposium on Empirical Software Engineering and Measurement
- Publisher
- IEEE
- Published
- 2009-10
- Pages
- 390-400
- ISSN
- 1938-6451 (ISSN-L)
- OpenAlex
- W1974655094
- Cited by
- 245
- References
- 0
- FWCI
- 6.23
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The evolution and impact of code smells: A case study of two open source systems. https://app.cochat.ai/papers/10.1109/esem.2009.5314231
- The paper
- Olbrich, S., Cruzes, D. S., Basili, V., & Zazworka, N. (2009). The evolution and impact of code smells: A case study of two open source systems. 2009 3rd International Symposium on Empirical Software Engineering and Measurement. https://doi.org/10.1109/esem.2009.5314231
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.