Sciweavers

173 search results - page 5 / 35
» Predicting the severity of a reported bug
Sort
View
77
Voted
HICSS
2005
IEEE
126views Biometrics» more  HICSS 2005»
15 years 3 months ago
Exploring Usability Discussions in Open Source Development
The public nature of discussion in open source projects provides a valuable resource for understanding the mechanisms of open source software development. In this paper we explore...
Michael B. Twidale, David M. Nichols
87
Voted
ECLIPSE
2005
ACM
15 years 6 days ago
Coping with an open bug repository
Most open source software development projects include an open bug repository—one to which users of the software can gain full access—that is used to report and track problems...
John Anvik, Lyndon Hiew, Gail C. Murphy
77
Voted
SIGSOFT
2009
ACM
15 years 11 months ago
Fair and balanced?: bias in bug-fix datasets
Software engineering researchers have long been interested in where and why bugs occur in code, and in predicting where they might turn up next. Historical bug-occurence data has ...
Christian Bird, Adrian Bachmann, Eirik Aune, John ...
70
Voted
EUROSYS
2009
ACM
15 years 7 months ago
First-aid: surviving and preventing memory management bugs during production runs
Memory bugs in C/C++ programs severely affect system availability and security. This paper presents First-Aid, a lightweight runtime system that survives software failures caused ...
Qi Gao, Wenbin Zhang, Yan Tang, Feng Qin
63
Voted
MSR
2006
ACM
15 years 4 months ago
Where is bug resolution knowledge stored?
ArgoUML uses both CVS and Bugzilla to keep track of bugfixing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by i...
Gerardo Canfora, Luigi Cerulo