An empirical study of refactoring challenges and benefits at Microsoft

IEEE Transactions on Software Engineering

Volumn 40, Issue 7, 2014, Pages 633-649

  Kim, Miryung ^a   Zimmermann, Thomas ^b   Nagappan, Nachiappan ^b  

^a The University of Texas at Austin   (United States)

^b MICROSOFT RESEARCH   (United States)

Author keywords

churn; component dependencies; defects; empirical study; Refactoring; software evolution

Indexed keywords

COMPUTER SOFTWARE SELECTION AND EVALUATION; COSINE TRANSFORMS; DEFECTS; SEMANTICS;

CHURN; COMPONENT DEPENDENCIES; EMPIRICAL STUDIES; REFACTORINGS; SOFTWARE EVOLUTION;

SURVEYS;

EID: 84904311708     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.2014.2318734     Document Type: Article

References (58)

1. M. Fowler, Refactoring: Improving the Design of Existing Code. Reading, MA, USA: Addison-Wesley, 2000.
2. L. A. Belady and M. Lehman, "A model of large program development," IBM Syst. J., vol. 15, no. 3, pp. 225-252, 1976.
3. K. Beck, Extreme Programming Explained, Embrace Change. Reading, MA, USA: Addison-Wesley, 2000.
4. W. Opdyke, Refactoring, Reuse & Reality, Lucent Technologies, Murray Hill, NJ, USA, 1999.
5. J. Ratzinger, T. Sigmund, and H. C. Gall, "On the relation of refactorings and software defect prediction," in Proc. ACM Int. Working Conf. Mining Softw. Repositories, 2008, pp. 35-38.
6. P. Weißgerber and S. Diehl, "Are refactorings less error-prone than other changes?" in Proc. ACM Int. Workshop Mining Softw. Repositories, 2006, pp. 112-118.
7. P. Weißgerber and S. Diehl, "Identifying refactorings from sourcecode changes," in Proc. 21st IEEE/ACM Int. Conf. Autom. Softw. Eng., 2006, pp. 231-240.
8. C. Görg and P. Weißgerber, "Error detection by refactoring reconstruction," in Proc. Int. Workshop Mining Softw. Repositories, 2005, pp. 1-5.
9. M. Kim, D. Cai, and S. Kim, "An empirical investigation into the role of refactorings during software evolution," in Proc. ACM IEEE 33rd Int. Conf. Softw. Eng., 2011, pp. 151-160.
10. T. Mens and T. Tourwe, "A survey of software refactoring," IEEE Trans. Softw. Eng., vol. 30, no. 2, pp. 126-139, Feb. 2004.
11. T. Hastie, R. Tibshirani, and J. H. Friedman, The Elements of Statistical Learning: Data Mining, Inference, and Prediction. New York, NY, USA: Springer-Verlag, 2001.
12. M. Kim, T. Zimmermann, and N. Nagappan, "Appendix to a field study of refactoring rationale, benefits, and challenges at microsoft," Microsoft Res., Tech. Rep. MSR-TR-2012-4, Redmond, WA, USA, 2012.
13. R. Johnson, "Beyond behavior preservation," Microsoft Faculty Summit 2011, Invited Talk, Jul. 2011.
14. Y. Brun, R. Holmes, M. D. Ernst, and D. Notkin, "Proactive detection of collaboration conflicts," in Proc. 19th ACM SIGSOFT Symp. 13th Eur. Conf. Found. Softw. Eng., 2011, pp. 168-178. [Online]. Available: http://doi.acm.org/10.1145/2025113.2025139
15. C. Bird and T. Zimmermann, "Assessing the value of branches with what-if analysis," in Proc. ACM SIGSOFT 20th Int. Symp. Found. Softw. Eng., 2012, pp. 45:1-45:11. [Online]. Available: http://doi.acm.org/10.1145/2393596. 2393648
16. M. Vakilian, N. Chen, S. Negara, B. A. Rajkumar, B. P. Bailey, and R. E. Johnson, "Use, disuse, and misuse of automated refactorings," in Proc. 34th Int. Conf. Softw. Eng., Jun. 2012, pp. 233-243.
17. A. Srivastava, J. Thiagarajan, and C. Schertz, "Efficient Integration testing using dependency analysis," Microsoft Res., Tech. Rep. MSR-TR-2005-94, Redmond, WA, USA, 2005.
18. Y. Kataoka, T. Imai, H. Andou, and T. Fukaya, "A quantitative evaluation of maintainability enhancement by refactoring," in Proc. Int. Conf. Softw. Maintenance, 2002, pp. 576-585. (Pubitemid 35406631)
19. C. Izurieta and J. M. Bieman, "How software designs decay: A pilot study of pattern evolution," in Proc. 1st Int. Symp. Empirical Softw. Eng. Meas., 2007, pp. 449-451.
20. Y. Guo, C. Seaman, R. Gomes, A. Cavalcanti, G. Tonin, F. Q. B. Da Silva, A. L. M. Santos, and C. Siebra, "Tracking technical debt-an exploratory case study," in Proc. 27th IEEE Int. Conf. Softw. Maintenance, Sep. 2011, pp. 528-531.
21. W. Cunningham, "The wycash portfolio management system," in Addendum Proc. Object-Oriented Programm. Syst., languages, Appl., 1992, pp. 29-30.
22. N. Brown, Y. Cai, Y. Guo, R. Kazman, M. Kim, P. Kruchten, E. Lim, A. MacCormack, R. Nord, I. Ozkaya, R. Sangwan, C. Seaman, K. Sullivan, and N. Zazworka, "Managing technical debt in software- reliant systems," in Proc. ACM FSE/SDP Workshop Future Softw. Eng. Res., 2010, pp. 47-52. [Online]. Available: http://doi. acm.org/10.1145/1882362.1882373
23. R. Kolb, D. Muthig, T. Patzke, and K. Yamauchi, (Mar. 2006). Refactoring a legacy component for reuse in a software product line: A case study: Practice articles. J. Softw. Maintenance Evol. [Online]. 18, pp. 109-132. Available: http://dl.acm.org/citation. cfm?id=1133105.1133108
24. M. Kim, T. Zimmermann, and N. Nagappan, "A field study of refactoring challenges and benefits," in Proc. ACM SIGSOFT 20th Int. Symp. Found. Softw. Eng., 2012, pp. 50:1-50:11. [Online]. Available: http://doi.acm.org/10.1145/2393596.2393655
25. P. Tarr, H. Ossher, W. Harrison, and J. Stanley M. Sutton, "N degrees of separation: Multi-dimensional separation of concerns," in Proc. 21st Int. Conf. Softw. Eng., 1999, pp. 107-119.
26. G. Kiczales, J. Lamping, A. Menhdhekar, C. Maeda, C. Lopes, J.-M. Loingtier, and J. Irwin, "Aspect-oriented programming," in Proc. Eur. Conf. Object-Oriented Programm., 1997, vol. 1241, pp. 220-242. [Online]. Available: citeseer.ist.psu.edu/kiczales97aspectoriented. html (Pubitemid 127083932)
27. M. Eaddy, T. Zimmermann, K. D. Sherwood, V. Garg, G. C. Murphy, N. Nagappan, and A. V. Aho, "Do crosscutting concerns cause defects?" IEEE Trans. Softw. Eng., vol. 34, no. 4, pp. 497-515, Jul. 2008.
28. R. J. Walker, S. Rawal, and J. Sillito, "Do crosscutting concerns cause modularity problems?" in Proc. ACM SIGSOFT 20th Int. Symp. Found. Softw. Eng., 2012, pp. 49:1-49:11. [Online]. Available: http://doi.acm.org/10. 1145/2393596.2393654
29. F. P. Brooks, The Mythical Man-Month: Essays on Software Engineering. Reading, MA, USA: Addison-Wesley, Aug. 1975. [Online]. Available: http://www.amazon.com/exec/obidos/redirect? tag=citeulike07-20&path=ASIN/ 0201835959
30. E. Murphy-Hill, A. P. Black, D. Dig, and C. Parnin, "Gathering refactoring data: A comparison of four methods," in Proc. 2nd ACM Workshop Refactoring Tools, 2008, pp. 1-5.
31. T. J. McCabe, "A complexity measure," IEEE Trans. Softw. Eng., vol. 2, no. 4, pp. 308-320, Jul. 1976.
32. N. Nagappan, B. Murphy, and V. Basili, "The influence of organizational structure on software quality: An empirical case study," in Proc. 30th ACM Int. Conf. Softw. Eng., 2008, pp. 521-530. [Online]. Available: http://doi.acm.org/10.1145/1368088.1368160
33. G. Antoniol, K. Ayari, M. Di Penta, F. Khomh, and Y.-G. Guéhéneuc, "Is it a bug or an enhancement?: A text-based approach to classify change requests," in Proc. ACM Conf. Center Adv. Stud. Collaborative Res.: Meeting Minds, 2008, pp. 304-318.
34. M. E. Conway, "How do committees invent?" Datamation, vol. 14, no. 4, pp. 28-31, 1968.
35. J. Herbsleb and R. Grinter, "Architectures, coordination, and distance: Conway's law and beyond," IEEE Softw., vol. 16, no. 5, pp. 63-70, Sep./Oct. 1999. (Pubitemid 32078191)
36. S. Bailey, S. Godbole, C. Knutson, and J. Krein, "A decade of conway's law: A literature review from 2003-2012," in Proc. 3rd Int. Workshop Replication Empir. Softw. Eng. Res., Oct. 2013, pp. 1-14.
37. P. Dalgaard, Introductory Statistics with R, 2nd ed. New York, NY, USA: Springer-Verlag, 2008.
38. E. Murphy-Hill, C. Parnin, and A. P. Black, "How we refactor, and how we know it," in Proc. 31st Int. Conf. Softw. Eng., 2009, pp. 287-297.
39. K. Sullivan, P. Chalasani, S. Jha, and V. Sazawal, Software Design as an Investment Activity: A Real Options Perspective in Real Options and Business Strategy: Applications to Decision Making. London, U.K.: Risk Books, Nov. 1999.
40. C. Y. Baldwin and K. B. Clark, Design Rules: The Power of Modularity. Cambridge, MA, USA: MIT Press, 1999.
41. Z. Xing and E. Stroulia, "UMLDiff: An algorithm for object-oriented design differencing," in Proc. 20th IEEE/ACM Int. Conf. Autom. Softw. Eng., 2005, pp. 54-65.
42. D. Dig and R. Johnson, "The role of refactorings in API evolution," in Proc. 21st IEEE Int. Conf. Softw. Maintenance, 2005, pp. 389-398.
43. A. MacCormack, J. Rusnak, and C. Y. Baldwin, "Exploring the structure of complex software designs: An empirical study of open source and proprietary code," Manage. Sci., vol. 52, no. 7, pp. 1015-1030, 2006. (Pubitemid 43990589)
44. Y. -G. Guéhéneuc and H. Albin-Amiot, "Using design patterns and constraints to automate the detection and correction of interclass design defects," in Proc. 39th Int. Conf. Exhib. Technol. Object- Oriented Languages Syst., 2001, pp. 296-305. [Online]. Available: http://dl.acm.org/ citation.cfm?id=882501.884740
45. R. Marinescu, "Detection strategies: Metrics-based rules for detecting design flaws," in Proc. 20th IEEE Int. Conf. Softw. Maintenance, 2004, pp. 350-359. [Online]. Available: http://dl.acm.org/ citation.cfm?id= 1018431.1021443 (Pubitemid 40601037)
46. Y. Guo, C. Seaman, N. Zazworka, and F. Shull, "Domain-specific tailoring of code smells: An empirical study," in Proc. 32nd ACM/ IEEE Int. Conf. Softw. Eng.-Vol. 2, 2010, pp. 167-170. [Online]. Available: http://doi.acm.org/10.1145/1810295.1810321
47. S. Wong, Y. Cai, M. Kim, and M. Dalton, "Detecting software modularity violations," in Proc. ACM IEEE 33rd Int. Conf. Softw. Eng., 2011, pp. 411-420.
48. R. Moser, A. Sillitti, P. Abrahamsson, and G. Succi, "Does refactoring improve reusability?" in Proc. 9th Int. Conf Reuse Off-the-Shelf Compon., 2006, pp. 287-297. (Pubitemid 44097329)
49. J. Carriere, R. Kazman, and I. Ozkaya, "A cost-benefit framework for making architectural decisions in a business context," in Proc. 32nd ACM/IEEE Int. Conf. Softw. Eng., 2010, pp. 149-157.
50. N. Nagappan and T. Ball, "Use of relative code churn measures to predict system defect density," in Proc. 27th ACM Int. Conf. Softw. Eng., 2005, pp. 284-292.
51. W. G. Griswold, "Program restructuring as an aid to software maintenance," Ph.D. dissertation, Dept. Comput. Sci. Eng., Univ. Washington, Seattle, WA, USA, 1991.
52. D. Roberts, J. Brant, and R. Johnson, "A refactoring tool for smalltalk," Theory Practice Object Syst., vol. 3, no. 4, pp. 253-263, 1997.
53. B. Daniel, D. Dig, K. Garcia, and D. Marinov, "Automated testing of refactoring engines," in Proc. 6th Joint Meet. Eur. Softw. Eng. Conf. ACM SIGSOFT Symp. Found. Softw. Eng., 2007, pp. 185-194.
54. G. C. Murphy, M. Kersten, and L. Findlater. (2006, Jul.). How are Java software developers using the eclipse IDE? IEEE Softw. [Online]. 23(4), pp. 76-83. Available: http://dx.doi.org/10.1109/ MS.2006.105
55. D. Dig and R. Johnson, "Automated detection of refactorings in evolving components," in Proc. Eur. Conf. Object-Oriented Programm., 2006, pp. 404-428. (Pubitemid 44153421)
56. K. Prete, N. Rachatasumrit, N. Sudan, and M. Kim, "Templatebased reconstruction of complex refactorings," in Proc. IEEE Int. Conf. Softw. Maintenance, Sep. 2010, pp. 1-10.
57. T. Zimmermann and N. Nagappan, "Predicting defects using network analysis on dependency graphs," in Proc. 30th Int. Conf. Softw. Eng., 2008, pp. 531-540. [Online]. Available: http://doi. acm.org/10.1145/1368088.1368161
58. C. Bird, N. Nagappan, H. Gall, B. Murphy, and P. Devanbu, "Putting it all together: Using socio-technical networks to predict failures," in Proc. 20th Int. Symp. Softw. Rel. Eng., 2009, pp. 109-119. [Online]. Available: http://dx.doi.org/10.1109/ ISSRE.2009.17