The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
A survey on software smells
Open accessAbstract
Abstract Context Smells in software systems impair software quality and make them hard to maintain and evolve. The software engineering community has explored various dimensions concerning smells and produced extensive research related to smells. The plethora of information poses challenges to the community to comprehend the state-of-the-art tools and techniques. Objective We aim to present the current knowledge related to software smells and identify challenges as well as opportunities in the current practices. Method We explore the definitions of smells, their causes as well as effects, and their detection mechanisms presented in the current literature. We studied 445 primary studies in detail, synthesized the information, and documented our observations. Results The study reveals five possible defining characteristics of smells — indicator, poor solution, violates best-practices, impacts quality, and recurrence. We curate ten common factors that cause smells to occur including lack of skill or awareness and priority to features over quality. We classify existing smell detection methods into five groups — metrics, rules/heuristics, history, machine learning, and optimization-based detection. Challenges in the smells detection include the tools’ proneness to false-positives and poor coverage of smells detectable by existing tools.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Cites
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
Subjective evaluation of software evolvability using code smells: An empirical study
Mäntylä, M. V., & Lassenius, C. (2007) · Empirical Software Engineering · doi:10.1007/s10664-006-9002-8 · Cited by 171 · cited 1×
“• Many authors have asserted that smell detection is a subjective process [73, 96, 84].”
Background
Cited by
(2019) · doi:10.1109/techdebt.2019.00027 · Cited by 94
Sustainable software engineering: Reflections on advances in research and practice
Venters, C. C., Capilla, R., Nakagawa, E. Y., Betz, S., Penzenstadler, B., Crick, T., & Brooks, I. (2023) · Information and Software Technology · doi:10.1016/j.infsof.2023.107316 · Cited by 59
DeleSmell: Code smell detection based on deep learning and latent semantic analysis
Zhang, Y., Ge, C., Hong, S., Tian, R., Dong, C., & Liu, J. (2022) · Knowledge-Based Systems · doi:10.1016/j.knosys.2022.109737 · Cited by 54
A systematic mapping study on architectural smells detection
Mumtaz, H., Singh, P., & Blincoe, K. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2020.110885 · Cited by 44
Predicting Design Impactful Changes in Modern Code Review: A Large-Scale Empirical Study
Uchoa, A., Barbosa, C., Coutinho, D., Oizumi, W., Assuncao, W. K. G., Vergilio, S. R., Pereira, J. A., Oliveira, A., & Garcia, A. (2021) · 2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR) · doi:10.1109/msr52588.2021.00059 · Cited by 42
“FG smells are indicators of structural degradation in the scope of methods and code blocks [37].”
BackgroundInfluential
Metadata
- Authors
- Sharma, T., & Spinellis, D.
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2018-04
- Volume
- 138
- Pages
- 158-173
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2780783514
- Cited by
- 251
- References
- 2
- FWCI
- 35.66
- Type
- journal article
- Language
- en
- Open access
- green
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
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.