2014
DOI: 10.1007/s10664-014-9344-6
|View full text |Cite
|
Sign up to set email alerts
|

An empirical study of the textual similarity between source code and source code summaries

Abstract: Source code documentation often contains summaries of source code written by authors. Recently, automatic source code summarization tools have emerged that generate summaries without requiring author intervention. These summaries are designed for readers to be able to understand the high-level concepts of the source code. Unfortunately, there is no agreed upon understanding of what makes up a "good summary." This paper presents an empirical study examining summaries of source code written by authors, readers, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
5
2
2

Relationship

1
8

Authors

Journals

citations
Cited by 31 publications
(8 citation statements)
references
References 37 publications
0
8
0
Order By: Relevance
“…Because of how LSS compares two bodies of text, large sentences often get artificially inflated, as a large number of words means at least one word is more likely to be semantically similar. We encountered this in previous work . When this did occur, conciseness scores and accuracy scores were usually lower.…”
Section: Discussionmentioning
confidence: 85%
“…Because of how LSS compares two bodies of text, large sentences often get artificially inflated, as a large number of words means at least one word is more likely to be semantically similar. We encountered this in previous work . When this did occur, conciseness scores and accuracy scores were usually lower.…”
Section: Discussionmentioning
confidence: 85%
“…Therefore, there is an urgent need to generate a short description for the code to describe the code function accurately and effectively avoid errors caused by differences in conceptual understanding between maintainers and developers. [28].…”
Section: Problem Statementmentioning
confidence: 99%
“…McBurney and McMillan propose generating docu-mentation summaries for Java methods using the call graph [7]. Furthermore, they propose an approach to evaluate a summary using textual similarity of that summary to the source code [42]. Haiduc et al [8] investigate the suitability of several text summarization techniques to automatically generate termbased summaries for methods and classes.…”
Section: Related Workmentioning
confidence: 99%