2018 IEEE International Conference on Software Maintenance and Evolution (ICSME) 2018
DOI: 10.1109/icsme.2018.00056
|View full text |Cite
|
Sign up to set email alerts
|

Adapting Neural Text Classification for Improved Software Categorization

Abstract: Software Categorization is the task of organizing software into groups that broadly describe the behavior of the software, such as "editors" or "science." Categorization plays an important role in several maintenance tasks, such as repository navigation and feature elicitation. Current approaches attempt to cast the problem as text classification, to make use of the rich body of literature from the NLP domain. However, as we will show in this paper, text classification algorithms are generally not applicable o… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
21
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
4
1

Relationship

3
7

Authors

Journals

citations
Cited by 30 publications
(21 citation statements)
references
References 52 publications
0
21
0
Order By: Relevance
“…However, as pointed out in Section III, an increasing number of research efforts are finding that code structure significantly improves code summarization. Evidence from Alon et al [37], LeClair et al [40], [64], and Haque et al [43] all point to how code structure seems to help code summarization tools broadly classify code behavior, even if good internal documentation is required to produce detailed summaries. We surmise that a way structure manifests itself in summaries is via the action word, and therefore ask RQ 3 .…”
Section: A Research Questionsmentioning
confidence: 99%
“…However, as pointed out in Section III, an increasing number of research efforts are finding that code structure significantly improves code summarization. Evidence from Alon et al [37], LeClair et al [40], [64], and Haque et al [43] all point to how code structure seems to help code summarization tools broadly classify code behavior, even if good internal documentation is required to produce detailed summaries. We surmise that a way structure manifests itself in summaries is via the action word, and therefore ask RQ 3 .…”
Section: A Research Questionsmentioning
confidence: 99%
“…Automatic documentation has a large potential impact on how so ware is developed and maintained. Not only would automatic documentation reduce the time and energy programmers spend reading and writing so ware, having a high level summary available has been shown to improve results in other SE tasks such as code categorization and code search [22,28].…”
Section: Problem Significance Scopementioning
confidence: 99%
“…Code search [15,44,45,134,138], Code classification [30,74,154] code readability classification/prediction [105,117], Function type inferring [53,103] Code generation [35,115], Code Summarization [75,135], Code Decompilation [66,71] Code change generation [130], Data structure classification [108], Reverse execution [111] Design pattern detection [127], Technical debt detection [118], Story points prediction [21] Inconsistent method name refactoring [92], Stable patch detection [55] Defect Defect prediction [94,98,129,136,137,140], Vulnerability prediction [27,38,52,151] 8 24 Bug localization/detection [59,72,81,139,144,155] , Code repair [10,132,141] Code smell detection …”
Section: Codementioning
confidence: 99%