C. Albert Thompson
Gail C. Murphy
Marc Palyart
Marko Gašparič
ABSTRACT
Software developers use issues as a means to describe a range of activities to be undertaken on a software system, including features to be added and defects that require fixing. When creating issues, software developers expend manual effort to specify relationships between issues, such as one issue blocking another or one issue being a sub-task of another. In particular, developers use a variety of relationships to express how work is to be broken down on a project. To better understand how software developers use work breakdown relationships between issues, we manually coded a sample of work breakdown relationships from three open source systems. We report on our findings and describe how the recognition of work breakdown relationships opens up new ways to improve software development techniques.
- Bugzilla. www.bugzilla.org. Accessed: 27/1/2016.Google Scholar
- Connect, project supporting health information exchange, www.connectopensource.org. Accessed: 27/1/2016.Google Scholar
- HBase.hbase.apache.org. Accessed: 27/1/2016.Google Scholar
- JIRA. www.atlassian.com/software/jira. Accessed: 27/1/2016.Google Scholar
- Mylyn. www.eclipse.org/mylyn. Accessed: 27/1/2016.Google Scholar
- J. Anvik, L. Hiew, and G. C. Murphy. Coping with an open bug repository. In OOPSLA Workshop on Eclipse Technology eXchange, pages 35--39, 2005. Google ScholarDigital Library
- S. Banerjee, J. Helmick, Z. Syed, and B. Cukic. Eclipse vs. mozilla: A comparison of two large-scale open source problem report repositories. In International Symposium on High Assurance Systems Engineering, pages 263--270, 2015. Google ScholarDigital Library
- N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj, and T. Zimmermann. What makes a good bug report? In The Joint Meeting of the European Software Engineering Conference and Symposium on The Foundations of Software Engineering, pages 308--318, 2008. Google ScholarDigital Library
- C. Bird, A. Bachmann, E. Aune, J. Duffy, A. Bernstein, V. Filkov, and P. Devanbu. Fair and balanced? bias in bug-fix datasets. In The Joint Meeting of the European Software Engineering Conference and Symposium on The Foundations of Software Engineering, 2009. Google ScholarDigital Library
- A. E. Hassan. Predicting faults using the complexity of code changes. In The International Conference on Software Engineering, pages 78--88, 2009. Google ScholarDigital Library
- M. Jankovic and M. Bajec. Comparison of software repositories for their usability in software process reconstruction. In The International Conference on Research Challenges in Information Science, pages 298--308, 2015.Google ScholarCross Ref
- A. J. Ko, B. A. Myers, and D. H. Chau. A linguistic analysis of how people describe software problems. In Visual Languages and Human-Centric Computing, pages 127--134, 2006. Google ScholarDigital Library
- A. Mockus, R. T. Fielding, and J. D. Herbsleb. Two case studies of open source software development: Apache and mozilla. Transactions on Software Engineering and Methodology, 11(3):309--346, 2002. Google ScholarDigital Library
- R. Moser, W. Pedrycz, and G. Succi. A comparative analysis of the efficiency of change metrics and static code attributes for defect prediction. In The International Conference on Software Engineering, pages 181--190, 2008. Google ScholarDigital Library
- G. Schermann, M. Brandtner, S. Panichella, P. Leitner, and H. Gall. Discovering loners and phantoms in commit and issue data. In The International Conference on Program Comprehension, 2015. Google ScholarDigital Library
- J. Śliwerski, T. Zimmermann, and A. Zeller. When do changes induce fixes? In The International Conference on Mining Software Repositories, pages 1--5, 2005. Google ScholarDigital Library
- A. Strauss and J. M. Corbin. Basics of qualitative research: Grounded theory procedures and techniques. Sage Publications, Inc., 1990.Google Scholar
- T. Zimmermann, N. Nagappan, H. Gall, E. Giger, and B. Murphy. Cross-project defect prediction: a large scale experiment on data vs. domain vs. process. In The Joint Meeting of the European Software Engineering Conference and Symposium on The Foundations of Software Engineering, pages 91--100, 2009. Google ScholarDigital Library
Recommendations
Early career software developers and work preferences in software engineering
AbstractContext: The software engineering researchers and practitioners echoed the need for investigations to better understand the engineers developing software and services. In light of current studies, there are significant associations between the ...
This study investigates the relationship between personality traits and work preferences of early career software engineers using data from 293 CS and SE practitioners/students. The clusters analysis and work preference questions found that cluster with ...
Issue ownership activity in two large software projects
Issue management is one of the major challenges of software development teams. Balanced workload allocation of developers who are responsible for the maintenance of the software product would impact the long-term reliability of the product. In this ...
Comments