skip to main content
research-article

Issue ownership activity in two large software projects

Published: 27 November 2012 Publication History

Abstract

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 paper, we analyse the issue report, issue ownership, and issue resolve patterns of two large software products over a period of time. We use GINI index to estimate the inequalities in issue ownership over time. Our results indicate that a small group of developers tends to take the ownership of a large portion of new issues especially when the active issue count is relatively high in the software development life cycle. We discuss the implications of this trend and propose long-term issue management strategies to deal with them.

References

[1]
Android Web Page, http://www.android.com/.
[2]
MSR 2012 Challenge Dataset, http://2012.msrconf.org/challenge.php.
[3]
Gartner Report on Third Quarter of Market Share: Mobile Communication Devices by Region and Country, 3Q11, 2011.
[4]
J. Anvik, L. Hiew, and G. C. Murphy. Who should fix this bug? In Proceedings of the International Conference on Software Engineering, pages 361--370, Shanghai, China, 2006.
[5]
J. Anvik and G. Murphy. Determining implementation expertise from bug reports. In Mining Software Repositories, 2007. ICSE Workshops MSR'07. Fourth International Workshop on, pages 1--8. IEEE, 2007.
[6]
J. Anvik and G. C. Murphy. Reducing the effort of bug report triage. ACM Transactions on Software Engineering and Methodology, 20(3):1--35, Aug. 2011.
[7]
A. Bakir, E. Kocaguneli, A. Tosun, A. Bener, and B. Turhan. Xiruxe: An Intelligent Fault Tracking Tool. AIPR09, Orlando, 2009.
[8]
V. Basili and D. Weiss. A methodology for collecting valid software engineering data. Software Engineering, IEEE Transactions on, (6):728--738, 1984.
[9]
N. Bettenburg and A. Hassan. Studying the Impact of Social Structures on Software Quality. In 2010 IEEE 18th International Conference on Program Comprehension, pages 124--133. IEEE, 2010.
[10]
E. Capra, C. Francalanci, and F. Merlo. An empirical study on the relationship between software design quality, development effort and governance in open source projects. IEEE Transactions on Software Engineering, 34(6):765--782, 2008.
[11]
D. Cubranic and G. Murphy. Automatic bug triage using text categorization. In Proceedings of the Sixteenth International Conference on Software Engineering Knowledge Engineering, pages 1--6. Citeseer, 2004.
[12]
J. L. Gastwirth. The Estimation of the Lorenz Curve and Gini Index. The Review of Economics and Statistics, 54(3):306--316, 1972.
[13]
E. Giger, M. Pinzger, and H. Gall. Predicting the Fix Time of Bugs. In RSSE '10 Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering, pages 52--56, 2010.
[14]
P. Guo, T. Zimmermann, N. Nagappan, and B. Murphy. Characterizing and predicting which bugs get fixed: An empirical study of Microsoft Windows. In Software Engineering, 2010 ACM/IEEE 32nd International Conference on, volume 1, pages 495--504. IEEE, 2010.
[15]
P. Guo, T. Zimmermann, N. Nagappan, and B. Murphy. Not my bug! and other reasons for software bug report reassignments. In Proceedings of the ACM 2011 conference on Computer supported cooperative work, pages 395--404. ACM, 2011.
[16]
S. Koch. Effort modeling and programmer participation in open source software projects. Information Economics and Policy, 20(4):345--355, Dec. 2008.
[17]
G. J. Myers, T. Badgett, T. Thomas, and C. Sandler. The Art of Software Testing. 2nd ed. John Wiley n& Sons, 2004.
[18]
A. Ngo-The and G. Ruhe. Optimized Resource Allocation for Software Release Planning. IEEE Transactions on Software Engineering, 35(1):109--123, 2009.
[19]
K. Petersen. Measuring and Predicting Software Productivity: A Systematic Map and Review. Information and Software Technology, 53(4):317--343, Dec. 2011.
[20]
H. Rittel and M. Webber. Dilemmas in a general theory of planning. Policy sciences, 4(2):155--169, 1973.
[21]
A. Tamrawi, T. Nguyen, and J. Al-Kofahi. Fuzzy set-based automatic bug triaging: NIER track. Proceedings of the 33rd International Conference on Software Engineering, pages 884--887, 2011.
[22]
X. Wang, L. Zhang, T. Xie, J. Anvik, and J. Sun. An Approach to Detecting Duplicate Bug Reports using Natural Language and Execution Information. In Proceedings of the 30th international conference on Software engineering, pages 461--470, 2008.
[23]
C. Weiss, R. Premraj, T. Zimmermann, and A. Zeller. How long will it take to fix this Bug? In Fourth International Workshop on Mining Software Repositories, 2007. ICSE Workshops MSR'07, number 2, 2007.
[24]
L. Williams, R. Kessler, W. Cunningham, and R. Jeffries. Strengthening the case for pair programming. Software, IEEE, 17(4):19--25, 2000.
[25]
K. Xu. How has the literature on GINI's Index evolved in the past 80 years. China Economic Quarterly, pages 1--41, 2003.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes  Volume 37, Issue 6
November 2012
191 pages
ISSN:0163-5948
DOI:10.1145/2382756
Issue’s Table of Contents
Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 27 November 2012
Published in SIGSOFT Volume 37, Issue 6

Check for updates

Author Tags

  1. issue ownership
  2. software issues
  3. software maintenance
  4. software quality

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)5
  • Downloads (Last 6 weeks)0
Reflects downloads up to 20 Jan 2025

Other Metrics

Citations

Cited By

View all
  • (2024)Examining ownership models in software teamsEmpirical Software Engineering10.1007/s10664-024-10538-529:6Online publication date: 27-Sep-2024
  • (2022)Classifying Fault Category and Severity of UAV Flight Controllers’ Reported Issues2022 6th International Conference on System Reliability and Safety (ICSRS)10.1109/ICSRS56243.2022.10067593(45-54)Online publication date: 23-Nov-2022
  • (2016)Towards semi-automated assignment of software change requestsJournal of Systems and Software10.1016/j.jss.2016.01.038115:C(82-101)Online publication date: 1-May-2016
  • (2015)The Art and Science of Analyzing Software DataundefinedOnline publication date: 15-Sep-2015
  • (2014)Factors affecting team evolution during software projectsProceedings of the 7th International Workshop on Cooperative and Human Aspects of Software Engineering10.1145/2593702.2593715(16-23)Online publication date: 2-Jun-2014
  • (2013)Emergence of developer teams in the collaboration network2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)10.1109/CHASE.2013.6614729(33-40)Online publication date: May-2013
  • (2013)Challenges and opportunities for software change request repositories: a systematic mapping studyJournal of Software: Evolution and Process10.1002/smr.163926:7(620-653)Online publication date: 16-Dec-2013

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media