A Validation of Object-Oriented Design Metrics as Quality Indicators
IEEE Transactions on Software Engineering
A Unified Framework for Coupling Measurement in Object-Oriented Systems
IEEE Transactions on Software Engineering
Exploring the relationship between design measures and software quality in object-oriented systems
Journal of Systems and Software
The prediction of faulty classes using object-oriented design metrics
Journal of Systems and Software
The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics
IEEE Transactions on Software Engineering
A Unified Framework for Cohesion Measurement in Object-OrientedSystems
Empirical Software Engineering
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
An Empirical Investigation of an Object-Oriented Software System
IEEE Transactions on Software Engineering
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
A Survey of Software Refactoring
IEEE Transactions on Software Engineering
Journal of Software Maintenance and Evolution: Research and Practice - Analyzing the Evolution of Large-Scale Software
Empirical Validation of Object-Oriented Metrics on Open Source Software for Fault Prediction
IEEE Transactions on Software Engineering
Proceedings of the 28th international conference on Software engineering
The evolution and impact of code smells: A case study of two open source systems
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Improving the usability of the source code quality index with interchangeable metrics sets
Information Processing Letters
On the ability of complexity metrics to predict fault-prone classes in object-oriented systems
Journal of Systems and Software
Finding software metrics threshold values using ROC curves
Journal of Software Maintenance and Evolution: Research and Practice
Proceedings of the 2011 ACM Symposium on Applied Computing
Investigating the impact of design debt on software quality
Proceedings of the 2nd Workshop on Managing Technical Debt
ACM SIGSOFT Software Engineering Notes
Are the classes that use exceptions defect prone?
Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution
ACM SIGSOFT Software Engineering Notes
An exploratory study of the impact of antipatterns on class change- and fault-proneness
Empirical Software Engineering
An exploratory study to investigate the impact of conceptualization in god class detection
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Exploring the impact of inter-smell relations on software maintainability: an empirical study
Proceedings of the 2013 International Conference on Software Engineering
To what extent can maintenance problems be predicted by code smell detection? - An empirical study
Information and Software Technology
Software trustworthiness 2.0-A semantic web enabled global source code analysis approach
Journal of Systems and Software
Hi-index | 0.01 |
Bad smells are used as a means to identify problematic classes in object-oriented systems for refactoring. The belief that the bad smells are linked with problematic classes is largely based on previous metric research results. Although there is a plethora of empirical studies linking software metrics to errors and error proneness of classes in object-oriented systems, the link between the bad smells and class error probability in the evolution of object-oriented systems after the systems are released has not been explored. There has been no empirical evidence linking the bad smells with class error probability so far. This paper presents the results from an empirical study that investigated the relationship between the bad smells and class error probability in three error-severity levels in an industrial-strength open source system. Our research, which was conducted in the context of the post-release system evolution process, showed that some bad smells were positively associated with the class error probability in the three error-severity levels. This finding supports the use of bad smells as a systematic method to identify and refactor problematic classes in this specific context.