Your SlideShare is downloading. ×
  • Like
Knowledge Collaboration by Mining Software Repositories
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Knowledge Collaboration by Mining Software Repositories

  • 1,209 views
Published

Presented at KCSD 2006.

Presented at KCSD 2006.

Published in Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,209
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
26
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Knowledge Collaboration by Mining Software Repositories Tom Zimmermann Saarland University, Saarbrücken, Germany
  • 2. Guiding developers Zimmermann, Weissgerber, Diehl, Zeller (TSE 2005)
  • 3. eROSE suggests further locations.
  • 4. eROSE prevents incomplete changes.
  • 5. eROSE is customizable.
  • 6. “Indirect” collaboration Direct collaboration Version archive
  • 7. “Indirect” collaboration Direct collaboration Version archive Mining Hidden Knowledge
  • 8. “Indirect” collaboration Direct collaboration Indirect Version collaboration archive Mining Hidden Knowledge
  • 9. Future
  • 10. #1: Change classification
  • 11. #1: Change classification bad changes (e.g., from bug database) X X X X
  • 12. #1: Change classification BUILD A CLASSIFIER bad changes (e.g., from bug database) X X X X
  • 13. #1: Change classification BUILD A CLASSIFIER bad changes (e.g., from bug database) X X X X new change
  • 14. #1: Change classification BUILD A CLASSIFIER bad changes (e.g., from bug database) X X X X new change PREDICT QUALITY
  • 15. #2: What should we collect • Mining software repositories relied on exiting repositories so far. • Collecting new data (e.g., navigation traces) opens new opportunities. • Software(ICSM 2005), DeLine et al. (VL/HCC 2005) Navigation Singer et al • Socialet al. (TagSea tool) Tagging Storey
  • 16. Mining across projects
  • 17. #3: Mining across projects • Extend source code search engines with mining techniques. • Large scale mining (129,167 SF projects) and large scale collaboration (1,393,250 SF users). • Usage Pei (MSR 2006) Koders.com patterns from Xie and
  • 18. Conclusion • History supports knowledge collaboration. • Future challenges: granularity and data. • Mining software repositories @ ASE 2006: − Wednesday 4pm: Impact analysis − Friday 9am: Management − Friday 11am: Mining software repositories