The DOI matches its Crossref record; 12 of the 12 references it cites were found in a registry or an index.
Java quality assurance by detecting code smells
Abstract
Software inspection is a known technique for improving software quality. It involves carefully examining the code, the design, and the documentation of software and checking these for aspects that are known to be potentially problematic based on past experience. Code smells are a metaphor to describe patterns that are generally associated with bad design and bad programming practices. Originally, code smells are used to find the places in software that could benefit from refactoring. In this paper we investigate how the quality of code can be automatically assessed by checking for the presence of code smells and how this approach can contribute to automatic code inspection. We present an approach for the automatic detection and visualization of code smells and discuss how this approach can be used in the design of a software inspection tool. We illustrate the feasibility of our approach with the development of jCOSMO, a prototype code smell browser that detects and visualizes code smells in JAVA source code. Finally, we show how this tool was applied in a case study.
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
Cites
A metrics suite for object oriented design
Chidamber, S. R., & Kemerer, C. F. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.295895 · Cited by 5,669
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
Design and code inspections to reduce errors in program development
Fagan, M. E. (1976) · IBM Systems Journal · doi:10.1147/sj.153.0182 · Cited by 1,492
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
Brown, W. H., Malveau, R. C., McCormick, H. W., & Mowbray, T. J. (1998) · Cited by 932
Tarski, A. (1941) · Journal of Symbolic Logic · doi:10.2307/2268577 · Cited by 817
Does code decay? Assessing the evidence from change management data
Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., & Mockus, A. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895984 · Cited by 636
Design and Code Inspections to Reduce Errors in Program Development
Fagan, M. E. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_13 · Cited by 561
Gilb, T., Graham, D., & Finzi, S. (1993) · Cited by 515
A refactoring tool for smalltalk
Roberts, D., Brant, J., & Johnson, R. (1997) · Theory and Practice of Object Systems · doi:10.1002/(sici)1096-9942(1997)3:4<253::aid-tapo3>3.0.co;2-t · Cited by 375
The Asf+Sdf Meta-environment: A Component-Based Language Development Environment
van den Brand, M. G. J., van Deursen, A., Heering, J., de Jong, H. A., de Jonge, M., Kuipers, T., Klint, P., Moonen, L., Olivier, P. A., Scheerder, J., et al. (2001) · Lecture Notes in Computer Science · doi:10.1007/3-540-45306-7_26 · Cited by 323
Self-citation
Cited by
A survey of software refactoring
Mens, T., & Tourwe, T. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.1265817 · Cited by 1,193
A Taxonomy of Model Transformation
Mens, T., & Van Gorp, P. (2006) · Electronic Notes in Theoretical Computer Science · doi:10.1016/j.entcs.2005.10.021 · Cited by 908
DECOR: A Method for the Specification and Detection of Code and Design Smells
Moha, N., Gueheneuc, Y.-G., Duchien, L., & Le Meur, A.-F. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.50 · Cited by 803
Detection strategies: metrics-based rules for detecting design flaws
Marinescu, R. (2004) · 20th IEEE International Conference on Software Maintenance, 2004. Proceedings. · doi:10.1109/icsm.2004.1357820 · Cited by 551
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
Metadata
- Authors
- van Emden, E., & Moonen, L.
- Venue
- Ninth Working Conference on Reverse Engineering, 2002. Proceedings.
- Publisher
- IEEE Comput. Soc
- Published
- 2003-06-26
- Pages
- 97-106
- ISSN
- 1095-1350 (ISSN-L)
- OpenAlex
- W2106013472
- Cited by
- 379
- References
- 12
- FWCI
- 13.76
- 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: Java quality assurance by detecting code smells. https://app.cochat.ai/papers/10.1109/wcre.2002.1173068
- The paper
- van Emden, E., & Moonen, L. (2003). Java quality assurance by detecting code smells. Ninth Working Conference on Reverse Engineering, 2002. Proceedings. https://doi.org/10.1109/wcre.2002.1173068
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.