Software Development Cultures and Cooperation Problems: A Field Study of the Early Stages of Development of Software for a Scientific Community

Article

Abstract

In earlier work, I identified a particular class of end-user developers, who include scientists and whom I term ‘professional end-user developers’, as being of especial interest. Here, I extend this work by articulating a culture of professional end-user development, and illustrating by means of a field-study how the influence of this culture causes cooperation problems in an inter-disciplinary team developing a software system for a scientific community. My analysis of the field study data is informed by some recent literature on multi-national work cultures. Whilst acknowledging that viewing a scientific development through a lens of software development culture does not give a full picture, I argue that it nonetheless provides deep insights.

Keywords

community software development cooperation field study scientific software development software development culture professional end-user developers 

Notes

Acknowledgements

I should like to express my heartfelt gratitude to those people who participated in this field study. For reasons of confidentiality I cannot name them, but they know who they are. In addition, I should like to thank my colleagues in the Empirical Studies of Software Development Group in the Centre for Research in Computing at the Open University, Marian Petre, Hugh Robinson and Helen Sharp, for their unwavering support of my work. I should also like to thank the anonymous reviewers of an earlier version of this paper for their suggestions and references.

References

  1. Basili, V. R., Carver, J., Cruzes, D., Hochstein, L., Hollingsworth, J. K., Shull, F., et al. (2008). Understanding the high performance computing community: a software engineers’ perspective. IEEE Software, 25(4), 29–36.CrossRefGoogle Scholar
  2. Brannen, M. Y., & Salk, J. (2000). Partnering across borders: negotiating organisational culture in a German-Japanese joint venture. Human Relations, 53, 451–487.CrossRefGoogle Scholar
  3. Brown, J. S., & Duguid, P. (2000). The social life of information. Boston: Harvard Business School.Google Scholar
  4. Carver, J. C., Kendall, R. P., Squires, S. E., Post, D. E. (2007). Software development environments for scientific and engineering software: A series of case studies. Proc. ICSE 2007Google Scholar
  5. De Roure, D., & Goble, C. (2009). Software design for empowering scientists. IEEE Software, 26(1), 88–95.CrossRefGoogle Scholar
  6. Hofstede, G. (1994). Cultures and organisations: Intercultural cooperation and its importance for survival. HarperCollins.Google Scholar
  7. Kelly, D. F. (2007). A software chasm: software engineering and scientific computing. IEEE Software, 24(6), 120–199.CrossRefGoogle Scholar
  8. Knorr Cetina, K. (1999). Epistemic cultures: How the sciences make knowledge. Harvard University Press.Google Scholar
  9. Kujala, S. (2003). User involvement: a review of the benefits and challenges. Behaviour and Information Technology, 22(1), 1–16.CrossRefGoogle Scholar
  10. Letondal, C. (2005). Participatory programming: developing programmable bioinformatic tools for end-users. In H. Lieberman, F. Paterno, V. Wulf (Eds.), End user development (pp. 207–242). Springer.Google Scholar
  11. Macaulay, C., Sloan, D., Jiang, X., Forbes, P., Loynton, S., Swedlow, J. R., et al. (2009). Usability and user-centred design in scientific software development. IEEE Software, 26(1), 96–102.CrossRefGoogle Scholar
  12. Petre, M., & Blackwell, A. F. (2007). Children as unwitting end-user programmers. VLHCC, IEEE Symposium on Visual Languages and Human-Centric Computing, 2007, 239–242.CrossRefGoogle Scholar
  13. Sanders, R., & Kelly, D. (2008). Scientific software: where’s the risk and how do scientists deal with it? IEEE Software, 25(4), 21–28.CrossRefGoogle Scholar
  14. Segal, J. (2001). Organisational learning and software process improvement: A case study. In K.-D. Althoff, R.L. Feldmann, W. Muller (Eds.). Advances in learning software organizations, lecture notes in computer science (Vol. 2176, pp. 68–82). Springer.Google Scholar
  15. Segal, J. (2005). When software engineers met research scientists: a case study. Empirical Software Engineering, 10, 517–536.CrossRefGoogle Scholar
  16. Segal, J. (2007). Some problems of professional end user developers. VLHCC, IEEE Symposium on Visual Languages and Human-Centric Computing, 2007, 111–118.CrossRefGoogle Scholar
  17. Segal, J. (2008a). ‘Models of scientific software development. SECSE 08, workshop on software engineering in computational science and engineering, workshop co-located with ICSE 08, Leipzig, Germany. http://www.cse.msstate.edu/~SECSE08/Papers/Segal.pdf.
  18. Segal, J. (2008b). Scientists and software engineers: A tale of two cultures. To appear in the 20th Psychology of Programming Interest Group Workshop.Google Scholar
  19. Segal, J., & Morris, C. (2008). Developing scientific software. IEEE Software, 25(4), 18–20.CrossRefGoogle Scholar
  20. Thew, S., Sutcliffe, A., Procter, R., Bruijn, D., McNaught, J., Venters, C., et al. (2009). Requirements engineering for e-science: experiences in epidemiology. IEEE Software, 26(1), 80–87.CrossRefGoogle Scholar
  21. Wagner, E. L., & Piccoli, G. (2007). Moving beyond user participation to achieve successful IS design. Comm ACM, 50(12), 51–55.CrossRefGoogle Scholar
  22. Walsham, G. (2002). Cross-cultural software production and use: a structurational analysis. MIS Quarterly, 26(4), 359–380.CrossRefGoogle Scholar

Copyright information

© Springer Science+Business Media B.V. 2009

Authors and Affiliations

  1. 1.Empirical Studies of Software Development Group, Centre for Research in Computing, The Department of ComputingThe Open UniversityMilton KeynesUK

Personalised recommendations