Successful Architectural Knowledge Sharing: Beware of Emotions

  • Eltjo R. Poort
  • Agung Pramono
  • Michiel Perdeck
  • Viktor Clerc
  • Hans van Vliet
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5581)


This paper presents the analysis and key findings of a survey on architectural knowledge sharing. The responses of 97 architects working in the Dutch IT Industry were analyzed by correlating practices and challenges with project size and success. Impact mechanisms between project size, project success, and architectural knowledge sharing practices and challenges were deduced based on reasoning, experience and literature. We find that architects run into numerous and diverse challenges sharing architectural knowledge, but that the only challenges that have a significant impact are the emotional challenges related to interpersonal relationships. Thus, architects should be careful when dealing with emotions in knowledge sharing.


Software Architecture Architecture Knowledge Software Project Management 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Baccarini, D.: The logical framework method for defining project success. Project Management Journal 30, 25–32 (1999)Google Scholar
  2. 2.
    Bacon, S.F.: Religious Meditations, 1597Google Scholar
  3. 3.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison-Wesley, Reading (2003)Google Scholar
  4. 4.
    Boehm, B.: Software Engineering Economics. Prentice-Hall, Englewood Cliffs (1981)zbMATHGoogle Scholar
  5. 5.
    Clements, P., Shaw, M., Shaw, M.: The golden age of software architecture: A comprehensive survey, tech., Technical report (2006)Google Scholar
  6. 6.
    Cronbach, L.J.: Coefficient alpha and the internal structure of tests. Psychometrika 16(3), 297–334 (1951)CrossRefGoogle Scholar
  7. 7.
    El Emam, K., Koru, A.G.: A replicated survey of IT software project failures. IEEE Software, 84–89 (September/October 2008)Google Scholar
  8. 8.
    Frederick, J., Brooks, P.: The Mythical Man-Month: Essays on Software Engineering, 20th edn. Addison-Wesley, Reading (1995)Google Scholar
  9. 9.
    Jones, C.: Software Assessments, Benchmarks, and Best Practices. Addison-Wesley, Reading (2000)Google Scholar
  10. 10.
    Lago, P., van Vliet, H.: Building up and reasoning about architectural knowledge. In: Hofmeister, C., Crnković, I., Reussner, R. (eds.) QoSA 2006. LNCS, vol. 4214, pp. 43–58. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  11. 11.
    Linberg, K.: Software developer perceptions about software project failure: a case study. The Journal of Systems and Software 49, 177–192 (1999)CrossRefGoogle Scholar
  12. 12.
    Markus, M.L.: Power, politics, and M.I.S. implementation. Commun. ACM 26(6), 430–444 (1983)CrossRefGoogle Scholar
  13. 13.
    McConnell, S.: Rapid Development. Microsoft Press (1996)Google Scholar
  14. 14.
    Pinto, J., Slevin, D.: Project success: definitions and measurement techniques. Project Management Journal 19, 67–72 (1988)Google Scholar
  15. 15.
    Procaccino, J.D.: What do software practitioners really think about project success: an exploratory study. Journal of Systems and Software 78, 194–203 (2005)CrossRefGoogle Scholar
  16. 16.
    Standish Group, Chaos Report (1994)Google Scholar
  17. 17.
    Tyree, J., Akerman, A.: Architecture decisions: Demystifying architecture. IEEE Software 22(2), 19–27 (2005)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Eltjo R. Poort
    • 1
  • Agung Pramono
    • 2
  • Michiel Perdeck
    • 1
  • Viktor Clerc
    • 2
  • Hans van Vliet
    • 2
  1. 1.Logica, P.O. Box 159, 1180 AD AmstelveenThe Netherlands
  2. 2.VU UniversityAmsterdamThe Netherlands

Personalised recommendations