Nothing Special   »   [go: up one dir, main page]

skip to main content
10.5555/2337223.2337227acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

Developer prioritization in bug repositories

Published: 02 June 2012 Publication History

Abstract

Developers build all the software artifacts in development. Existing work has studied the social behavior in software repositories. In one of the most important software repositories, a bug repository, developers create and update bug reports to support software development and maintenance. However, no prior work has considered the priorities of developers in bug repositories. In this paper, we address the problem of the developer prioritization, which aims to rank the contributions of developers. We mainly explore two aspects, namely modeling the developer prioritization in a bug repository and assisting predictive tasks with our model. First, we model how to assign the priorities of developers based on a social network technique. Three problems are investigated, including the developer rankings in products, the evolution over time, and the tolerance of noisy comments. Second, we consider leveraging the developer prioritization to improve three predicted tasks in bug repositories, i.e., bug triage, severity identification, and reopened bug prediction. We empirically investigate the performance of our model and its applications in bug repositories of Eclipse and Mozilla. The results indicate that the developer prioritization can provide the knowledge of developer priorities to assist software tasks, especially the task of bug triage.

References

[1]
J. Anvik, L. Hiew, and G.C. Murphy, "Who Should Fix This Bug?," Proc. 28th Intl. Conf. Software Engineering (ICSE'06), May 2006, pp. 361-370.
[2]
J. Anvik and G.C. Murphy, "Reducing the Effort of Bug Report Triage: Recommenders for Development-Oriented Decisions," ACM Trans. Software Engineering & Methodology, vol.20, no.3, Aug. 2011.
[3]
C. Bird, A. Gourley, P. Devanbu, M. Gertz and A. Swaminathan, "Mining Email Social Networks," Proc. 3rd Intl. Workshop Mining Software Repositories (MSR'06), May 2006, pp.137-143.
[4]
N. Bettenburg and A.E. Hassan, "Studying the Impact of Social Structures on Software Quality," Proc. IEEE 18th Intl. Conf. Program Comprehension (ICPC'10), Jun. 2010, pp.124-133.
[5]
A. Begel, Y.P. Khoo, and T. Zimmermann, "Codebook: Discovering and Exploiting Relationships in Software Repositories," Proc. 32nd Intl. Conf. Software Engineering (ICSE'10), May 2010, pp. 125-134.
[6]
P. Bhattacharya and I. Neamtiu, "Fine-Grained Incremental Learning and Multi-Feature Tossing Graphs to Improve Bug Triaging," Proc. 26th IEEE Intl. Conf. Software Maintenance (ICSM'10), Sept. 2010, pp. 1-10.
[7]
C. Bird, N. Nagappan, H. Gall, B. Murphy, and P. Devanbu, "Putting it All Together: Using Socio-Technical Networks to Predict Failures," Proc. 20th Intl. Symp. Software Reliability Engineering (ISSRE'09), Nov. 2009, pp.109-119.
[8]
C. Bird, D. Pattison, R. D'Souza, V. Filkov and P. Devanbu, "Latent Social Structure in Open Source Projects," Proc. 16th ACM SIGSOFT Intl. Symp. Foundations of software engineering (FSE'08), Nov. 2008, pp.24-35.
[9]
N. Bettenburg, R. Premraj, T. Zimmermann, and S. Kim, "Duplicate Bug Reports Considered Harmful... Really?," Proc. 24th IEEE Intl. Conf. Software Maintenance (ICSM'08), Sept. 2008, pp. 337-345.
[10]
D. ¿ubranic and G.C. Murphy, "Automatic Bug Triage Using Text Categorization," Proc. 16th Intl. Conf. Software Engineering & Knowledge Engineering (SEKE'04), Jun. 2004, pp. 92-97.
[11]
T. DeMarco and T. Lister, Peopleware: Productive Projects and Teams, 2nd ed. Dorset House, New York, 1999.
[12]
Eclipse. http://eclipse.org/.
[13]
M. Fischer, M. Pinzger and H. Gall, "Analyzing and Relating Bug Report Data for Feature Tracking," Proc. 10th Working Conf. Reverse Engineering (WCRE'03), Nov. 2003, pp. 90-101.
[14]
M. Gegick, P. Rotella, and T. Xie, "Identifying Security Bug Reports via Text Mining: An Industrial Case Study," Proc. 7th IEEE Working Conf. Mining Software Repositories (MSR'10), May 2010, pp. 11-20.
[15]
P.J. Guo, T. Zimmermann, N. Nagappan, and B. Murphy, "Characterizing and Predicting Which Bugs Get Fixed: An Empirical Study of Microsoft Windows," Proc. 32nd Intl. Conf. Software Engineering (ICSE'10), May 2010, pp. 495-504.
[16]
A.E. Hassan, "The Road Ahead for Mining Software Repositories," Proc. Frontiers of Software Maintenance (FoSM '08), Sept. 2008, pp. 48-57.
[17]
Q. Hong, S. Kim, S.C. Cheung, and C. Bird, "Understanding a Developer Social Network and its Evolution," Proc. 27th IEEE Intl. Conf. Software Maintenance (ICSM'11), Sept. 2011, pp. 323-332.
[18]
P. Hooimeijer and W. Weimer, "Modeling Bug Report Quality," Proc. 22nd IEEE/ACM Intl. Conf. Automated Software Engineering (ASE'07), Nov. 2007, pp. 34-43.
[19]
G. Jeong, S. Kim, and T. Zimmermann, "Improving Bug Triage with Tossing Graphs," Proc. 17th ACM SIGSOFT Symp. Foundations of Software Engineering (FSE'09), Aug. 2009, pp. 111-120.
[20]
A. Lamkanfi, S. Demeyer, E. Giger, and B. Goethals, "Predicting the Severity of a Reported Bug," Proc. 7th IEEE Working Conf. Mining Software Repositories (MSR'10), May 2010, pp. 1-10.
[21]
L. Lü, Y.-C. Zhang, C.H. Yeung, and T. Zhou, "Leaders in Social Networks, the Delicious Case," PLoS One, vol. 6, no. 6, Jun. 2011.
[22]
Mozilla. http://mozilla.org/.
[23]
T. Menzies and A. Marcus, "Automated Severity Assessment of Software Defect Reports," Proc. IEEE Conf. Software Maintenance (ICSM'08), Sept. 2008, pp. 346-355.
[24]
A. Meneely and L. Williams, "Socio-Technical Developer Networks: Should We Trust Our Measurements?," Proc. 33rd Intl. Conf. Software Engineering (ICSE'11), May 2011, pp. 281-290.
[25]
A. Meneely, L. Williams, W. Snipes, and J. Osborne, "Predicting Failures with Deverloper Networks and Social Network Analysis," Proc. 16th ACM SIGSOFT Intl. Symp. Foundations of Software Engineering (FSE'08), Nov. 2008, pp. 13-23.
[26]
J.-W. Park, M.-W. Lee, J. Kim, S.-W. Hwang, and S. Kim, "CosTriage: A Cost-Aware Triage Algorithm for Bug Reporting Systems," Proc. 25th Conf. Artificial Intelligence (AAAI'11), Aug. 2011, pp. 139-144.
[27]
M. Pinzger, N. Nagappan, and B. Murphy, "Can Developer-Module Networks Predict Failures?," Proc. 16th ACM SIGSOFT Intl. Symp. Foundations of Software Engineering (FSE'08), Nov. 2008, pp. 2-12.
[28]
P. Runeson, M. Alexandersson, and O. Nyholm, "Detection of Duplicate Defect Reports Using Natural Language Processing," Proc. Intl. Conf. Software Engineering (ICSE'07), May 2007, pp. 499-510.
[29]
S. Rastkar, G.C. Murphy, and G. Murray, "Summarizing Software Artifacts: A Case Study of Bug Reports," Proc. 32nd Intl. Conf. Software Engineering (ICSE'10), May 2010, pp. 505-514.
[30]
E. Shihab, A. Ihara, Y. Kamei, W.M. Ibrahim, M. Ohira, B. Adams, A.E. Hassan, and K. Matsumoto, "Predicting Re-opened Bugs: A Case Study on the Eclipse Project," Proc. 17th Working Conf. Reverse Engineering (WCRE'10), Oct. 2010, pp. 249-258.
[31]
C. Sun, D. Lo, X. Wang, J. Jiang, and S.-C. Khoo, "A Discriminative Model Approach for Accurate Duplicate Bug Report Retrieval," Proc. 32nd Intl. Conf. Software Engineering (ICSE'10), May 2010, pp. 45-54.
[32]
A. Tamrawi, T.T. Nguyen, J.M. Al-Kofahi, and T.N. Nguyen, "Fuzzy-Set and Cache-Based Approach for Bug Triaging," Proc. 19th ACM SIGSOFT Symp. Foundations of Software Engineering (FSE'11), Sept. 2011, pp. 365-375.
[33]
I.H. Witten, E. Frank, and M.A. Hall, Data Mining: Practical Machine Learning Tools and Techniques, 3rd ed. Morgan Kaufmann, Burlington, MA, 2011.
[34]
T. Wolf, A. Schröter, D. Damian, and T. Nguyen, "Predicting Build Failures Using Social Network Analysis on Developer Communication," Proc. 31st Intl. Conf. Software Engineering (ICSE'09), May 2009, pp. 1-11.
[35]
X. Wang, L. Zhang, T. Xie, J. Anvik, and J. Sun, "An Approach to Detecting Duplicate Bug Reports Using Natural Language and Execution Information," Proc. 30th Intl. Conf. Software Engineering (ICSE'08), May 2008, pp. 461-470.
[36]
J. Xiao and W. Afzal, "Search-based Resource Scheduling for Bug Fixing Tasks," Proc. 2nd Intl. Symp. Search Based Software Engineering (SSBSE'10), Sept. 2010, pp. 133-142.
[37]
J. Xuan, H. Jiang, Z. Ren, Z. Luo, "Solving the Large Scale Next Release Problem with a Backbone Based Multilevel Algorithm," IEEE Trans. Software Engineering, preprint.
[38]
J. Xuan, H. Jiang, Z. Ren, J. Yan, and Z. Luo, "Automatic Bug Triage Using Semi-Supervised Text Classification," Proc. 22th Intl. Conf. Software Engineering & Knowledge Engineering (SEKE'10), Jul. 2010, pp. 209-214.
[39]
W. Zou, Y. Hu, J. Xuan, and H. Jiang. "Towards Training Set Reduction for Bug Triage," Proc. 35th Annual IEEE Intl. Computer Software and Applications Conference (COMPSAC'11), Jul. 2011, pp. 576-581.
[40]
T. Zimmermann, R. Premraj, N. Bettenburg, S. Just, A. Schröter, and C. Weiss, "What Makes a Good Bug Report?," IEEE Trans. Software Engineering, vol. 36, no.5, Oct. 2010, pp. 618-643.

Cited By

View all
  • (2022)Context- and Fairness-Aware In-Process Crowdworker RecommendationACM Transactions on Software Engineering and Methodology10.1145/348757131:3(1-31)Online publication date: 7-Mar-2022
  • (2020)Profiling Developers Through the Lens of Technical DebtProceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)10.1145/3382494.3422172(1-6)Online publication date: 5-Oct-2020
  • (2019)A comparison of bugs across the iOS and Android platforms of two open source cross platform browser appsProceedings of the 6th International Conference on Mobile Software Engineering and Systems10.5555/3340730.3340748(76-86)Online publication date: 25-May-2019
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '12: Proceedings of the 34th International Conference on Software Engineering
June 2012
1657 pages
ISBN:9781467310673

Sponsors

Publisher

IEEE Press

Publication History

Published: 02 June 2012

Check for updates

Qualifiers

  • Article

Conference

ICSE '12
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)4
  • Downloads (Last 6 weeks)1
Reflects downloads up to 19 Nov 2024

Other Metrics

Citations

Cited By

View all
  • (2022)Context- and Fairness-Aware In-Process Crowdworker RecommendationACM Transactions on Software Engineering and Methodology10.1145/348757131:3(1-31)Online publication date: 7-Mar-2022
  • (2020)Profiling Developers Through the Lens of Technical DebtProceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)10.1145/3382494.3422172(1-6)Online publication date: 5-Oct-2020
  • (2019)A comparison of bugs across the iOS and Android platforms of two open source cross platform browser appsProceedings of the 6th International Conference on Mobile Software Engineering and Systems10.5555/3340730.3340748(76-86)Online publication date: 25-May-2019
  • (2019)Towards Issue Recommendation for Open Source CommunitiesIEEE/WIC/ACM International Conference on Web Intelligence10.1145/3350546.3352514(164-171)Online publication date: 14-Oct-2019
  • (2019)Bisecting commits and modeling commit risk during testingProceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3338906.3338944(279-289)Online publication date: 12-Aug-2019
  • (2019)DeepTriageProceedings of the ACM India Joint International Conference on Data Science and Management of Data10.1145/3297001.3297023(171-179)Online publication date: 3-Jan-2019
  • (2019)Mining historical test logs to predict bugs and localize faults in the test logsProceedings of the 41st International Conference on Software Engineering10.1109/ICSE.2019.00031(140-151)Online publication date: 25-May-2019
  • (2019)Towards prioritizing user-related issue reports of mobile applicationsEmpirical Software Engineering10.1007/s10664-019-09684-y24:4(1964-1996)Online publication date: 1-Aug-2019
  • (2018)Be careful of when: an empirical study on time-related misuse of issue tracking dataProceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3236024.3236054(307-318)Online publication date: 26-Oct-2018
  • (2018)Fuzzy Clustering of Crowdsourced Test Reports for AppsACM Transactions on Internet Technology10.1145/310616418:2(1-28)Online publication date: 2-Feb-2018
  • Show More Cited By

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media