Architecture-Centric Development in Globally Distributed Projects

  • Joachim SauerEmail author


In this chapter architecture-centric development is proposed as a means to strengthen the cohesion of distributed teams and to tackle challenges due to geographical and temporal distances and the clash of different cultures. A shared software architecture serves as blueprint for all activities in the development process and ties them together. Architecture-centric development thus provides a plan for task allocation, facilitates the cooperation of globally distributed developers, and enables continuous integration reaching across distributed teams. Advice is also provided for software architects who work with distributed teams in an agile manner.


Software Architect Software Architecture Agile Method Global Software Development Continuous Integration 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Bass, L., & Kazman, R. (1999). Architecture-based development (CMU/SEI-99-TR-007). Carnegie Mellon University. Google Scholar
  2. 2.
    Bass, L., Clements, P., & Kazman, R. (2003). Software architecture in practice (2nd ed.). Reading: Addison-Wesley Longman Publishing. Google Scholar
  3. 3.
    Bischofberger, W. R., Kühl, J., & Löffler, S. (2004). Sotograph—a pragmatic approach to source code architecture conformance checking. In F. Oquendo, B. Warboys, & R. Morrison (Eds.), Proceedings of the 1st European workshop on software architecture (EWSA 2004) (pp. 1–9). St Andrews, England, May 21–22. Google Scholar
  4. 4.
    Clements, P., Garlan, D., Bass, L., Stafford, J., Nord, R., Ivers, J., & Little, R. (2002). Documenting software architectures: Views and beyond. Upper Saddle River: Pearson Education. Google Scholar
  5. 5.
    Damian, D., & Moitra, D. (2006). Global software development: How far have we come? IEEE Software, 23(5), 17–19. CrossRefGoogle Scholar
  6. 6.
    Fowler, M. (2006). Continuous integration.
  7. 7.
    Herbsleb, J. D., & Grinter, R. E. (1999). Architectures, coordination, and distance: Conway’s law and beyond. IEEE Software, 16(5), 63–70. CrossRefGoogle Scholar
  8. 8.
    Jacobson, I., Booch, G., & Rumbaugh, J. (1999). The unified software development process. Reading: Addison-Wesley Longman Publishing. Google Scholar
  9. 9.
    Kornstädt, A., & Sauer, J. (2007). Mastering dual-shore development—the tools & materials approach adapted to agile offshoring. In B. Meyer & M. Joseph (Eds.), Proceedings of the 1st international conference on software engineering approaches for offshore and outsourced development (SEAFOOD 2007) (pp. 83–95). Revised Papers, Zurich, Switzerland, February 5–6. Google Scholar
  10. 10.
    Kornstädt, A., & Sauer, J. (2007). Tackling offshore communication challenges with agile architecture-centric development. In Proceedings of the 6th working IEEE/IFIP conference on software architecture (WICSA’07). Mumbai, India, January 6–9. Google Scholar
  11. 11.
    Ovaska, P., Rossi, M., & Marttiin, P. (2003). Architecture as a coordination tool in multi-site software development. Software Process: Improvement and Practice, 8(4), 233–247. CrossRefGoogle Scholar
  12. 12.
    Rogers, R. O. (2004). Scaling continuous integration. In Proceedings of the 5th international conference on extreme programming and agile processes in software engineering (XP 2004) (pp. 68–76). Garmisch-Partenkirchen, Germany, June 6–10. Google Scholar
  13. 13.
    Sauer, J. (2008). Enabling agile offshoring with the dual-shore model. In W. Maalej & B. Bruegge (Eds.), Software engineering 2008—Workshopband, Fachtagung des GI-Fachbereichs Softwaretechnik (pp. 35–42). Munich, Germany, February 18–22. Google Scholar
  14. 14.
    Smolander, K. (2002). Four metaphors of architecture in software organizations: Finding out the meaning of architecture in practice. In Proceedings of the 2002 international symposium on empirical software engineering (ISESE 2002). Nara, Japan, October 3–4. Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  1. 1.C1 WPS GmbHHamburgGermany

Personalised recommendations