ACM Home Page
Please provide us with feedback. Feedback
Predicting failures with developer networks and social network analysis
Full text PdfPdf (429 KB)
Source Foundations of Software Engineering archive
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering table of contents
Atlanta, Georgia
SESSION: Social structures table of contents
Pages 13-23  
Year of Publication: 2008
ISBN:978-1-59593-995-1
Authors
Andrew Meneely  North Carolina State University, Raleigh, NC
Laurie Williams  North Carolina State University, Raleigh, NC
Will Snipes  Nortel Networks, Research Triangle Park, NC
Jason Osborne  North Carolina State University, Raleigh, NC
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 20,   Downloads (12 Months): 247,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1453101.1453106
What is a DOI?

ABSTRACT

Software fails and fixing it is expensive. Research in failure prediction has been highly successful at modeling software failures. Few models, however, consider the key cause of failures in software: people. Understanding the structure of developer collaboration could explain a lot about the reliability of the final product. We examine this collaboration structure with the developer network derived from code churn information that can predict failures at the file level. We conducted a case study involving a mature Nortel networking product of over three million lines of code. Failure prediction models were developed using test and post-release failure data from two releases, then validated against a subsequent release. One model's prioritization revealed 58% of the failures in 20% of the files compared with the optimal prioritization that would have found 61% in 20% of the files, indicating that a significant correlation exists between file-based developer network metrics and failures.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Network Analysis: Methodological Foundations. Berlin: Springer, 2005.
 
2
Allen, T. J., Managing the Flow of Technology: MIT Press, 1977.
3
 
4
 
5
Barabasi, A.-L. and Albert, R., "Emergence of scaling in random networks," Science, vol. 286, no. 5439, pp. 509--512, 1999.
 
6
Barabasi, A.-L. and Oltvai, Z. N., "Network Biology: Understanding the Cell's Functional Organization," Nature Reviews Genetics, vol. 5, no. 2, pp. 101--113, 2004.
 
7
8
9
 
10
11
 
12
Gao, K. and Khoshgoftaar, T. M., "A Comprehensive Empirical Study of Count Models for Software Fault Prediction," Reliability, IEEE Transactions on, vol. 56, no. 2, pp. 223--236, June, 2007.
 
13
Girvan, M. and Newman, M. E. J., "Community Structure in Social and Biological Networks," The Proceedings of the National Academy of Sciences, vol. 99, no. 12, pp. 7821--7826, 2001.
 
14
Gonzales-Barahona, J. M., Lopez-Fernandez, L., and Robles, G., "Applying Social Network Analysis to the Information in CVS Repositories," in 2005 International Workshop on Mining Software Repositories, 2004.
15
 
16
 
17
Lave, J. and Wenger, E., Situated Learning: Legitimate Peripheral Participation. Cambridge: Cambridge University Press, 1991.
 
18
Mockus, A. and Weiss, D. M., "Predicting Risk of Software Changes," Bell Labs Technical Journal, vol. 5, pp. 169--180, 2002.
 
19
20
21
22
23
24
 
25
 
26
27
 
28


Collaborative Colleagues:
Andrew Meneely: colleagues
Laurie Williams: colleagues
Will Snipes: colleagues
Jason Osborne: colleagues