Sciweavers

47 search results - page 1 / 10
» Summarizing software artifacts: a case study of bug reports
Sort
View
ICSE
2010
IEEE-ACM
13 years 9 months ago
Summarizing software artifacts: a case study of bug reports
Many software artifacts are created, maintained and evolved as part of a software development project. As software developers work on a project, they interact with existing projec...
Sarah Rastkar, Gail C. Murphy, Gabriel Murray
MSR
2010
ACM
13 years 7 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
WCRE
2010
IEEE
13 years 3 months ago
Predicting Re-opened Bugs: A Case Study on the Eclipse Project
—Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be...
Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid ...
MSR
2009
ACM
13 years 11 months ago
Assigning bug reports using a vocabulary-based expertise model of developers
For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment...
Dominique Matter, Adrian Kuhn, Oscar Nierstrasz
ICSE
2010
IEEE-ACM
13 years 7 months ago
Managing iterations with UNICASE
Planning iterations in software projects requires considering artifacts from different aspects such as requirements, specifications, tasks or even bug reports. UNICASE is a unifie...
Jonas Helming, Maximilian Koegel