Detecting Inconsistent Code Identifiers


KIPS Transactions on Software and Data Engineering, Vol. 2, No. 5, pp. 319-328, May. 2013
10.3745/KTSDE.2013.2.5.319,   PDF Download:

Abstract

Software maintainers try to comprehend software source code by intensively using source code identifiers. Thus, use of inconsistent identifiers throughout entire source code causes to increase cost of software maintenance. Although participants can adopt peer reviews to handle this problem, it might be impossible to go through entire source code if the volume of code is huge. This paper introduces an approach to automatically detecting inconsistent identifiers of Java source code. This approach consists of tokenizing and POS tagging all identifiers in the source code, classifying syntactic and semantic similar terms, and finally detecting inconsistent identifiers by applying proposed rules. In addition, we have developed tool support, named CodeAmigo, to support the proposed approach. We applied it to two popular Java based open source projects in order to show feasibility of the approach by computing precision.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
S. N. Lee, S. T. Kim, S. Y. Park, "Detecting Inconsistent Code Identifiers," KIPS Transactions on Software and Data Engineering, vol. 2, no. 5, pp. 319-328, 2013. DOI: 10.3745/KTSDE.2013.2.5.319.

[ACM Style]
Sung Nam Lee, Sun Tae Kim, and Soo Young Park. 2013. Detecting Inconsistent Code Identifiers. KIPS Transactions on Software and Data Engineering, 2, 5, (2013), 319-328. DOI: 10.3745/KTSDE.2013.2.5.319.