The DOI matches its Crossref record.
Product Metrics for Automatic Identification of "Bad Smell" Design Problems in Java Source-Code
Abstract
Refactoring can have a direct influence on reducing the cost of software maintenance through changing the internal structure of the source-code to improve the overall design that helps the present and future programmers evolve and understand a system. Bad smells are a set of design problems with refactoring identified as a solution. Locating these bad smells has been described as more a human intuition than an exact science. This paper addresses the issue of identifying the characteristics of a bad smell through the use of a set of software metrics. Then by using a pre-defined set of interpretation rules to interpret the software metric results applied to Java source-code, the software engineer can be provided with significant guidance as to the location of bad smells. These issues are addressed in a number of ways. Firstly, a precise definition of bad smells is given from the informal descriptions given by the originators Fowler and Beck. The characteristics of the bad smells have been used to define a set of measurements and interpretation rules for a subset of the bad smells. A prototype tool has been implemented to enable the evaluation of the interpretation rules in two case studies.
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
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
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
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
An Exploratory Study of the Impact of Code Smells on Software Change-proneness
Khomh, F., Di Penta, M., & Gueheneuc, Y.-G. (2009) · 2009 16th Working Conference on Reverse Engineering · doi:10.1109/wcre.2009.28 · Cited by 306
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
Metadata
- Authors
- Munro, M. J.
- Venue
- 11th IEEE International Software Metrics Symposium (METRICS'05)
- Publisher
- IEEE
- Published
- 2005-10-24
- Pages
- 15-15
- OpenAlex
- W2149963636
- Cited by
- 191
- References
- 0
- FWCI
- 2.83
- 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: Product Metrics for Automatic Identification of "Bad Smell" Design Problems in Java Source-Code. https://app.cochat.ai/papers/10.1109/metrics.2005.38
- The paper
- Munro, M. J. (2005). Product Metrics for Automatic Identification of "Bad Smell" Design Problems in Java Source-Code. 11th IEEE International Software Metrics Symposium (METRICS'05). https://doi.org/10.1109/metrics.2005.38
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.