collaborative bug triaging
DESCRIPTION
This approach supports bug triaging on a multi-touch table to foster collaboration.TRANSCRIPT
![Page 1: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/1.jpg)
N/A
Katja Kevic, Sebastian C. Müller, Thomas Fritz, and Harald C. Gall
Collaborative Bug Triaging
CHASE ‘13, San Francisco – May 25, 2013
![Page 2: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/2.jpg)
Motivation
How to support developers for collaborative bug triaging?2
bug
bug
bug
bug bug
bug
![Page 3: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/3.jpg)
Related Work
• Source code analysis [e.g. MCDonald 2000]
• «One out of four bug reports required dicussion and negotiation..» [Carstensen, 1995]
3J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?,” in Proceedings of the 28th International Conference on Software Engineering, ICSE ’06.
D. W. McDonald and M. S. Ackerman, “Expertise recommender: a flexible recommendation system and architecture,” in Proceedings of the 2000 ACM Conference on Computer Supported Cooperative Work, CSCW ’00,
Carstensen, P. H., Sorensen, C. and Tuikka, T., Let's talk about bugs! Scandanavian Journal of Information Systems, 1995. 7,1 33-54.
• Information Retrieval or Machine Learning [e.g. Anvik 2006]
![Page 4: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/4.jpg)
Related Work
• Source code analysis [e.g. MCDonald 2000]
• «One out of four bug reports required dicussion and negotiation..» [Carstensen, 1995]
4J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?,” in Proceedings of the 28th International Conference on Software Engineering, ICSE ’06.
D. W. McDonald and M. S. Ackerman, “Expertise recommender: a flexible recommendation system and architecture,” in Proceedings of the 2000 ACM Conference on Computer Supported Cooperative Work, CSCW ’00,
Carstensen, P. H., Sorensen, C. and Tuikka, T., Let's talk about bugs! Scandanavian Journal of Information Systems, 1995. 7,1 33-54.
• Information Retrieval or Machine Learning [e.g. Anvik 2006]
![Page 5: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/5.jpg)
Collaborative Bug Triaging
Collaboration
IR + change set analysis
Allow change set investigation
5
![Page 6: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/6.jpg)
Information Retrieval – Finding
similar Bugs
0.78
0.72
0.71
cosine similarity
threshold
> 0.7
6
![Page 7: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/7.jpg)
Information Retrieval – Finding
similar Bugs
0.78
cosine similarity
threshold
7
> 0.75
![Page 8: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/8.jpg)
Information Retrieval – Finding
similar Bugs
0.78
0.72
0.71
cosine similarity
threshold
8
> 0.6
![Page 9: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/9.jpg)
Change Set Analysis – Finding Potential
Experts
0.71
0.78
0.72
5.46
1.44
4.28
9
Developer 1
Developer 2
Developer 3
7Change set 1
2Change set 2
2Change set 3
4Change set 4
Similar bug 1
Similar bug 2
Similar bug 3
![Page 10: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/10.jpg)
Prototype: Analysis
10
![Page 11: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/11.jpg)
Prototype: Context
11
![Page 12: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/12.jpg)
Collaboration
12
![Page 13: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/13.jpg)
Evaluation
• Applied in our own software projects
• Future work: user studies
13
![Page 14: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/14.jpg)
Summary
14
Collaboration
IR + change set analysis
Allow change set investigation
For more details visit:http://www.ifi.uzh.ch/seal/people/kevic/researchprojects/CollabBugTriaging.html
![Page 15: Collaborative Bug Triaging](https://reader036.vdocuments.us/reader036/viewer/2022081603/55896f90d8b42a807a8b470a/html5/thumbnails/15.jpg)
References
15
J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?,” inProceedings of the 28th International Conference on Software Engineering,ICSE ’06, (New York, NY, USA), pp. 361–370, ACM, 2006.
D. W. McDonald and M. S. Ackerman, “Expertise recommender: aflexible recommendation system and architecture,” in Proceedings ofthe 2000 ACM Conference on Computer Supported Cooperative Work,CSCW ’00, (New York, NY, USA), pp. 231–240, ACM, 2000.
Carstensen, P. H., Sorensen, C. and Tuikka, T., Let's talk about bugs! Scandanavian Journal of Information Systems, 1995. 7,1 33-54.