Back to Current Issues

Software Engineering Domain Knowledge to Identify Duplicate Bug Reports

Dr.J.KEZIYA RANI, , , ,

Affiliations
ASST.PROFESSOR, DEPT.OF.CS&T, S.K.UNIVERSITY, ANANTHAPURAMU.

:under process

Abstract

Earlier, many methodologies was proposed for detecting duplicate bug reports by comparing the textual content of bug reports to subject-specific contextual material, namely lists of software-engineering terms, such as non-functional requirements and architecture keywords. When a bug report includes a word in these word-list contexts, the bug report is measured to be linked with that context and this information is likely to improve bug-deduplication methods. Here, we recommend a technique to partially automate the extraction of contextual word lists from software-engineering literature. Evaluating this software-literature context technique on real-world bug reports creates useful consequences that indicate this semi-automated method has the potential to significantly decrease the manual attempt used in contextual bug deduplication while suffering only a minor loss in accuracy.

Citation

Dr.J.KEZIYA RANI," Software Engineering Domain Knowledge to Identify Duplicate Bug Reports”, International Journal of Computer Engineering In Research Trends, 3(11):585-588,November-2016.

Keywords : software literature; duplicate bug reports; information retrieval; machine learning; documentation.

References

[1]	P. Runeson, M. Alexandersson, and O. Nyholm, “Detection of duplicate defect reports using natural language processing,” in Software Engineer-ing, 2007. ICSE 2007. 29th International Conference on. IEEE, 2007, pp. 499–510.

[2]	C. Sun, D. Lo, X. Wang, J. Jiang, and S.-C. Khoo, “A discriminative model approach for accurate duplicate bug report retrieval,” in Pro-ceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 1. ACM, 2010, pp. 45–54.

[3]	C. Sun, D. Lo, S.-C. Khoo, and J. Jiang, “Towards more accurate retrieval of duplicate bug reports,” in Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering. IEEE Computer Society, 2011, pp. 253–262.

[4]	A. Alipour, A. Hindle, and E. Stroulia, “A contextual approach towards more accurate duplicate bug report detection,” in Proceedings of the Tenth International Workshop on Mining Software Repositories. IEEE Press, 2013, pp. 183–192.

[5]	A. Alipour, “A contextual approach towards more accurate duplicate bug report detection,” Master’s thesis, University of Alberta, Fall 2013.

[6]	D. Han, C. Zhang, X. Fan, A. Hindle, K. Wong, and E. Stroulia, “Understanding android fragmentation with topic analysis of vendor-specific bugs,” in Reverse Engineering (WCRE), 2012 19th Working Conference on. IEEE, 2012, pp. 83–92.

[7]	R. S. Pressman and W. S. Jawadekar, “Software engineering,” New York 1992, 1987.

[8]	M. L. Murphy, The Busy Coder’s Guide to Advanced Android Develop-ment. CommonsWare, LLC, 2009.

[9]	N. Klein, C. S. Corley, and N. A. Kraft, “New features for duplicate bug detection.” in MSR, 2014, pp. 324–327.

[10]	N. Bettenburg, R. Premraj, T. Zimmermann, and S. Kim, “Duplicate bug reports considered harmful. . . really?” in Software Maintenance, 2008. ICSM 2008. IEEE International Conference on. IEEE, 2008, pp. 337–345.

[11]	N. Jalbert and W. Weimer, “Automated duplicate detection for bug tracking systems,” in Dependable Systems and Networks With FTCS and DCC, 2008. DSN 2008. IEEE International Conference on. IEEE, 2008, pp. 52–61.

[12]	Y. Dang, R. Wu, H. Zhang, D. Zhang, and P. Nobel, “Rebucket: A method for clustering duplicate crash reports based on call stack similarity,” in Proceedings of the 2012 International Conference on Software Engineering. IEEE Press, 2012, pp. 1084–1093.

[13]	A. Sureka and P. Jalote, “Detecting duplicate bug report using character n-gram-based features,” in Software Engineering Conference (APSEC), 2010 17th Asia Pacific. IEEE, 2010, pp. 366–374.

[14]	A. Lazar, S. Ritchey, and B. Sharif, “Improving the accuracy of duplicate bug report detection using textual similarity measures,” in Proceedings of the 11th Working Conference on Mining Software Repositories. ACM, 2014, pp. 308–311.

[15] A. Kiezun. Basic tutorial eclipse 3.1. [On-line]. Available: http://archive.eclipse.org/eclipse/downloads/drops/R-3. 1-200506271435/org.eclipse.jdt.doc.user.3.1.pdf.zip
[16] Sun Microsystems. (2008) Openoffice.org 3.0 developer’s guide. [Online]. Available:        https://wiki.openoffice.org/w/images/3/34/DevelopersGuide_ OOo3.0.0.odt 
[17]	Mozilla Developer Network and individual contributors. Mozilla developer guide. [Online]. Available: https://developer.mozilla.org/enUS/docs/Mozilla/Developer_guide

DOI Link : Not yet assigned

Download :

V3I1104.pdf

Refbacks : There are currently no refbacks

Support Us

We have kept IJCERT is a free peer-reviewed scientific journal to endorse conservation. We have not put up a paywall to readers, and we do not charge for publishing. But running a monthly journal costs is a lot. While we do have some associates, we still need support to keep the journal flourishing. If our readers help fund it, our future will be more secure.