Open Access Open Access  Restricted Access Subscription or Fee Access

Role of Fault Reporting in Existing Software Industry

Sandeep Dalal, Rajender Chhillar


Fault is defined as any inappropriate behaviour of AUT (Application under Test) which could lead to the failure of the software. Fault detection and reporting goes in parallel and effective reporting of faults by tester means that the faults having high severity & priority are taken care appropriately and fixed by developer with quick turn around time & should not inject other faults, because most of the times fixing one fault injects other faults which are generally difficult to find due to lesser regression testing time and strict deadlines. This paper caters to the detailed analysis of fault reporting system which is the most important aspect of software testing life cycle & has direct impact on improvement of software quality. IFRS is proposed fault reporting system which identifies and defines all the elements of an ideal FRS which if followed will optimize the fault reporting, correction and validation process. If quality team can optimize the fault reporting process and report all the valid bugs in time, then it will certainly enhance the reliability of overall software system. A Survey was conducted among the different organizations to make a comparative analysis of fault reporting tools and to identify the major problems during fault reporting.


AUT (Application Under Test), Faults Detection, Fault Reporting, FRS (Fault Reporting System), IFRS (Ideal Fault Reporting System)

Full Text:



N. Battenberg, S. Just, S. Schroter, C. Weiss, R.Premraj and T. Zimmermann. “Quality of Bug Reports in Eclipse”, Proceedings of 2007

OOPSLA Workshop on Eclipse Technology Exchange (ETX), October 2007 .Retrieved on 06-06-2008. URL:

Kaner, C. "Effective Bug Reporting" (Tutorial Session) 15th International Software Quality Conference (Quality Week), San Francisco, CA, September 2002.

Vijayaraghavan, G., Kaner, C.. "Bugs in your shopping cart: A taxonomy.” 15th International Software Quality Conference (Quality Week), San Francisco, CA, 2002.

Shihab, E., Ihara, A., Kamei, Y., Ibrahim, W.M., Ohira, M., Adams, B.,Hassan, A.E., and Matsumoto, K. “Predicting Re-opened Bugs: A Case Study on the Eclipse Project.” In Proceedings of the 17th Working Conference on Reverse Engineering (2010), 249-258.

Hooimeijer, P. and Weimer, W. Modeling bug report quality. In Proceedings of the 22nd IEEE/ACM International Conference on Automated Software Engineering (2007), 34-43.

Panjer, L.D. “Predicting Eclipse Bug Lifetimes.” In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories (2007).

Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., and Zimmermann, T. What Makes a Good Bug Report? In FSE '08: Proceedings of the 16th International Symposium on Foundations of Software Engineering (November 2008).

E. Hendrickson. “Writing Effective bug reports”, Software Testing and Quality Engineering Magzine 2003.

Y.Z. Gong, “On software's defects,” Journal of Academy of Armored For Engineering, 2003, Vol.17, No.1, pp.60-63.

Grady, Robert B. “Software Failure Analysis for High-Return Process Improvement Decisions.” Hewlett-Packard Journal, 47(4) (August).

Anbalagan, P. and Vouk, M. “On Predicting the Time taken to Correct Bugs in Open Source Projects” (short paper). In ICSM '09: Proceedings of the International Conference on Software Maintenance (September 2009).

Breu, S., Premraj, R., Sillito, J., and Zimmermann, T. “Investigating Information Needs to Improve Cooperation Between Developers and Bug Reporters.” In CSCW '10: Proceedings of the ACM Conference on Computer Supported Cooperative Work (February 2010).

Menzies, T. and Marcus, A. “Automated severity assessment of software defect reports.” In ICSM '08: Proceedings of the 24th IEEE International Conference on Software Maintenance (September 2008), 346-355.

Weiss, C., Premraj, R., Zimmermann, T., and Zeller, A. “How Long Will It Take to Fix This Bug?” In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories (2007).

Elisabeth. “Writing Effective Bug Reports” Software Testing and Quality Engineering Magazine (2003).

Endres, A., “An Analysis of Errors and Their Causes in System Programs”, Proceedings of International Conference on Reliable Software pp 327-336(1975).

Ostrand,Thomas and Weyuker. "Collecting and Categorizing Software Error Data in an Industrial Environment." J. Syst. and Software 4, 11 (Nov. 1984), 289-300.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.