Skip to main content

Detecting Inconsistent Names of Source Code Using NLP

  • Conference paper

Part of the book series: Communications in Computer and Information Science ((CCIS,volume 352))

Introduction

Software developers use refactoring in order to improve quality of source code. Refactoring is a disciplined technique for restructuring an existing body of code without changing its external behavior[3]. For example, ‘Extract method’ is the one of the refactoring approaches to improving readability of the large-scale method by splitting them into several small-scale methods. In refactoring, code smell indicates any symptom in the source code that possibly causes a deeper problem. Although inconsistent names of source code elements as one of the code smells are crucial, it is hardly achieved by going through the whole source code. Furthermore, it generally can be handled by several developers that understand the source code and also is easy to pass without checking because it does not affect software execution.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Buse, R., Weimer, W.: A Metric for Software Readiability. In: Proceedings of International Symposium on Software Testing and Analysis (ISSTA), Seattle, WA, pp. 121–130 (2008)

    Google Scholar 

  2. Code Conventions for the Java Programming Language: Why Have Code Conventions, Sunmicro Systems (1999), http://www.oracle.com/technetwork/java/index-135089.html

  3. Fowler, M.: Refactoring: Improving the Design of Existing Code. Addison-Wesley (1999)

    Google Scholar 

  4. Levenshtein, V.I.: Binary codes capable of correcting deletions, insertions and reversals. Soviet Physics Doklady 10(8), 707–710 (1966)

    MathSciNet  Google Scholar 

  5. Posnett, D., Hindle, A., Devanbu, P.: A Simpler Model of Software Readiability. In: Proceedings of International Confernce on Mining Software Repository(MSR), Honolulu, Hawaii, pp. 73–82 (2011)

    Google Scholar 

  6. The Stanford Parser: A statistical parser, Home page (2012), http://nlp.stanford.edu/software/lex-parser.shtml

  7. WordNet: A lexical database for English, Home page (2012), http://wordnet.princeton.edu/

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Lee, S., Kim, S., Kim, J., Park, S. (2012). Detecting Inconsistent Names of Source Code Using NLP. In: Kim, Th., Ma, J., Fang, Wc., Zhang, Y., Cuzzocrea, A. (eds) Computer Applications for Database, Education, and Ubiquitous Computing. EL DTA 2012 2012. Communications in Computer and Information Science, vol 352. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-35603-2_17

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-35603-2_17

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-35602-5

  • Online ISBN: 978-3-642-35603-2

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics