Browse > Article
http://dx.doi.org/10.9708/jksci.2014.19.9.103

Designing a Repository Independent Model for Mining and Analyzing Heterogeneous Bug Tracking Systems  

Lee, Jae-Kwon (Dept. of Computer Engineering, Chungbuk National University)
Jung, Woo-Sung (Dept. of Computer Engineering, Chungbuk National University)
Publication Information
Journal of the Korea Society of Computer and Information / v.19, no.9, 2014 , pp. 103-115 More about this Journal
Abstract
In this paper, we propose UniBAS(Unified Bug Analysis System) to provide a unified repository model by integrating the extracted data from the heterogeneous bug tracking systems. The UniBAS reduces the cost and complexity of the MSR(Mining Software Repositories) research process and enables the researchers to focus on their logics rather than the tedious and repeated works such as extracting repositories, processing data and building analysis models. Additionally, the system not only extracts the data but also automatically generates database tables, views and stored procedures which are required for the researchers to perform query-based analysis easily. It can also generate various types of exported files for utilizing external analysis tools or managing research data. A case study of detecting duplicate bug reports from the Firfox project of the Mozilla site has been performed based on the UniBAS in order to evaluate the usefulness of the system. The results of the experiments with various algorithms of natural language processing and flexible querying to the automatically extracted data also showed the effectiveness of the proposed system.
Keywords
Mining Software Repositories; Repository Independent Model; Bug Tracking System;
Citations & Related Records
연도 인용수 순위
  • Reference
1 C. Weiss, R. Premraj, T. Zimmermann, and A. Zeller, "How Long Will It Take to Fix This Bug?," Proc. 4th International Workshop on Mining Software Repositories, pp. 1-8, 2007.
2 H. M. Tran, C. Lange, G. Chulkov, J. Schönwälder, and M. Kohlhase, "Applying Semantic Techniques to Search and Analyze Bug Tracking Data," Journal of Network and Systems Management, vol. 17, no. 3, pp. 285-308, May. 2009.   DOI
3 M. Capraro, "Towards a Representative and Diverse Analysis of Issue-Tracker Related Code and Process Metrics," Friedrich-Alexander-University Erlangen-Nurnberg, Germany, 2013.
4 N. Kaushik and L. Tahvildari, "A Comparative Study of the Performance of IR Models on Duplicate Bug Detection," Proc. 16th European Conference on Software Maintenance and Reengineering, pp. 159-168, 2012.
5 H. P. Luhn, "The Automatic Creation of Literature Abstracts," IBM Journal of Research and Development, vol. 2, no. 2, pp. 159-165, 1958.   DOI
6 P. Runeson, M. Alexandersson, and O. Nyholm, "Detection of Duplicate Defect Reports Using Natural Language Processing," Proc. 29th International Conference on Software Engineering, pp. 499-510, 2007.
7 A. T. Nguyen, T. T. Nguyen, T. N. Nguyen, D. Lo, and C. Sun, "Duplicate bug report detection with a combination of information retrieval and topic modeling," Proc. 27th IEEE/ACM International Conference on Automated Software Engineering, pp. 70-79, 2012.
8 J. Zhou, H. Zhang, and D. Lo, "Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports," Proc. 34th International Conference on Software Engineering, pp. 14-24, 2012.
9 D. Kim, Y. Tao, S. Kim, and A. Zeller, "Where Should We Fix This Bug? A Two-Phase Recommendation Model," IEEE Transactions on Software Engineering, vol. 39, no. 11, pp. 1597-1610, Nov. 2013.   DOI   ScienceOn
10 D. Cubranic and G. C. Murphy, "Automatic bug triage using text categorization," Proc. 16th International Conference on Software Engineering & Knowledge Engineering, pp. 92-97, 2004.
11 J. Anvik, L. Hiew, and G. C. Murphy, "Who should fix this bug?," Proc. 28th International Conference on Software Engineering, pp. 361-370, 2006.
12 F. Servant and J. A. Jones, "WhoseFault: Automatic developer-to-fault assignment through fault localization," Proc. 34th International Conference on Software Engineering, pp. 36-46, 2012.
13 T. Zimmermann, R. Premraj, N. Bettenburg, S. Just, A. Schroter, and C. Weiss, "What Makes a Good Bug Report?," IEEE Transactions on Software Engineering, vol. 36, no. 5, pp. 618-643, Sep. 2010.   DOI   ScienceOn
14 N. Bettenburg, S. Just, A. Schroter, C. Weiss, R. Premraj, and T. Zimmermann, "Quality of bug reports in Eclipse," Proc. 5th OOPSLA Workshop on Eclipse Technology eXchange, pp. 21-25, 2007.
15 N. Bettenburg, S. Just, A. Schroter, C. Weiss, R. Premraj, and T. Zimmermann, "What makes a good bug report?," Proc. 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering, pp. 308-318, 2008.
16 N. Bettenburg, R. Premraj, T. Zimmermann, and S. Kim, "Extracting structural information from bug reports," Proc. 5th Working Conference on Mining Software Repositories pp. 27-30, 2008.