2020
DOI: 10.1016/j.jss.2020.110567
|View full text |Cite
|
Sign up to set email alerts
|

Bug severity prediction using question-and-answer pairs from Stack Overflow

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
30
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 48 publications
(30 citation statements)
references
References 8 publications
0
30
0
Order By: Relevance
“…Y. Tan et al [37] proposed a novel approach for predicting severity. They linked the bug repositories post on stack overflows to the contents of Mozilla, Eclipse, and GCC bug reports.…”
Section: Volume XX 2020mentioning
confidence: 99%
“…Y. Tan et al [37] proposed a novel approach for predicting severity. They linked the bug repositories post on stack overflows to the contents of Mozilla, Eclipse, and GCC bug reports.…”
Section: Volume XX 2020mentioning
confidence: 99%
“…There are models that predict bug severity using textual description in bug reports [7,8,9,10,11,12,13,14]. Reference [7] carried out a comparison between the newly proposed bug and already existing bugs in the bug database using BM25-based document similarity function and then assigned the severity for the new reports based on the similarity calculated.…”
Section: Related Workmentioning
confidence: 99%
“…Reference [9] compiled improved versions of bug reports of Mozilla, Eclipse and GCC by integrating questions and the correspond answers from stack trace. Subsequently, they trained Naï ve Bayesian, k-Nearest Neighbor algorithm (KNN), and Long Short-Term Memory (LSTM) models to classify bug reports into severity levels.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations