Skip to main content

BUGVILLA: Calibrating Bug Reports with Correlated Developers, Tracking Bug Reports, and Performance Analysis

  • Conference paper
  • First Online:
Intelligent System Design

Part of the book series: Advances in Intelligent Systems and Computing ((AISC,volume 1171))

  • 770 Accesses

Abstract

A bug is defined as the error in code because of which a system cannot produce the desired output. Whenever a bug occurs, a bug report is created. To find the cause of a bug, developers will execute the whole code continuously and analyze the code depending upon the report they received. So the bug reports should be accurate as the developers depend on the bug report received to solve a particular bug. Bug reports are the documents which provide total information of a particular bug with different accuracy. We need to manage the bugs which arise while working on a software project. Developers usually take the help of spreadsheets and fill them with new bugs which are raised. But when the list of bugs increases to a large number and all developers working on a single spreadsheet to update bugs may create ambiguity. Every software project reaches this point, especially during testing and deployment when users tend to find an application’s bugs. So, a tool for tracking bug reports will be useful instead of a spreadsheet. Where tracking bug reports is an important feature which helps to observe the activities of software developers. Moreover, it is important to observe that a bug will be assigned to the developer who is an expert in solving that particular type of developer. This paper introduces a new tool for tracking bug reports, using which we can assign bugs to their respective developers, view bug status, check bug history, check the total performance of developers, and also communicate with developers by means of a group chat.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 169.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 219.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

References

  1. Musale, K., & Gagare, G. (2015). Towards effective troubleshooting with data truncation. International Journal of Advanced Research in Computer and Communication Engineering, 4(11).

    Google Scholar 

  2. Xuan, B. J., Jiang, H., Hu, Y., Ren, Z., Zou, W., Luo, Z., & Wu, X. (2015). Towards effective bug triage with software data reduction techniques. IEEE Transactions on Knowledge and Data Engineering, 27(1).

    Google Scholar 

  3. Jadhava, A., & Jadhava, K. (2015). A survey on software data reduction techniques for effective bug triaging. International Journal of Computer Science and Information Technologies, 6(5), 4611–4612.

    Google Scholar 

  4. Pradeep, S., & Sharma, Y. K. (2019). A pragmatic evaluation of stress and performance testing for web applications. In IEEE Proceedings of AICAI (pp. 399–403), doi: 978-1-5386-9347-6.

    Google Scholar 

  5. Serrano, N., & Ciordia, I. (2005). Bugzilla, ITracker, and Other Bug Trackers. In Published in IEEE Software.

    Google Scholar 

  6. Avram, G., Sheehan, A., & Sullivan, D. K. (2008). Defect tracking systems in global software development-a work practice study. In Proceedings of the 2008 International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2008, Leipzig, Germany, Tuesday, May 13, 2008.

    Google Scholar 

  7. Zimmermann, T., Premraj, R., Bettenburg, N., Just, S., Schroter, A., & Weiss, C. (2010). What makes a good bug report? IEEE Transactions on Software Engineering, 36(5).

    Google Scholar 

  8. Xuan, J., He, J., Ren, Z., & Luo, J. Y. Z. (2019). Automatic bug triage using semisupervised text classification. Journal of Systems and Software, March 2019.

    Google Scholar 

  9. John, A., & Gail, M. (2011). Reducing the effort of bug report triage: Recommenders for development-oriented decisions. ACM Transactions on Software Engineering and Methodology, 20(3).

    Google Scholar 

  10. Krisztian, B. Leif, A., & Maarten, D. R. (2006). Formal models for expert finding in enterprise corpora. In 29th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval, Washington.

    Google Scholar 

  11. Zou, W., Hu, Y., Xuan, J., & Jiang, H. (2011). Towards training set reduction for bug triage. In IEEE 35th Annual Computer Software and Applications Conference, NJ.

    Google Scholar 

Download references

Future Work

In future scope, additional features will be leveraged like companies can have their own profile with a manager and group of developers. Also, an option of creating different group chats will be developed.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to G. Sreeram .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2021 Springer Nature Singapore Pte Ltd.

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Prasad, G.S., Kiran, D., Sreeram, G. (2021). BUGVILLA: Calibrating Bug Reports with Correlated Developers, Tracking Bug Reports, and Performance Analysis. In: Satapathy, S., Bhateja, V., Janakiramaiah, B., Chen, YW. (eds) Intelligent System Design. Advances in Intelligent Systems and Computing, vol 1171. Springer, Singapore. https://doi.org/10.1007/978-981-15-5400-1_56

Download citation

Publish with us

Policies and ethics