Implementation and Analysis of a Refactoring Tool for Detecting Code Smells

Amandeep Kaur,Himanshi Raperia

doi:10.24297/ijct.v6i1.4455

Amandeep Kaur, Himanshi Raperia

Open Access

https://doi.org/10.24297/ijct.v6i1.4455

Copy DOI

Abstract

Software development is a field which is in action for decades. Preparing code for Software is not a difficult task, but preparing an efficient code is complicated one. To change the code is to make internal structure of the code easier to understand and economic to modify, without changing the behavior and desired response. More changes will make software patchy. No Software is free from smells especially the patchy one. Lots of work has been done for detecting and removing a few of the smells (Refactoring) from code. In this paper our main focus will be on tool SCSD (Software Code Smell Detector) developed, uses a bit classification, clustering approach with K-mean Clustering Algorithm to detect the code smells, which can implement completely different architecture if it discovers smell.Â

Highlights

Software development is at boon from last decade or two
Memory can be saved by removing Dead code and unwanted parameters
Complexity can be simplified to major extent, if it would be possible to divide Large Classes and Long Methods into more in number but small, simplified and relevant ones

Summary

Introduction

Software development is at boon from last decade or two. A code smell can be said as drawback of the code. Code smells get introduced in software due to recursive implementation and design problems which calls for maintenance and evolution of the software. There are numerous code smells, but our tool is capable of detecting four smells only and they are: a. Large Class: Large classes, like long methods, are difficult to read, understand, and troubleshoot. Does the class contain too many responsibilities? Can the large class be restructured or broken into smaller classes? Does the class contain too many responsibilities? Can the large class be restructured or broken into smaller classes? If possible, it should be done

Objectives

Methods

Conclusion