Sciweavers

173 search results - page 1 / 35
» Predicting the severity of a reported bug
Sort
View
MSR
2010
ACM
13 years 9 months ago
Predicting the severity of a reported bug
—The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bu...
Ahmed Lamkanfi, Serge Demeyer, Emanuel Giger, Bart...
SIGSOFT
2009
ACM
14 years 5 months ago
Improving bug triage with bug tossing graphs
A bug report is typically assigned to a single developer who is then responsible for fixing the bug. In Mozilla and Eclipse, between 37%-44% of bug reports are "tossed" ...
Gaeul Jeong, Sunghun Kim, Thomas Zimmermann
ISSTA
2012
ACM
11 years 7 months ago
Residual investigation: predictive and precise bug detection
We introduce the concept of “residual investigation” for program analysis. A residual investigation is a dynamic check installed as a result of running a static analysis that ...
Kaituo Li, Christoph Reichenbach, Christoph Csalln...
MSR
2010
ACM
13 years 6 months ago
Identifying security bug reports via text mining: An industrial case study
-- A bug-tracking system such as Bugzilla contains bug reports (BRs) collected from various sources such as development teams, testing teams, and end users. When bug reporters subm...
Michael Gegick, Pete Rotella, Tao Xie
ICSM
2009
IEEE
13 years 11 months ago
On predicting the time taken to correct bug reports in open source projects
Existing studies on the maintenance of open source projects focus primarily on the analyses of the overall maintenance of the projects and less on specific categories like the co...
Prasanth Anbalagan, Mladen A. Vouk