English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Tools annual

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Presents the access of premium content as premium feature

Premium Content

Global: Zendy Plus annual

Global: Zendy Free Plan

When writing source code, programmers have varying levels of freedom when itcomes to the creation and use of identifiers. Do they habitually use the sameidentifiers, names that are different to those used by others? Is it thenpossible to tell who the author of a piece of code is by examining theseidentifiers? If so, can we use the presence or absence of identifiers to assistin correctly classifying programs to authors? Is it possible to hide theprovenance of programs by identifier renaming? In this study, we assess theimportance of three types of identifiers in source code author classificationfor two different Java program data sets. We do this through a sequence ofexperiments in which we disguise one type of identifier at a time. Theseexperiments are performed using as a tool the Source Code Author Profiles(SCAP) method. The results show that, although identifiers when examined as awhole do not seem to reflect program authorship for these data sets, whenexamined separately there is evidence that class names do signal the author ofthe program. In contrast, simple variables and method names used in Javaprograms do not appear to reflect program authorship. On the contrary, ouranalysis suggests that such identifiers are so common as to mask authorship. Webelieve that these results have applicability in relation to the robustness ofcode plagiarism analysis and that the underlying methods could be valuable incases of litigation arising from disputes over program authorship.

The significance of user-defined identifiers in Java source code authorship identification