The impact of geographic distribution and the nature of technical coupling on the quality of global software development projects

Journal of software: Evolution and Process

Volumn 24, Issue 2, 2012, Pages 153-168

  Cataldo, Marcelo ^a   Nambiar, Sangeeth ^b  

^a Carnegie Mellon University   (United States)

^b Robert Bosch Engineering and Business Solutions Ltd   (India)

Author keywords

Architectural dependencies; Geographical dispersion; Global software development; Software quality; Technical coupling

Indexed keywords

ARCHITECTURAL COMPONENTS; ARCHITECTURAL DEPENDENCIES; DISTRIBUTED DEVELOPMENT; GEOGRAPHIC DISPERSION; GEOGRAPHIC DISTRIBUTION; GEOGRAPHICAL DISPERSIONS; GLOBAL SOFTWARE DEVELOPMENT; LOGICAL DEPENDENCIES; MULTIDIMENSIONAL NATURE; PRODUCT QUALITY; SOFTWARE PROJECT; SOFTWARE QUALITY;

COMPUTER SOFTWARE SELECTION AND EVALUATION;

SOFTWARE DESIGN;

EID: 84863304932     PISSN: None     EISSN: 20477481     Source Type: Journal    
DOI: 10.1002/smr.477     Document Type: Conference Paper

References (50)

1. Carmel E. Global Software Team: Collaboration Across Borders and Time Zones. Prentice-Hall: Englewood Cliffs, NJ, 1999.
2. Espinosa JA, Slaughter SA, Kraut RE, Herbsleb JD. Familiarity, complexity, and team performance in geographically distributed software development. Organization Science 2007; 18(4):613-630.
3. Herbsleb JD, Mockus A. An empirical study of speed and communication in globally distributed software development. IEEE Transactions on Software Engineering 2003; 29(6):481-494.
4. Karolak DW. Global Software Development: Managing Virtual Teams and Environments. IEEE Computer Society: Los Alamitos, CA, 1988.
5. Hinds PJ, Kiesler S. Distributed Work. MIT Press: Cambridge MA, 2002.
6. O'Leary MB, Cummings JN. The spatial, temporal and configurational characteristics of geographic dispersion in team. MIS Quarterly 2007; 31(3):433-452. (Pubitemid 47359819)
7. Herbsleb JD. Global software engineering: The future of socio-technical coordination. Proceedings of the Future of Software Engineering (FOSE'07). IEEE Computer Society: Washington DC, U.S.A., 2007; 188-198. (Pubitemid 47484925)
8. Cataldo M, Wagstrom P, Herbsleb JD, Carley KM. Identification of coordination requirements: Implications for the design of collaboration and awareness tools. Proceedings of the Conference on Computer Supported Cooperative Work (CSCW'06). ACM: New York NY, U.S.A., 2006; 353-362. (Pubitemid 47112424)
9. Cataldo M, Herbsleb J, Carley K. Socio-technical congruence: A framework for assessing the impact of technical and work dependencies on software development productivity. Proceedings of the Second Symposium on Empirical Software Engineering and Measurement (ESEM'08). IEEE Computer Society: Washington DC, U.S.A., 2008; 2-11.
10. Espinosa JA, Slaughter SA, Kraut RE, Herbsleb JD. Team knowledge and coordination in geographically distributed software development. Journal of Management Information Systems 2007; 24(1):135-169.
11. Mockus A, Weiss D. Globalization by chunking: A quantitative approach. IEEE Software 2001; 18(2):30-37. (Pubitemid 32293337)
12. Agerfalk PJ, Fitzgerald B. Flexible and distributed software processes: Old petunias in new bowls. Communications of the ACM 2006; 49(10):26-34.
13. Gumm DC. Distribution dimensions in software development projects: A taxonomy. IEEE Software 2006; 23(5):45-51. (Pubitemid 46405199)
14. Baldwin CY, Clark KB. Design Rules: The Power of Modularity. MIT Press: Cambridge MA, 2000.
15. Henderson RM, Clarck KB. Architectural innovation: The reconfiguration of existing product technologies and the failure of established firms. Administrative Science Quarterly 1990; 35:9-30.
16. Parnas DL. On the criteria to be used in decomposing systems into modules. Communications of ACM 1972; 15(12):1053-1058.
17. von Hippel E. Task partitioning: An innovation process variable. Research Policy 1990; 19:407-418.
18. Olson GM, Olson JS. Distance matters. Human-Computer Interaction 2000; 15(2&3):139-178. (Pubitemid 32251322)
19. Cataldo M, Mockus A, Roberts JA, Herbsleb JD. Technical dependencies, work dependencies and their impact of failures. IEEE Transactions on Software Engineering 2009; 35(6):864-878.
20. de Souza CRB, Redmiles D, Cheng L, Millen D, Patterson J. How a good software practice thwarts collaboration- The multiple roles of APIs in software development. Proceedings of the 12th Conference on Foundations of Software Engineering (FSE'04). ACM: New York NY, U.S.A., 2004; 221-230. (Pubitemid 40787584)
21. Nagappan N, Murphy B, Basili VR. The influence of organizational structure on software quality: An empirical case study. Proceedings of the International Conference on Software Engineering (ICSE'08). ACM: New York NY, U.S.A., 2008; 521-530.
22. Evaristo JR, Scudder R. Geographically distributed project teams: A dimensional analysis. Proceedings of the 33rd Hawaii International Conference on Systems Science (HICSS'00). IEEE Computer Society: Washington DC, U.S.A., 2000; 1-11.
23. Prikladnicki R, Audy J, Evaristo JR. Distributed software development: toward an understanding of the relationship between project team, users and customers. Proceedings of the Fifth International Conference on Enterprise Information Systems (ICEIS'03). Springer-Verlag: Germany, 2003; 417-423.
24. Ramasubbu N, Balan RK. Globally distributed software development project performance: An empirical analysis. Proceedings of the 15th Conference on Foundations of Software Engineering (FSE'07). ACM: New York NY, U.S.A., 2007; 125-134.
25. Grinter RE, Herbsleb JD, Perry DE. The geography of coordination dealing with distance in R&D work. Proceedings of the Conference on Supporting Group Work (GROUP'99). ACM: New York NY, U.S.A., 1999; 306-315.
26. Cataldo M, Bass M, Herbsleb JD, Bass L. On coordination mechanism in global software development. Proceedings of the International Conference on Global Software Engineering (ICGSE'07). IEEE Computer Society: Washington DC, U.S.A., 2007; 71-80.
27. Espinosa JA, Nan N, Carmel E. Do gradations of time zone separation make a difference in performance? A first laboratory study. Proceedings of the International Conference in Global Software Engineering (ICGSE'07). IEEE Computer Society: Washington DC, U.S.A., 2007; 12-22.
28. Sangwan R, Bass M, Mullick N, Paulish D, Kazmeier J. Global Software Development Handbook. Auerbach Publishers: Philadelphia PA, 2006.
29. Kabanoff B. Equity, equality, power and conflict. Academy of Management Review 1991; 16(2):416-441.
30. Hinds PJ, Bailey DE. Out of sight, out of sync: Understanding conflict in distributed teams. Organization Science 2003; 14(6):615-632.
31. Briand LC, Wust J, Daly JW, Porter DV. Exploring the relationships between design measures and software quality in object-oriented systems. The Journal of Systems and Software 2000; 51(3):245-273.
32. Nagappan N, Ball T. 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 (ESEM'07). IEEE Computer Society: Washington DC, U.S.A., 2007; 363-373.
33. Stevens WP, Myers GJ, Constantine LL. Structure design. IBM Systems Journal 1974; 13:231-256.
34. Zimmermann T, Nagappan N. The predicting defects using network analysis on dependency graphs. Proceedings of the International Conference on Software Engineering (ICSE'08). ACM: New York NY, U.S.A., 2008; 531-540.
35. Selby RW, Basili VR. Analyzing error-prone system structure. IEEE Transactions on Software Engineering 1991; 17(2):141-152.
36. Eaddy M, Zimmermannn T, Sherwood KD, Garg V, Murphy GC, Nagappan N, Aho AV. Do crosscutting concerns cause defects? IEEE Transactions on Software Engineering 2008; 34(4):497-515.
37. Gall H, Hajek K, Jazayeri M. Detection of logical coupling based on product release history. Proceedings of the International Conference on Software Maintenance (ICSM'98). IEEE Computer Society: Washington DC, U.S.A., 1998; 190-198.
38. Kraut RE, Streeter LA. Coordination in software development. Communications of the ACM 1995; 38(3):69-81.
39. Fenton NE, Neil M. A critique of software defect prediction models. IEEE Transactions on Software Engineering 1999; 25(5):675-689. (Pubitemid 30541838)
40. Graves TL, Karr AF, Marron JS, Siy H. Predicting fault incidence using software change history. IEEE Transactions on Software Engineering 2000; 26(7):653-661.
41. Boh WF, Slaughter SA, Espinosa JA. Learning from experience in software development: A multilevel analysis. Management Science 2007; 53(8):1315-1331. (Pubitemid 351159607)
42. Harter DE, Krishnan MS, Slaughter SA. Effects of process maturity on quality, cycle time, and effort on software product development. Management Science 2000; 46(4):451-466.
43. Krishnan MS, Kriebel CH, Kekre S, Mukhipadhyay T. An empirical analysis of productivity and quality in software products. Management Science 2000; 46(6):745-759.
44. Barlett CA, Ghoshal S. Transnational Management (3rd edn). McGraw-Hill: Boston MA, 2000.
45. Weisband S. Lessons about leadership at a distance and future research directions. Leadership at a Distance: Research in Technologically-Supported Work, Weisband S (ed.). Lawrence Erlbaum Associates: London, 2008.
46. Kutner M, Nachtsheim C, Neter J. Applied Linear Regression Models (4th edn). McGraw-Hill/Irwin: Boston MA, U.S.A., 2004.
47. Curtis B, Kransner H, Iscoe N. A field study of software design process for large systems. Communications of the ACM 1988; 31(11):1268-1287.
48. Cummings J, Espinosa JA, Pickering CK. Crossing spatial and temporal boundaries in globally distributed projects: A relational model of coordinatiion delay. Information Systems Research 2009; 20(3):420-439.
49. McGrath J, Hollingshead A. Groups Interacting with Technology. Sage Publishers: Beverley Hills, CA, 1994.
50. Allen R, Garlan D. A formal basis for architectural connection. ACM Transactions on Software Engineering and Methodology 1997; 6(3):213-249. (Pubitemid 127449188)