A case history analysis of software error cause-effect relationships
IEEE Transactions on Software Engineering
Orthogonal Defect Classification-A Concept for In-Process Measurements
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Learning from Our Mistakes with Defect Causal Analysis
IEEE Software
Evaluating Software Development Objectively
IEEE Software
A Case Study of Software Process Improvement During Development
IEEE Transactions on Software Engineering
Evolution in Open Source Software: A Case Study
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Experiences with defect prevention
IBM Systems Journal
Helping users avoid bugs in GUI applications
Proceedings of the 27th international conference on Software engineering
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
How long did it take to fix bugs?
Proceedings of the 2006 international workshop on Mining software repositories
Automatic Identification of Bug-Introducing Changes
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Measuring the evolution of open source software systems with their communities
ACM SIGSOFT Software Engineering Notes
An automated model-based debugging approach
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Towards a simplification of the bug report form in eclipse
Proceedings of the 2008 international working conference on Mining software repositories
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
A time-lag analysis for improving communication among OSS developers
JSAI-isAI'09 Proceedings of the 2009 international conference on New frontiers in artificial intelligence
Do crosscutting concerns cause modularity problems?
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Towards understanding software change request assignment: a survey with practitioners
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Hi-index | 0.00 |
As open source software products have evolved over time to satisfy a variety of demands from increasing users, they have become large and complex in general. Open source developers often face with challenges in fixing a considerable amount of bugs which are reported into a bug tracking system on a daily basis. As a result, the mean time to resolve bugs has been protracted in these days. In order to reduce the mean time to resolve bugs, managers/leaders of open source projects need to identify and understand the bottleneck of a bug modification process in their own projects. In this paper, we propose an analysis method which represents a bug modification process using a bug tracking system as a state transition diagram and then calculates the amount of time required to transit between states. We have conducted a case study using Firefox and Apache project data to confirm the usefulness of the analysis method. From the results of the case study, we have found that the method helped to reveal that both of the projects took a lot of time to verify results of bug modifications by developers.