International Journal of Engineering Research in Computer Science and Engineering (IJERCSE)

A Comparative Study of Bug Prediction Model in Software Engineering

Author : Ankita Rathore ¹ Dr. Anand Rajavat ²

Date of Publication :7th September 2016

Abstract: an issue model is an outlining model of something that could turn out seriously in the improvement or operation of a touch of apparatus. From the model, the originator or customer can then predict the results of this particular weakness. Issue models can be used as a piece of all branches of planning. Steady quality are a trademark typical for a system's prosperity, and can be used for condition checking and perceptive bolster This paper proposes using a re-order model of programming testing to assess the cost ampleness of test effort task methodology checking issue estimate results. Using unsupervised systems like batching is useful perspective for issue desire in programming modules In this paper we familiarize a gathering figuring on account of gathering programming modules together keeping the final objective to reduce reiteration. For a circumstance study applying inadequacy desire of a little structure to affirmation testing in the telecom business, results from our proliferation model showed that the best framework was to allow the test effort to compare [1].

Reference :

1. Steve Weber, “The success of open source”, Harvard University Press, 2009.
2. K Sowe Sulayman, G. Stamelos Ioannis, “Emerging free and open source software practices”, Idea Group Inc (IGI), 2008.
3. Martin Reddy, “API Design for C++”, Elsevier, 2011.
4. Nicolas Serrano, Ismael Ciordia, “Bugzilla, ITracker, and Other Bug Trackers”, IEEE software, Vol 22, pp. 11-13, 2005.
5. G Abaee, D.S. Guru, “Enhancement of Bug Tracking Tools; the Debugger”, Software Technology and Engineering (ICSTE), 2nd International Conference, Vol 1, 2010.
6. Thomas Zimmermann, Rahul Premraj, Jonathan Sillito, and Silvia Breu, “Improving Bug Tracking Systems”, 31th International Conference on Software Engineering , Vancouver, BC, Canada, 2009.
7. Nicholas Jalbert, Westley Weimer “Automated Duplicate Detection for Bug Tracking Systems” International Conference on Dependable Systems & Networks: Anchorage, Alaska, IEEE, 2008.
8. M. Pinzer Fischer, H. Gall “Populating a Release History Database from version control and bug tracking systems” Software Maintenance, IEEE, 2003.
9. S, Just, R. Premraj and T. Zimmermann. “Towards the next generation of bug tracking systems”, Visual Languages and Human-Centric Computing, IEEE, 2008.
10. M.P Francisco, P.B. Perez and G. Robles “Correlation between bug notifications, messages and participants in Debian's bug tracking system” Empirical Software Engineering and Measurement, First International Symposium, 2007.
11. A. Hora, N. Anquetil, S. Ducasse, M. Bhatti, C. Couto, M.T. Valente and J. Martins, “Bug Maps: A Tool for the Visual Exploration and Analysis of Bugs” Software Maintenance and Reengineering (CSMR), 16th European Conference, 2012.
12. Stephen Blair “A Guide to Evaluating a Bug Tracking System, White paper, 2004.