{ 0 comments }
ISSRE 2008 – International Symposium on Software Reliability Engineering
Seattle, 11th-14th November 2008
The International Symposium on Software Reliability Engineering (ISSRE) comes to Seattle. The conferences focuses on the practice and theory of software systems reliability engineering. ISSRE will provide an in-depth representation of both software reliability engineering (SRE) theory and experimentation. This year’s strong focus will be bridging the gap between academic research and industrial use of SRE techniques. Three keynote speakers from academia and industry will share their experience and vision of software reliability. Five carefully selected tutorials expose the attendees to the state-of-the-art of tools and techniques and in software reliability. Don’t miss ISSRE in Seattle – the conference dinner will be on the famous Space Needle in Seattle.
Registration is now open!
http://www.issre.org
{ 0 comments }
RSSE 2008 – Recommendation Systems for Software Engineering
Workshop at ACM SIGSOFT 2008 / FSE-16, November 10, Atlanta, GA, USA
Recommendation systems for software engineering are tools that help developers and managers to better cope with the huge amount of information faced in today’s software projects.
The goal of this workshop is to bring together researchers and practitioners with interest and experience in the elaboration and evaluation of concepts, techniques, and tools for providing recommendations to developers involved in software engineering tasks.
Registration is now open, for more details visit the RSSE 2008 homepage
{ 0 comments }
Welcome to my new Homepage.
Some technical things are still under construction (site-maps, SEO), but most of the contents are finished. Check out my research page or my publications (featuring abstracts for all and downloads for most of my papers).
It’s the fourth time that I try blogging. The first attempts were mostly personal diaries, not really interesting to anyone and very time-consuming to maintain. Also, I was not too happy with the blogging systems (Typepad, Blogger, Rotten Tomatoes). This time it will be different: I am blogging for my professional homepage. In addition, Wordpress is much easier to use and I purchased a professional theme (Thesis Theme). We will see how it goes.
{ 0 comments }
Other archived pages: index – publications – talks – activities – travel – news
{ 0 comments }
- Bug reports containing stack traces get fixed sooner. (APACHE/ECLIPSE/MOZILLA)
- Bug reports that are easier to read have lower lifetimes. (APACHE/ECLIPSE/MOZILLA)
- Including code samples in your bug report increases the chances of it getting fixed. (MOZILLA)
{ 0 comments }
Scrutinize is a web based tool designed to take information from a source code repository, and present it in a way that allows project team members to learn about how the project has been changing and who has made those changes. Try Scrutinize.
Scrutinize on Vimeo. Try Scrutinize.
{ 0 comments }
In software development, bug reports provide crucial information to developers. However, these reports widely differ in their quality. We conducted a survey among developers and users of APACHE, ECLIPSE, and MOZILLA to find out what makes a good bug report. The analysis of the 466 responses revealed an information mismatch between what developers need and what users supply. Most developers consider steps to reproduce, stack traces, and test cases as helpful, which are at the same time most difficult to provide for users. Such insight is helpful to design new bug tracking tools that guide users at collecting and providing more helpful information. Our CUEZILLA prototype is such a tool and measures the quality of new bug reports; it also recommends which elements should be added to improve the quality. We trained CUEZILLA on a sample of 289 bug reports, rated by developers as part of the survey. In our experiments, CUEZILLA was able to predict the quality of 31-48% of bug reports accurately.
{ 0 comments }
Lately, I have been using and shuffling tag clouds a lot in my presentations. Here is a YouTube video demonstrating this effect, followed by instructions on how to create the effect in Apple Keynote. Click here to download the source Keynote file.
{ 0 comments }
In a survey we found that most developers have experienced duplicated bug reports, however, only few considered them as a serious problem. This contradicts popular wisdom that considers bug duplicates as a serious problem for open source projects. In the survey, developers also pointed out that the additional information provided by duplicates helps to resolve bugs quicker. In this paper, we therefore propose to merge bug duplicates, rather than treating them separately. We quantify the amount of information that is added for developers and show that automatic triaging can be improved as well. In addition, we discuss the different reasons why users submit duplicate bug reports in the first place.
{ 0 comments }
