Mining Software Archives
Learning from History

[ Software Evolution | Vulnerable Components | Predicting Failures | Good Bug Reports | Related Changes | Cross-cutting Concerns | Usage Patterns | Jazz | Trends ]

What's new

• Our project "Mining Jazz Data to Assess Development Processes" got awarded US $25,000 Jazz Faculty Grant.
• One of the most popular German computer magazines (c't) covered Vulture, our vulnerability prediction tool (c't 2007, Issue 21, page 52)
• One of the most popular German computer magazines (c't) covered the BugCache algorithm (c't 2007, Issue 13, page 46)
• We have mined the Mozilla history to predict vulnerabilities.
  • Read the paper (Proc. Computer and Communications Security, Alexandria, Virginia)
• Our Eclipse bug data, listing the defect density of all Eclipse components, is now available for download.
• We have mined the Microsoft bug databases to predict component failures.
  • Read the paper (Proc. International Conference on Software Engineering, Shanghai)
  • Read the FAZ article: Wie anfällig wird "Vista"? (in German)
• Looking for the technical report on APFEL: "Fine-grained Processing of CVS Archives with APFEL"? Click here...
• Looking for the extended version of "Mining Version Archives for Co-changed Lines"? Click here...
• A paper on HAM and DynaMine has been selected for the Mining Challenge at MSR 2006 in Shanghai. Read the paper...
• Be warned: Don't program on Fridays! Why not? Read more...
• The eROSE plug-in for ECLIPSE that uses data mining to suggest related changes is available for download. Read more... or Download now...
• Subscribe to our announcement mailing list and you will be notified of new papers and downloads. Read more...

Projects

• Mining API Popularity: Which the the best API out there?
• AKTARI - Mining Trends in Software: Which is the best library versions to use? Check the choice of the majotiy!
• Mining Jazz Data: What is it that makes a good development process?
• Vulnerable components: Tell me what you import, and I'll tell you how vulnerable you are.
• Predicting component failures: What is it that makes software fail?
• Good bug reports: What makes a good bug report? Ask our CUEZILLA tool.
• Recommending related changes: You changed function foo(). What else do you need to change?
• Locating cross-cutting concerns in history: Which parts of your software do not align with the given modularization?
• Discovering usage patterns: How can we learn that a call to addWidget() should be followed by removeWidget()?

Software

• eROSE: Guiding Programmers in Eclipse

• Andreas Zeller (contact)
• Thomas Zimmermann
• Rahul Premraj
• Stephan Neuhaus