Measuring Code Smells and Anti-Patterns
Reeshti, Rajni Sehgal, Renuka Nagpal, Deepti Mehrotra
Abstract
Reeshti, Rajni Sehgal, Renuka Nagpal, Deepti Mehrotra
Abstract
Code smells are the design problems of software that are categorized under the names like smells, code scattering, code flaws, code tangling and code non-complying to design principles, etc. It highlights a deeper problem and significant issues in the software design model. As soon as these design problems are discovered, it has to be rectified by applying suitable refactoring techniques and improving various aspects concerning quality such as ability to maintain easily, comprehend better and reuse. The reason to rectify smells is that the existence of smells in the code can lead to downfall showcasing negative implications on the overall software functionality and the quality of software which increases the overall maintenance and a lot of cost goes waste in this process. In this paper, the recent advances and refactoring tools are being deployed to identify non-essential code smells, demarcate the existence and evolution of smells by analyzing previous versions and new versions of code.
OpenAlex reports 4 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Code smells are the design problems of software that are categorized under the names like smells, code scattering, code flaws, code tangling and code non-complying to design principles, etc. It highlights a deeper problem and significant issues in the software design model. As soon as these design problems are discovered, it has to be rectified by applying suitable refactoring techniques and improving various aspects concerning quality such as ability to maintain easily, comprehend better and reuse. The reason to rectify smells is that the existence of smells in the code can lead to downfall showcasing negative implications on the overall software functionality and the quality of software which increases the overall maintenance and a lot of cost goes waste in this process. In this paper, the recent advances and refactoring tools are being deployed to identify non-essential code smells, demarcate the existence and evolution of smells by analyzing previous versions and new versions of code.
Key concepts: Code smell, Code refactoring, Computer science, Software engineering, Code (set theory), Reuse, Static program analysis, Software quality