[Basili et al. 1994] Basili, V., G. Caldiera, and D.H. Rombach. 1994. The Goal Question Metric Paradigm. In Encyclopedia of Software Engineering, ed. J. Marciniak, 528–532. Hoboken, NJ: John Wiley & Sons, Inc.

[Basili et al. 1996] Basili, V., L. Briand, and W. Melo. 1996. A Validation of Object Oriented Design Metrics as Quality Indicators. IEEE Transactions on Software Engineering 22(10): 751–761.

[Basili et al. 1999] Basili, V., F. Shull, and F. Lanubile. 1999. Building Knowledge through Families of Experiments. IEEE Transactions on Software Engineering 25(4): 456–473.

[Bhat and Nagappan 2006] Bhat, T., and N. Nagappan. 2006. Building Scalable Failure-proneness Models Using Complexity Metrics for Large Scale Software Systems. Proceedings of the XIII Asia Pacific Software Engineering Conference: 361–366.

[Bird et al. 2009] Bird, C., et al. 2009. Putting It All Together: Using Socio-technical Networks to Predict Failures. Proceedings of the 20th IEEE international conference on software reliability engineering: 109–119.

[Boehm 1981] Boehm, B.W. 1981. Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, Inc.

[Borgatti et al. 2002] Borgatti, S., M.G. Everett, and L.C. Freeman. 2002. UCINET 6 for Windows: Software for Social Network Analysis. Harvard, MA: Analytic Technologies.

[Briand et al. 1999] Briand, L.C., J. Wuest, S. Ikonomovski, and H. Lounis. 1999. Investigating quality factors in object-oriented designs: an industrial case study. Proceedings of the 21st international conference on software engineering: 345–354.

[Brooks 1995] Brooks, F.P. 1995. The Mythical Man-Month, Anniversary Edition. Boston: Addison-Wesley.

[Chidamber and Kemerer 1994] Chidamber, S.R., and C.F. Kemerer. 1994. A Metrics Suite for Object Oriented Design. IEEE Transactions on Software Engineering 20(6): 476–493.

[Conway 1968] Conway, M.E. 1968. How Do Committees Invent? Datamation 14(4): 28–31.

[El Emam 2000] El Emam, K. 2000. A Methodology for Validating Software Product Metrics. Ottawa, Ontario, Canada: National Research Council of Canada.

[El Emam et al. 2001] El Emam, K., S. Benlarbi, N. Goel, and S.N. Rai. 2001. The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics. IEEE Transactions on Software Engineering 27(7): 630–650.

[Han and Kamber 2006] Han, J., and M. Kamber. 2006. Data Mining: Concepts and Techniques, Second Edition. San Francisco: Elsevier.

[Herbsleb and Grinter 1999] Herbsleb, J.D., and R.E. Grinter. 1999. Architectures, coordination, and distance: Conway’s Law and beyond. IEEE Software 16(5): 63–70.

[IEEE 1990] IEEE. 1990. IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology. New York: The Institute of Electrical and Electronics Engineers.

[ISO/IEC 1996] ISO/IEC. 1996. DIS 14598-1 Information Technology—Software Product Evaluation. International Organization for Standardization.

[Khoshgoftaar et al. 1996] Khoshgoftaar, T.M., E.B. Allen, N. Goel, A. Nandi, and J. McMullan. 1996. Detection of Software Modules with High Debug Code Churn in a Very Large Legacy System. Proceedings of the Seventh International Symposium on Software Reliability Engineering: 364.

[McCabe 1976] McCabe, T.J. 1976. A Complexity Measure. IEEE Transactions on Software Engineering 2(4): 308–320.

[Mockus et al. 2009] Mockus, A., N. Nagappan, and T.T. Dinh-Trong. 2009. Test Coverage and Post-verification Defects: A Multiple Case Study. Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement: 291–301.

[Nagappan and Ball 2005] Nagappan, N., and T. Ball. 2005. Use of Relative Code Churn Measures to Predict System Defect Density. Proceedings of the 27th international conference on software engineering: 284–292.

[Nagappan and Ball 2007] Nagappan, N., and T. Ball. 2007. Using Software Dependencies and Churn Metrics to Predict Field Failures: An Empirical Case Study. Proceedings of the First International Symposium on Empirical Software Engineering and Measurement: 364–373.

[Nagappan et al. 2006a] Nagappan, N., T. Ball, and A. Zeller. 2006. Mining metrics to predict component failures. Proceedings of the 28th international conference on software engineering: 452–461.

[Nagappan et al. 2006b] Nagappan, N., T. Ball, and B. Murphy. 2006. Using Historical In-Process and Product Metrics for Early Estimation of Software Failures. Proceedings of the 17th International Symposium on Software Reliability Engineering: 62–74.

[Nagappan et al. 2008] Nagappan, N., B. Murphy, and V. Basili. 2008. The Influence of Organizational Structure on Software Quality: An Empirical Case Study. Proceedings of the 30th international conference on software engineering: 521–530.

[Ostrand et al. 2004] Ostrand, T.J., E.J. Weyuker, and R.M. Bell. 2004. Where the Bugs Are. Proceedings of the 2004 ACM SIGSOFT international symposium on software testing and analysis: 86–96.

[Schröter et al. 2006] Schröter, A., T. Zimmermann, and A. Zeller. 2006. Predicting Component Failures at Design Time. Proceedings of the 2006 ACM/IEEE international symposium on empirical software engineering: 18–27.

[Tang et al. 1999] Tang, M.-H., M.-H. Kao, and M.-H. Chen. 1999. An empirical study on object-oriented metrics. Proceedings of the 6th International Symposium on Software Metrics: 242.

[von Mayrhauser et al. 1999] von Mayrhauser, A., J. Wang, M.C. Ohlsson, and C. Wohlin. 1999. Deriving a fault architecture from defect history. Proceedings of the 10th International Symposium on Software Reliability Engineering: 295.