An interactive ambient visualization for code smells
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Code smells are characteristics of software that indicate that code may have a design problem. Code smells have been proposed as a way for programmers to recognize the need for restructuring their software. Because code smells can go unnoticed while programmers are working, tools called smell detectors have been developed to alert programmers to the presence of smells in their code, and to help them understand the cause of those smells. In this paper, we propose a novel smell detector called Stench Blossom that provides an interactive ambient visualization designed to first give programmers a quick, high-level overview of the smells in their code, and then, if they wish, to help in understanding the sources of those code smells. We also describe a laboratory experiment with 12 programmers that tests several hypotheses about our tool. Our findings suggest that programmers can use our tool effectively to identify smells and to make refactoring judgements. This is partly because the tool serves as a memory aid, and partly because it is more reliable and easier to use than heuristics for analyzing smells.
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
McFarlane, D. C. (2002) · Human–Computer Interaction · doi:10.1207/s15327051hci1701_2 · Cited by 378 · cited 1×
“In this sense, our visualization uses negotiated interruption, where the user is informed of the availability of information but is not forced to acknowledge it immediately [14].”
Method
Cited by
Why don't software developers use static analysis tools to find bugs?
Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606613 · Cited by 568
Self-citationComparing and experimenting machine learning techniques for code smell detection
Arcelli Fontana, F., Mäntylä, M. V., Zanoni, M., & Marino, A. (2016) · Empirical Software Engineering · doi:10.1007/s10664-015-9378-4 · Cited by 450
Use, disuse, and misuse of automated refactorings
Vakilian, M., Chen, N., Negara, S., Rajkumar, B. A., Bailey, B. P., & Johnson, R. E. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227190 · Cited by 106
Improving software developers' fluency by recommending development environment commands
Murphy-Hill, E., Jiresal, R., & Murphy, G. C. (2012) · Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering · doi:10.1145/2393596.2393645 · Cited by 67
Self-citation
Metadata
- Authors
- Murphy-Hill, E., & Black, A. P.
- Venue
- Proceedings of the 5th international symposium on Software visualization
- Publisher
- ACM
- Published
- 2010-10-25
- Pages
- 5-14
- OpenAlex
- W2099535882
- Cited by
- 147
- References
- 1
- FWCI
- 7.65
- 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: An interactive ambient visualization for code smells. https://app.cochat.ai/papers/10.1145/1879211.1879216
- The paper
- Murphy-Hill, E., & Black, A. P. (2010). An interactive ambient visualization for code smells. Proceedings of the 5th international symposium on Software visualization. https://doi.org/10.1145/1879211.1879216
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.