Effective Bug Triage And Using Techniques In Bug Data Reduction And Data Management In Bug Repositories

Ch. Kiranmai, K. Sobhana


The vast majority of the software organizations need to manage substantial number of programming bugs each day. Programming bugs are unavoidable and altering programming bugs is a costly assignment. A bug archive assumes a critical part in overseeing programming bugs. Programming organizations spend most if their cost in managing programming bugs. In programming improvement, programming vaults are substantial scale databases for putting away the yield of programming advancement, e.g., source code, messages, determinations and bugs. Customary programming investigation is not totally appropriate for the substantial scale and complex information in programming archives. In a bug archive bug is kept up as a bug report. Bug report incorporates all the literary depiction with respect to bugs and upgrade status of bug altering. The data put away in bug reports has two primary difficulties. Firstly the extensive scale information and furthermore low nature of information. Because of expansive number of day by day bugs reported, the quantity of bug reports is scaling up in the storehouse. Boisterous and repetitive bugs are debasing the nature of bug reports. A substantial number of every day reported bugs are put away in bug vaults. The way toward altering bug will be bug triage, which plans to allot a master engineer to another bug. In conventional programming new bugs are physically triaged by master engineer i.e. human triager. New techniques are being utilized every time. Human traiging was not a period worth process and was not effective on account of legitimate task of engineers .Nowadays the systems focus towards remedy task of the designer to the individual bug consequently. It will be a viable technique for the organizations who confronts the test of relegating the designer. In proposed framework we utilize a successful bug triage framework which will lessen the bug information to spare the work cost of engineers and enhance the quality to encourage the procedure of bug triage.


J. Anvik, L. Hiew, and G. C. Murphy, “Who should fix this bug?” in Proc. 28th Int. Conf. Softw. Eng., May 2006, pp. 361–370.

S. Artzi, A. Kie _ zun, J. Dolby, F. Tip, D. Dig, A. Paradkar, and M. D. Ernst, “Finding bugs in web applications using dynamic test generation and explicit-state model checking,” IEEE Softw., vol. 36, no. 4, pp. 474–494, Jul./Aug. 2010.

J. Anvik and G. C. Murphy, “Reducing the effort of bug report triage: Recommenders for development-oriented decisions,” ACM Trans. Soft. Eng. Methodol., vol. 20, no. 3, article 10, Aug. 2011.

C. C. Aggarwal and P. Zhao, “Towards graphical models for text processing,” Knowl. Inform. Syst., vol. 36, no. 1, pp. 1–21, 2013.

Bugzilla, (2014). [Online]. Avaialble: http://bugzilla.org/

K. Balog, L. Azzopardi, and M. de Rijke, “Formal models for expert finding in enterprise corpora,” in Proc. 29th Annu. Int. ACM SIGIR Conf. Res. Develop. Inform. Retrieval, Aug. 2006, pp. 43–50.

P. S. Bishnu and V. Bhattacherjee, “Software fault prediction using quad tree-based k-means clustering algorithm,” IEEE Trans. Knowl. Data Eng., vol. 24, no. 6, pp. 1146–1150, Jun. 2012.

H. Brighton and C. Mellish, “Advances in instance selection for instance-based learning algorithms,” Data Mining Knowl. Discovery, vol. 6, no. 2, pp. 153–172, Apr. 2002.

S. Breu, R. Premraj, J. Sillito, and T. Zimmermann, “Information needs in bug reports: Improving cooperation between developers and users,” in Proc. ACM Conf. Comput. Supported Cooperative Work, Feb. 2010, pp. 301–310.

V. Bolon-Canedo, N. S anchez-Marono, and A. Alonso-Betanzos, “A review of feature selection methods on synthetic data,” Knowl. Inform. Syst., vol. 34, no. 3, pp. 483–519, 2013.

Full Text: PDF [Full Text]


  • There are currently no refbacks.

Copyright © 2012, All rights reserved.| ijmca.org

Creative Commons License
International Journal of Mechanical Engineering and Computer Applications by chief editor is licensed under a Creative Commons Attribution 3.0 Unported License.Permissions beyond the scope of this license may be available at www.ijmca.org.