{ 0 comments }
Far ahead of the pack:
- What Makes a Good Bug Report? – FSE 2008
Based on a survey of 466 developers and users, the paper reveals an information mismatch between what developers need and what users supply in bug reports. The paper is definitely one of my favorites for 2008 and also won an ACM SIGSOFT Distinguished Paper Award.
Fun fact: Google or Live search for “FSE 2008″ and the paper appears on the first page.
Runner-ups:
- Duplicate Bug Reports Considered Harmful… Really? – ICSM 2008
Duplicate bug reports often contain additional information that is not included in the original bug report. In this paper we quantified this extra information. - Towards the Next Generation of Bug Tracking Systems – VL/HCC 2008
This paper discusses frequent problems with bug reporting and present ideas on how to build better bug tracking systems. - Predicting Defects in SAP Java Code – ICSE 2009 SEIP
Technically not published until 2009, but many people search for papers accepted to ICSE since the program is not yet online. In this paper, we replicated several studies on defect prediction in SAP code and describe our experiences.
{ 0 comments }
Modern programming environments automatically collect lots of data on software development, notably changes and defects. The field of mining software archives deals with the automated extraction, collection, and abstraction of information from this data. This is the introduction to a special issue of IEEE Software on Mining Software Archives presenting a selection of the exciting research that is taking place in the field.
[click for table of contents]
[click for guest editor introduction]
{ 0 comments }
Since November 17, 2008, I am Researcher at Microsoft Research in Redmond, USA. However, I will keep my ties to University of Calgary as an Adjunct Assistant Professor. Check out my new homepage at Microsoft:
{ 1 comment }
Which components of a large software system are the most defect-prone? In a study on a large SAP Java system, we evaluated and compared a number of defect predictors, based on code features such as complexity metrics, static error detectors, change frequency, or component imports, thus replicating a number of earlier case studies in an industrial context. We found the overall predictive power to be lower than expected; still, the resulting regression models successfully predicted 50–60% of the 20% most defect-prone components.
{ 0 comments }
The International Workshop on Defects in Large Software Systems (DEFECTS 2009) will be collocated with ISSTA 2009. The workshop date will be July 19, 2009. Submission deadlines will be announced soon.
Update: The workshop web-page is now online: DEFECTS 2009
Submit papers by Monday, April 13, 2009.
{ 0 comments }
To find out more about our research on bug reports and bug tracking, visit Better Bug Tracking. Or read What Makes a Good Bug Report?
Most of this research was carried out at Saarland University, which did a (german) press release: Wie meldet man Software-Fehler korrekt?
And in case you missed Rahul’s talk at FSE 2008, here is his presentation:
Thanks to all the developers and users who participated in our survey.
{ 0 comments }
