{'fraction_non_alphanumeric': 0.014652014652014652, 'fraction_numerical': 0.0, 'mean_word_length': 5.3076923076923075, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Performance - Detection of Bad Smells In Code for Refactoring Methods

Day by day the complexity levels of Software system increasing. Hence more effort is required for software organizations to develop new or rebuild existing system of high quality. Refactoring reduces 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 developers to evolve and understand a system. This paper describes new refactoring methods and metrics along with the existing metrics to identify the characteristics of bad smells "Lazy Class" and "Temporary Field" through which the developer can be provided with significant guidance to locate bad smells. After identifying these bad smells, appropriate refactoring methods can remove them.