Abstract
Software development process involves developing, building and enhancing high-quality software for specific tasks and as a consequence generates considerable amount of data. This data can be managed in a systematic manner creating knowledge repositories that can be used to competitive advantage. Lesson's learned as part of the development process can also be part of the knowledge bank and can be used to advantage in subsequent projects by developers and software practitioners. Code smells are a group of symptoms which reveal that code is not good enough and requires some actions to have a cleansed code. Software metrics help to detect code smells while refactoring methods are used for removing them. Furthermore, various tools are applicable for detecting of code smells. A Code smell repository organizes all the available knowledge in the literature about code smells and related concepts. An analytical study of code smells is presented in this paper which extracts useful, actionable and indicative knowledge.
Highlights
INTRODUCTIONLesson's learned and best practices in software development process are spread out over literature in various forms such as Code smells, design patterns, idioms etc
Today’s software development process produces large amount of data
22 code smells are detected by one or more out of 39 software metrics and 28 code smells can be removed by 74 refactoring actions
Summary
Lesson's learned and best practices in software development process are spread out over literature in various forms such as Code smells, design patterns, idioms etc. The significance of this study is to extract some insightful information from inter relation between code smells, software metrics, refactoring actions and detection tools.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
