Issue Starvation in Software Development: A Case Study on the Redmine Issue Tracking System Dataset
Keywords:Dataset, Redmine, Issue Report, Issue Starvation, Mining Software Repository,
AbstractIn computing, starvation refers to the scenario when a process does not get required resources to complete its work. This mainly happens due to very simple priority based scheduling algorithms. Issues in software development require resources too and which issue will get the required resources depend on its priority. So the question is: Does starvation occur in Software Development too? The authors tried to answer the question with the help of their prepared dataset named as “Redmine Dataset”. Redmine is one of the popular web-based project management tool as well as an Issue Tracking Systems which also provide role-based access control. Currently, the Redmine ITS has more than 13000 issues and the number of issues is increasing time to time being. The authors have analyzed the Redmine dataset and found that starvation also occurred for issues in Software Development. The authors believe that this finding will steer the Software Engineering community for conducting research on advanced prioritization techniques which will resolve Issue starvation. Furthermore, the authors have provided few future research directions where this dataset can be used.
A. Silberschatz, P. B. Galvin, and G. Gagne, Operating System Principles. John Wiley & Sons, 2006.
M. Ortu, G. Destefanis, B. Adams, A. Murgia, M. Marchesi, and R. Tonelli, “The JIRA repository dataset: Understanding social aspects of software development,” in Proceedings of the 11th International Conference on Predictive Models and Data Analytics in Software Engineering, 2015, pp. 1-4.
A. Lamkanfi, J. Pérez, and S. Demeyer, “The eclipse and mozilla defect tracking dataset: a genuine dataset for mining bug information,” in Proceedings of the 10th Working Conference on Mining Software Repositories, 2013, pp. 203-206.
D. Spinellis, “A repository with 44 years of unix evolution,” in Proceedings of the 12th Working Conference on Mining Software Repositories, 2015, pp. 462-465.
J. Spolsky, “Painless Bug Tracking,” in Rock Star Developer News, 2000. Available at https://www.joelonsoftware.com/2000/11/08/ painless-bug-tracking/
J. Marini, Document Object Model. McGraw-Hill, Inc., 2002.
R. Verborgh, and M. De Wilde, Using OpenRefine. Packt Publishing Ltd., 2013.
B. S. Ainapure, Software Testing and Quality Assurance. Technical Publications, 2009.
P. Berander, and A. Andrews, “Requirements prioritization,” in Engineering and Managing Software Requirements, A. Aurum, and C. Wohlin, Eds. Springer, 2005, 69-94.
M. Rahim, M. Hasan, A. E. Chowdhury, and S. Das, “Software engineering practices and challenges in Bangladesh: A preliminary survey,” Journal Telecommunication, Electronic and Computer, submitted for publication.
B. Regnell, M. Höst, J. N. och Dag, P. Beremark, and T. Hjelm, “An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software,” Requirements Engineering, vol. 6, no. 1, pp. 51-62, 2001.
D. Leffingwell, and D. Widrig. Managing Software Requirements: A Unified Approach. Addison-Wesley Profesional, 2000.
J. Karlsson, and K. Ryan, “A cost-value approach for prioritizing requirements,” IEEE Software, vol. 14, no. 5, pp. 67-74, 1997.
K. Beck, Extreme Programming Explained: Embrace Change. Addison-Wesley Profesional, 2000.
How to Cite
TRANSFER OF COPYRIGHT AGREEMENT
The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):
- All proprietary right other than copyright, such as patent rights
- The right to make further copies of all or part of the published article for my use in classroom teaching
- The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
- The right to make copies of the published work for internal distribution within the institution that employs me
I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.