IDEAS home Printed from https://ideas.repec.org/h/spr/ssrchp/978-3-031-55048-5_17.html
   My bibliography  Save this book chapter

An Insight into Code Smell Detection Tool

Author

Listed:
  • Shrasti Mourya

    (Jawaharlal Nehru University)

  • Piyush Pratap Singh

    (Jawaharlal Nehru University)

  • V. B. Singh

    (Jawaharlal Nehru University)

Abstract

A code smell isn’t a bug and it won’t help your system operate exceptionally. It might simply make it more difficult for software engineers to comprehend and maintain project source code, resulting in extra maintenance expenses. Researchers have provided a variety of techniques and tools for extracting code smells throughout the last 20 years. Therefore, there is a need for comprehensive research that summarizes and compares the large range of existing tools. We present a complete catalogue of all known code smell detection tools in this paper. We found 112 tools as a result of our study, 52 of them available for download online. They also support a variety of programming languages including Java, JavaScript, C, C++, C#, Python, and others. We categorize different code smell detection tools in this study based on their type, availability, detection techniques, identified code smells, supported languages, and main features.

Suggested Citation

  • Shrasti Mourya & Piyush Pratap Singh & V. B. Singh, 2024. "An Insight into Code Smell Detection Tool," Springer Series in Reliability Engineering,, Springer.
    • Handle: RePEc:spr:ssrchp:978-3-031-55048-5_17
    DOI: 10.1007/978-3-031-55048-5_17
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:ssrchp:978-3-031-55048-5_17. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.