Abstract
Software refactoring is the process that requires modification in the source code to avoid bad smell. Professional has reviewed typical situations that may need refactoring call it bad smells, indicating that a few piece of the existing code stink dreadful. Bad smells are linked to consequent refactoring policy that can aid dismissing bad smells. Code smell is indication which representing some part is incorrect. It shows that code supposed to refractor or overall design should reconsider. Important is, where to refractor within in existing software is somewhat challenge to recognize region of bad design. Bad design is branded as “bad smells” in existing code. The detection of bad smell code can be done by parsing the particular code and store the related data in database, to detect the bad smell code, display result and provide solution.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Ganesh B. Regulwar R. M. Tugnayat (2015), “An Uncovering of Bad Smell in Software Refactoring” International Journal of Current Engineering and Technology, ISSN 2277–4106.
HELSINKI UNIVERSITY OF TECHNOLOGY, Department of Computer Science and Engineering, Software Business and Engineering Institute-Mika Mäntylä – “Bad Smells in Software – a Taxonomy and an Empirical Study”.
Source: Martin Fowler, Refactoring, “Improving the Design of Existing Code”, Addison Wesley, (1999).
Ganesh B. Regulwar and R. M. Tugnayat, (2013) “A Review on Code Cleanup and Code Standard Refactoring”, International Journal of Current Engineering and Technology E-ISSN 2277-4106, P-ISSN 2347-5161.
Fowler, M, et al. (1999), “Refactoring: Improving the Design of Existing Code”, Addison Wesley. ZHANG, M., HALL, T., WERNICK, P. & BADDOO, N. Code Bad Smells: A Review of Current Knowledge. Technical Report No. 468, Hatfield, STRI, University of Hertfordshire.
Beck, K., Brant, J., Opdyke, Fowler, M., W. and Roberts, D (1999), “Refactoring: Improving the Design of Existing Code”, Addison-Wesley Professional.
Opdyke, W (1992), “Refactoring Object-Oriented Frameworks”, PhD thesis, University of Illinois at Urbana-Champaign.
“A quantitative evaluation of maintainability enhancement by Refactoring”, Yoshio kataoka, Tetsuji fukaya (2002) Proceedings of the international conference on software Maintenance (ICSM’02) IEEE.
Brant, J. and Johnson, R, Roberts, D. (1997), “A Refactoring Tool for Smalltalk. Theory and Practice of Object Systems”, 3(4):253–263.
Reinke, C., Li, H. and Thompson, S (2003), “Tool Support for Refactoring Functional Programs”, In Proc. ACM SIGPLAN Workshop on Haskell. pp. 27–38. ACM, Uppsala, Sweden.
Schrijvers, T., Serebrenik, A. and Demoen, B (2004): Refactoring Prolog Code. In Proc. 18th Workshop on (Constraint) Logic Programming, Potsdam, Germany.
Fowler, M. Crossing Refactoring’s Rubicon (2001). http://www.martinfowler.com/articles/refactoringRubicon.html.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2019 Springer Nature Singapore Pte Ltd.
About this paper
Cite this paper
Regulwar, G.B., Tugnayat, R.M. (2019). Detection of Bad Smell Code for Software Refactoring. In: Saini, H., Sayal, R., Govardhan, A., Buyya, R. (eds) Innovations in Computer Science and Engineering. Lecture Notes in Networks and Systems, vol 32. Springer, Singapore. https://doi.org/10.1007/978-981-10-8201-6_16
Download citation
DOI: https://doi.org/10.1007/978-981-10-8201-6_16
Published:
Publisher Name: Springer, Singapore
Print ISBN: 978-981-10-8200-9
Online ISBN: 978-981-10-8201-6
eBook Packages: EngineeringEngineering (R0)