Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Detection of Duplicate Defect Reports Using Natural Language Processing
ICSE '07 Proceedings of the 29th international conference on Software Engineering
An approach to detecting duplicate bug reports using natural language and execution information
Proceedings of the 30th international conference on Software engineering
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Experiences on Analysis of Requirements Quality
ICSEA '08 Proceedings of the 2008 The Third International Conference on Software Engineering Advances
Automated support for managing feature requests in open forums
Communications of the ACM - A View of Parallel Computing
A discriminative model approach for accurate duplicate bug report retrieval
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Requirements elicitation in open source software development: a case study
Proceedings of the 3rd International Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development
HICSS '11 Proceedings of the 2011 44th Hawaii International Conference on System Sciences
Improved Duplicate Bug Report Identification
CSMR '12 Proceedings of the 2012 16th European Conference on Software Maintenance and Reengineering
The bug report duplication problem: an exploratory study
Software Quality Control
It's not a bug, it's a feature: how misclassification impacts bug prediction
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 0.00 |
While requirements for open source projects originate from a variety of sources like e.g. mailing lists or blogs, typically, they eventually end up as feature requests in an issue tracking system. When analyzing how these issue trackers are used for requirements evolution, we witnessed a high percentage of duplicates in a number of high-prole projects. Further investigation of six open source projects and their users led us to a number of important observations and a categorization of the root causes of these duplicates. Based on this, we propose a set of improvements for future issue tracking systems.