The code cleaning requires the incorporation of the various processes to remove the clones from the source code as well as the programming irregularities, which improve the overall design of the code. In this paper, the proposed model has been designed for the purpose of code cleaning by using the multi-factor code cleaning algorithm. The proposed model is entirely based upon the elimination of the source code irregularities, which contains the bad smells, code clones and other such problems. The proposed model is designed to work in the three primary components, which includes the code clone and smell detection and marking algorithm, which is followed by the refactoring method estimation and then the application of the refactoring application in the final phase for the act of cleaning the source code. The proposed model utilizes the divide and conquer method, which is concerned with the extraction of the methods from the class files. Also the proposed model analyzed and extracts the independent statements from the extracted methods, which incorporates the common statement elimination, which removes the common statements from the duplication removal process. The proposed model has been designed to refactor the code on the basis of the bad smell detection and elimination with the appropriate method. The proposed model has been analyzed under the various kinds of the datasets for the experimental evaluation, where it has been found better. The proposed model has been recorded with the significant values of the parameters of the accuracy, precision and recall.

Code clone detection, Code cleaning, Duplication detection, Overlapping shifting method

[1] M. Fowler, Refactoring: Improving the Design of Existing Code, Addison-Wesley, 2000.
[2] W. G. Griswold, W. F. Opdyke, The Birth of Refactoring: A retrospective on the Nature of High-Impact Software Engineering Research, IEEE Software, 32 (6) (2015), 30-38.
[3] R. Geiger, Evolution Impact of Code Clones, Diploma Thesis, University of Zurich, October, 2005.
[4] M. Hafiz, J. Overbey, Refactoring Myths, IEEE Software 32 (6) (2015), 39-43.
[5] ToolIclonehttp://www.softwareclones.org/iclones.php>(accessed December 2015).
[6] ToolJcdhttp://www.swag.uwaterloo.ca/jcd/> (accessed December 2015).
[7] R. Koschke, I. D. Baxter, M. Conradt, J. R. Cordy, Software Clone Management Towards Industrial Application, Dagstuhl Seminar 12071 on 2 (2) (2012) 21-57.
[8] M. Kim, Z. Thomas, N. Nachiappan, An Empirical Study of Refactoring Challenges and Benefits at Microsoft, Software Engineering, IEEE Transactions on 40, (7 ) (2014) 633-649.
[9] E. Kodhai, S. Kanmani, Method-Level Code Clone Modification using Refactoring Techniques for Clone Maintenance, Advanced Computing: An International Journal (ACIJ), 4 (2), March 2013, 7-26.
[10] E. Murphy-Hill, C. Parnin, A.P. Black, Refactoring Tools: Fitness for Purpose, IEEE Transactions on Software Engineering, 25, (5), (2008) 38-44.
[11] E. Murphy-Hill, A. P. Black, Why Don’t People Use Refactoring Tools?, in proceedings of the Computer Science Faculty Publications and Presentations, Portland State University, Portland, (2007), Paper 115.
[12] T. Mens, T. Tourwé, A Survey of Software Refactoring, IEEE Transactions on Software Engineering, 30, (2), (2004) 126-139.
[13] M. O’Keeffe, M. Ó, Cinnéide, Search-based refactoring: an empirical study, J. Softw.Maint.Evol, Res. Pract., 20, (2008), 345–364.
[14] C.K. Roy, J.R. Cordy, A Survey on Software Clone Detection Research, Technical Report 2007-541, Queen’s University at Kingston Ontario, Canada, 2007, p.115.
[15] C.K Roy, M.F Zibran, R. Koschke, The Vision of Software Clone Management: Past, Present, and Future (keynote paper), in: proceeding of the Software Maintenance and Reengineering and Reverse Engineering, Antwerp, Belgium, (CSMR-WCRE), 2014, pp. 18-33.
[16] D. Rattan, R. Bhatia, and M. Singh, Software clone detection: A systematic review, Information and Software Technology 55 (7) (2013) 1165-1199.
[17] M. Tufano, F. Palomba, G. Bavota, R. Oliveto, M. D. Penta, A. D. Lucia, D. Poshyvanyk, When and Why Your Code Starts to Smell Bad, in: Proceedings of the 37th International Conference on Software Engineering, Florence, Italy, 2015, pp. 403-414.
[18] N. Tsantalis, D. Mazinanian, G. P. Krishnan, Assessing the Refactorability of Software Clones, Software Engineering, IEEE Transactions on 41 (11) (2015) 1055-1090.
[19] M. D Wit, A. Zaidman, A. V. Deursen, Managing Code Clones Using Dynamic Change Tracking and Resolution, In: proceeding of the ICSM, 2009 pp. 169–178.
[20] M. D Wit, Managing Clones Using Dynamic Change Tracking and Resolution, Master’s thesis, Software Engineering Research Group, Delft University of Technology, 2009.
[21] M. F. Zibran, C. K. Roy, The Road to Software Clone Management: A survey, Technical Report 2012–03, The University of Saskatchewan, Canada, Feb., 2012 p. 54.
[22] M. F. Zibran, Chanchal Kumar Roy, Conflict-aware optimal scheduling of prioritised code clone refactoring, IET Software, on 7 (3) (June, 2013) 167-186.