Testing in the wild: The Social and organisational dimensions of real world practice

Computer Supported Cooperative Work

Volumn 18, Issue 5-6, 2009, Pages 559-580

  Rooksby, John ^a   Rouncefield, Mark ^b   Sommerville, Ian ^a  

^a UNIVERSITY OF ST ANDREWS   (United Kingdom)

^b LANCASTER UNIVERSITY   (United Kingdom)

Author keywords

Dependability; Ethnography; Ethnomethodology; Organisational issues; Software development; Systems testing; Work practices

Indexed keywords

COMPUTER SOFTWARE; SYSTEMS ENGINEERING;

BAD PRACTICES; COOPERATIVE ACTIVITY; CURRENT PRACTICES; ETHNOGRAPHY; ETHNOMETHODOLOGY; KEY PARTS; REAL-WORLD; REAL-WORLD PRACTICE; SOFTWARE DEVELOPMENT SYSTEMS; WORK PRACTICES;

SOFTWARE DESIGN;

EID: 73449126198     PISSN: 09259724     EISSN: 15737551     Source Type: Journal    
DOI: 10.1007/s10606-009-9098-7     Document Type: Article

References (55)

1. J Ahonen T Junttila M Sakkinen 2004 Impacts of the organizational model on testing: three industrial cases Empirical Software Engineering 9 4 275 296 10.1023/B:EMSE.0000039880.99096.af
2. F Alby C Zucchermaglio 2009 Time, narratives and participation frameworks in software troubleshooting Computer Supported Cooperative Work 18 2-3 129 146 10.1007/s10606-008-9090-7
3. J Bach 1998 A framework for good enough testing IEEE Computer 31 10 124 126 1745094
4. Beizer, B. (1983). Software testing techniques. New York: Van Nostrand Reinhold.
5. Blythin, S., Hughes, J., Kristoffersen, S., Rodden, T., & Rouncefield, M. (1997). Recognising 'success' and 'failure': Evaluating groupware in a commercial context. In Proceedings of Group'97, The ACM SIGGROUP Conference on Supporting Group Work, Phoenix, USA, November 16-19, 1997, pp. 39-46.
6. Brooks, F. (1975). The mythical man month. Essays on software engineering. Boston: Addison-Wesley.
7. M Büscher J O'Neill J Rooksby 2009 Designing for diagnosing: introduction to the special issue on diagnostic work Computer Supported Cooperative Work 18 2-3 109 128 10.1007/s10606-009-9092-0
8. G Button 2000 The ethnographic tradition and design Design Studies 21 4 319 332 10.1016/S0142-694X(00)00005-3
9. Button, G., & Sharrock, W. (1992). Occasioned practices in the work of software engineers. In M. Jirotka & J. Goguen (Eds.), Requirements analysis: Social and technical issues (pp. 217-240). London: Academic.
10. G Button W Sharrock 1996 Project work: the organisation of collaborative design and development in software engineering Computer Supported Cooperative Work 5 4 369 386 10.1007/BF00136711
11. G Button W Sharrock 1998 The organisational accountability of technological work Social Studies of Science 28 1 78 102 10.1177/ 030631298028001003
12. L Capretz 2003 Personality types in software engineering International Journal of Human-Computer Studies 58 2 207 214 10.1016/S1071-5819(02)00137-4
13. P Carstensen C Sørensen 1995 Let's talk about bugs! Scandinavian Journal of Information Systems 7 1 33 54
14. H Collins 1988 Public experiments and displays of virtuosity: the core set revisited Social Studies of Science 18 4 725 748 10.1177/030631288018004006
15. Cornford, J., & Pollock, N. (2003). Putting the university online. Information technology and organisational change. Maidenhead: Open University Press.
16. A Da Cunha D Greathead 2007 Does personality matter? An analysis of code-review ability Communications of the ACM 50 5 109 112 10.1145/1230819. 1241672 (Pubitemid 46725669)
17. Dant, T., & Francis, D. (1998). Planning in organisations: rational control or contingent activity? Sociological Research Online, 3(2), < http://www.socresonline.org.uk/socresonline/3/2/4.html >.
18. E Dijkstra 1972 The humble programmer Communications of the ACM 15 10 859 866 10.1145/355604.361591
19. J Downer 2007 When the chick hits the fan: representativeness and reproducibility in technological tests Social Studies of Science 37 1 7 26 10.1177/0306312706064235
20. Evans, M. (1984). Productive software test management. New York: Wiley.
21. Feller, J., & Fitzgerald, B. (2001). Understanding open source software development. Boston: Addison-Wesley.
22. Garfinkel, H. (1967). Studies in ethnomethodology. Englewood Cliffs: Prentice Hall.
23. R Harper 2000 The organisation in ethnography Computer Supported Cooperative Work 9 2 239 264 10.1023/A:1008793124669 (Pubitemid 30594917)
24. Home Office Identity and Passport Service. (2007). Report on key projects implemented in 2007. http://www.ips.gov.uk/passport/downloads/IPS-report-on- key-projects-implemented-2007.pdf (retrieved 20th September 2008).
25. House of Commons Transport Committee. (2008). The opening of Heathrow Terminal 5. Twelfth Report of Session 2007-08. London: The Stationary Office Limited.
26. Jorgensen, P. (2002). Software testing a craftsman's approach. Boca Raton: CRC Press.
27. N Juristo A Moreno W Strigel 2006a Guest editors' introduction: software testing practices in industry IEEE Software 23 4 19 21 10.1109/MS.2006.104
28. N Juristo A Moreno S Vegas M Solari 2006b In search of what we experimentally know about unit testing IEEE Software 23 6 72 80 10.1109/MS.2006.166 (Pubitemid 44824160)
29. Kaner, C., Bach, J., & Pettichord, B. (2002). Lessons learned in software testing. New York: Wiley.
30. Lippert, M., Roock, S., & Wolf, H. (2002). Extreme programming in action. Practical examples from real world projects. New York: Wiley.
31. Mackenzie, D. (1990). Inventing accuracy: A historical sociology of nuclear missile Guidance. Cambridge: MIT.
32. Mackenzie, D. (2001). Mechanizing proof. Computing, risk and trust. Cambridge: MIT.
33. D Martin M Hartswood R Slack A Voss 2007 Achieving dependability in the configuration, integration and testing of healthcare technologies Computer Supported Cooperative Work 15 5-6 467 499 10.1007/s10606-006-9032-1
34. Martin, D., Rooksby, J., & Rouncefield, M. (2007b). Users as contextual features of software product development and testing. In Proceedings of Group'07, pp. 301-310.
35. Martin, D., Rooksby, J., Rouncefield, M., & Sommerville, I. (2007c). 'Good' organisational reasons for 'bad' software testing: An ethnographic study of testing in a small software company. In Proceedings of ICSE'07, pp. 602-611.
36. J Miller Y Zhichao 2004 A cognitive-based mechanism for constructing software inspection teams IEEE Transactions on Software Engineering 30 11 811 825 10.1109/TSE.2004.69 (Pubitemid 40055831)
37. Myers, G. (1976). The art of software testing. New York: Wiley.
38. Patton, R. (2006). Software testing. Indianapolis: Sams.
39. T Pinch 1993 "Testing-One, two, three testing!": towards a sociology of testing Science Technology & Human Values 18 1 25 41 10.1177/016224399301800103 743698
40. Randall, D., Harper, R., & Rouncefield, M. (2007). Fieldwork for design: Theory and practice. London: Springer Verlag.
41. M Reddy P Dourish W Pratt 2006 Temporality in medical work: time also matters Computer Supported cooperative work 15 1 29 53 10.1007/s10606-005-9010-z (Pubitemid 43296568)
42. K Rönkkö Y Dittrich D Randall 2005 When plans do not work out: how plans are used in software development projects Computer Supported Cooperative Work 14 5 433 468 10.1007/s10606-005-9004-x (Pubitemid 43014707)
43. Royce, W. (1970). Managing the development of large software systems. In Proceedings of WESTCON, August 1970, reprinted in Proceedings of ICSE '87 the 9th International Conference on Software Engineering, Monterey, USA. pp. 328-338.
44. Runeson, P. (2006). A survey of unit testing practices. IEEE Software, July/August 2006, pp. 22-29.
45. K Schmidt L Bannon 1992 Taking CSCW seriously: supporting articulation work Computer Supported Cooperative Work 1 1-2 7 40 10.1007/BF00752449
46. J Segal 2005 When software engineers met research scientists: a case study Empirical Software Engineering 10 4 517 536 10.1007/s10664-005-3865-y (Pubitemid 41406984)
47. Sharrock, W., & Anderson, B. (1993). Working towards agreement. In G. Button (Ed.), Technology in working order (pp. 149-161). London: Routledge.
48. W Sharrock B Anderson 1994 The user as a scenic feature of design space Design Studies 15 1 5 18 10.1016/0142-694X(94)90036-1
49. Simon, H. (1969). The sciences of the artificial. Cambridge: MIT.
50. Suchman, L. (1987). Plans and situated action: The problem of the human-machine communication. Cambridge: Cambridge University Press.
51. Tassey, G. (2002). The economic impacts of inadequate infrastructure for software testing. National Institute of Standards and Technology, US Department of Commerce Technology Administration. RTI Project Number 7007.011.
52. J Whittaker 2000 What is software testing? And why is it so hard? IEEE Software 17 1 70 79 10.1109/52.819971 (Pubitemid 30527451)
53. Whittaker, J. (2002). How to break software: A practical guide to testing. Boston: Addison-Wesley.
54. Winter, J., Rönkkö, K., Ahlberg, M., & Hotchkiss, J. (2008). Meeting organisational needs and quality assurance through balancing agile & formal usability testing results. In Proceedings of CEE-SET the 3rd IFIP TC2 Central and East European Conference on Software Engineering Techniques, Brno, Czech Republic, Oct. 13-15.
55. Woolgar, S. (1991). Configuring the user, the case of usability trials. In J. Law (Ed.), A sociology of monsters. Essays on power technology and domination (pp. 58-100). London: Routledge.