Patterns of Work: A Pragmatic Approach

  • K. Kashimura
  • Y. Hara
  • N. Ikeya
  • David RandallEmail author
Part of the Computer Supported Cooperative Work book series (CSCW)


As was suggested in Chap.  1, we need to ‘… accumulate and synthesize knowledge about such social domains from case studies to be able to anticipate the use and behavioral impact of new designs’. In turn, Beringer suggests, we need to go about, ‘extracting key findings and summarizing key insights [so that] they can become a reusable set of foundational insights about target domains’. How we might do this, however, is a somewhat intractable problem. The past 20 years and more has, without question, seen a significant shift in the way in which data relating to design problems is collected and analysed. One of the most significant aspects of this has been the ‘turn to the social’ often associated with the deployment of ethnographic practices for design-related purposes.


Diesel Engine Augmented Reality Design Team Software Maintenance Maintenance Work 
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.


  1. Alexander, C. (1979). The timeless way of building. New York: Oxford University Press.Google Scholar
  2. Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M., Fiksdahl-King, I., & Angel, S. (1977). A pattern language. New York: Oxford University Press.Google Scholar
  3. Avizienis, A., Laprie, J. C., & Randell, B. (2001). Fundamental concepts of dependability. Computing Science: University of Newcastle upon Tyne.Google Scholar
  4. Bateman, J. (1995). Preventive maintenance: Stand alone manufacturing compared with cellular manufacturing. Industrial Management, 37(1), 19.Google Scholar
  5. Bendifallah, S. A., & Scacchi, W. (1987). Understanding software maintenance work. IEEE Transactions on Software Engineering, SE-13(3), 311–323.CrossRefGoogle Scholar
  6. Beyer, H., & Holzblatt, K. (1998). Contextual design: Defining customer-centred systems. San Francisco: Morgan Kaufmann Publishers. ISBN 1558604111.Google Scholar
  7. Bobrow, D. G., & Whalen, J. (2002). Community knowledge sharing in practice. Reflections, 4(2), 47–59.CrossRefGoogle Scholar
  8. Boehm-Davis, D. A., Fox, J. E., & Philips, B. H. (1996). Techniques for exploring program comprehension, empirical studies of programmers (pp. 3–37). Washington, DC: Ablex.Google Scholar
  9. Borchers, J. (2001). A pattern approach to interaction design. AI & Society, 15, 359–376 (Human Computer Interaction, 21(1), January 2001).Google Scholar
  10. Carstensen, P. (1999). Here is the knowledge-where should I put it? Findings from a study of how knowledge spaces are used within a support group. In IEEE 8th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE ‘99) Proceedings.Google Scholar
  11. Charmaz, K. (2006). Constructing grounded theory: A practical guide through qualitative analysis. London: Sage.Google Scholar
  12. Cooke, F. L. (2000). Implementing TPM in plant maintenance: Some organisational barriers. International Journal of Quality & Reliability Management, 17(9), 1003–1016.CrossRefGoogle Scholar
  13. Crabtree, A., Rouncefield, M., & Tolmie, P. (2012). Doing design ethnography. London: Springer.CrossRefGoogle Scholar
  14. Crosby, M. E., Scholtz, J., & Widenbeck, S. (2002). The roles beacons play in comprehension for novice and expert programmers. In 14th Workshop of the Psychology of Programming Interest Group, Brunel University (pp. 58–78).Google Scholar
  15. Dearden, A. M., & Finlay, J. (2006). Pattern languages in HCI: a critical review. Human Computer Interaction, 21(1), 49–102.CrossRefGoogle Scholar
  16. Denef, S. (2012). A pattern language of firefighting frontline practice to inform the design of ubiquitous computing. Communications in Computer and Information Science, 277, 308–312.CrossRefGoogle Scholar
  17. Dovey, K. (1990). The pattern language and its enemies. Design Studies, 11, 3–9.CrossRefGoogle Scholar
  18. Erickson, T. (2000). Lingua Francas for design: Sacred places and pattern languages DIS ’00. In Proceedings of the 3rd conference on designing interactive systems: Processes, practices, methods, and techniques (pp. 357–368). New York: ACM.Google Scholar
  19. Gabriel, R. (1996). Patterns of software. New York: Oxford University Press.Google Scholar
  20. Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1993). Design patterns: Abstraction and reuse of object-oriented design (Lecture notes in computer science, Vol. 707, pp. 406–431). Berlin: Springer.Google Scholar
  21. Gits, C. W. (1992). Design of maintenance concepts. International Journal of Production Economics, 24, 217–226.CrossRefGoogle Scholar
  22. Glaser, B. G., & Strauss, A. L. (1967). The discovery of grounded theory: Strategies for qualitative research. Chicago: Aldine.Google Scholar
  23. Goodyear, P. (2005). Patterns, educational design and networked learning: Patterns, pattern languages and design practice. Australasian Journal of Educational Technology,21(1), 82–101.Google Scholar
  24. Hughes, J. A., Randall, D., & Shapiro, D. (1992). From ethnographic record to system design. In Computer supported cooperative work (Vol. 1, pp. 123–141).Google Scholar
  25. Hughes, J. A., Randall, D., & Shapiro, D. (1993). Designing with ethnography: Making work visible. Interacting with Computers, 5(2), 239–253.CrossRefGoogle Scholar
  26. Hughes, J., King, V., Rodden, T., & Anderson, H. (1994). Moving out of the control room: Ethnography in system design. In Proceedings of the ACM conference on computer supported cooperative work, Chapel Hill, North Carolina (pp. 429–438). New York: ACM Press.Google Scholar
  27. Hutchins, E. (1995). Cognition in the wild. Cambridge, MA: MIT Press.Google Scholar
  28. Kaptelinen, V., & Nardi, B. (2006). Acting with technology: Activity theory and interaction design. Cambridge: MIT Press.Google Scholar
  29. Kemerer, C., & Slaughter, S. (1997). Determinants of software maintenance profiles: An empirical investigation. Software Maintenance: Research and Practice, 9, 235–251.CrossRefGoogle Scholar
  30. Ko, A. J., Aung, H. H., & Myers, B. A. (2005). Eliciting design requirements for maintenance-oriented IDE’s: A detailed study of corrective and perfective maintenance tasks. Human-Computer Interaction Institute, Paper 179.Google Scholar
  31. Laporte, T. (1996). High reliability organizations: Unlikely, demanding and at risk. Journal of Contingencies and Crisis Management, 4, 60–71.CrossRefGoogle Scholar
  32. Laporte, T. R., & Consolini, P. M. (1991). Working in practice but not in theory. Journal of Public Administration Research and Theory, 1(1), 19–47.Google Scholar
  33. Laporte, T., & Consolini, P. (1998a). Theoretical and operational challenges of “high-reliability organizations”: Air-traffic control and aircraft carriers. International Journal of Public Administration, 21(6-8), 847–852.CrossRefGoogle Scholar
  34. Laporte, T., & Consolini, P. (1998b). Working in practice but not in theory: Theoretical challenges of “high-reliability organizations”. Journal of Public Administration Research and Theory, 1(1), 19–48.Google Scholar
  35. Lin, J., & Landay, J. A. (2002). Damask: A tool for early-stage design and prototyping of multi-device user interfaces. In Proceedings of the 8th international conference on distributed multimedia systems (2002 international workshop on visual computing), San Francisco, CA, September 26–28, 2002 (pp. 573–580).Google Scholar
  36. Marquez, A. C. (2007). The maintenance management framework: models and methods for complex systems maintenance. Berlin: Springer.Google Scholar
  37. Martin, D., & Sommerville, I. (2004). Patterns of cooperative interaction: Linking ethnomethodology and design. ACM Transactions on Computer-Human Interaction, 11(1), March (the patterns archive is available at
  38. McDonald, N., Corrigan, S., Daly, C., & Cromie, S. (2000). Safety management systems and safety culture in aircraft maintenance organisations. Safety Science, 34, 151–176.CrossRefGoogle Scholar
  39. Nakagawa, T. (2005). Maintenance theory of reliability. Berlin: Springer.Google Scholar
  40. Orr, J. (1996). Talking about machines: An ethnography of a modern job. Ithaca: Cornell University Press.Google Scholar
  41. Orton, J. D., & Weick, K. (1990). Loosely coupled systems: A reconceptualization. Academy of Management Review, 15, 203.Google Scholar
  42. Perrow, C. (1999). Normal accidents: Living with high-risk technologies. Princeton: Princeton University Press.Google Scholar
  43. Pipek, V., & Wulf, V. (2003). Pruning the answer garden: Knowledge sharing in maintenance engineering. In Proceedings of the 6th European Conference on Computer Supported Cooperative Work, 14–18 September, Helsinki, Finland.Google Scholar
  44. Randall, D., Harper, R., & Rouncefield, M. (2007). Fieldwork for design. London: Springer.CrossRefGoogle Scholar
  45. Randall, D., Hughes, J., & Shapiro, D. (1993). Systems development – the fourth dimension: Perspectives on the social organization of work. In P. Quintas (Ed.), Social dimensions of systems engineering: People, processes, policies and software development (pp. 197–214). Hemel Hempstead: Ellis Horwood.Google Scholar
  46. Raouf, A., & Ben-Daya, M. (1995). Total maintenance management: A systematic approach. Journal of Quality in Maintenance Engineering, 1(1), 6–14.CrossRefGoogle Scholar
  47. Rising, L. (1998). The patterns handbook: Techniques, strategies, and applications. Cambridge: Cambridge University Press.Google Scholar
  48. Salingaros, N. (2000). The structure of pattern languages. Architectural Research Quarterly, 4, 149–162.CrossRefGoogle Scholar
  49. Schmidt, K. (2012). The trouble with ‘tacit knowledge’. International Journal of Computer Supported Cooperative Work, 21(2--3), 163–225.Google Scholar
  50. Smith, R., & Hawkins, B. (2004). Lean maintenance. Oxford: Elsevier.Google Scholar
  51. Smith, R., & Mobley, R. K. (2008). Rules of thumb for maintenance and reliability engineers. Oxford: Elsevier.Google Scholar
  52. Strauss, A., & Corbin, J. (1997). Grounded theory in practice. London: Sage.Google Scholar
  53. Swanson, L. (2001). Linking maintenance strategies to performance. International Journal of Production Economics, 70, 237–244.CrossRefGoogle Scholar
  54. Swanson, E. B. (1976). The dimensions of maintenance. In ICSE ‘76 Proceedings of the 2nd international conference on software engineering (pp. 492–497). New York: ACM Press.Google Scholar
  55. Tan, W.-G., & Gable, G. (1998). Attitudes of maintenance personnel towards maintenance work: A comparative analysis. Journal of Software Maintenance: Research and Practice,10(1), 59–74.CrossRefGoogle Scholar
  56. van Welie, M., & van der Veer, G. (2003). Pattern languages in interaction design: Structure and Organization Human-Computer Interaction – INTERACT’03M (Rauterberg, M., Menozzi, M., & Wesson, J., Eds., pp. 527–534). Amsterdam: IOS Press.Google Scholar
  57. Weick, K. (1976). Educational organizations as loosely coupled systems. Administrative Science Quarterly, 21(1), 1–19.CrossRefGoogle Scholar
  58. Wireman, T. (2004). Benchmarking best practices in maintenance management. New York: Industrial Press.Google Scholar
  59. Yamauchi, Y., Whalen, J., & Bobrow, D. (2003). Information use of service technicians in difficult cases. In 2003 Proceeding CHI ’03: Proceedings of the SIGCHI conference on Human factors in computing systems.Google Scholar

Copyright information

© Springer-Verlag London 2015

Authors and Affiliations

  • K. Kashimura
    • 1
  • Y. Hara
    • 1
  • N. Ikeya
    • 2
  • David Randall
    • 3
    Email author
  1. 1.Hitachi Design DivisionTokyoJapan
  2. 2.Keio UniversityTokyoJapan
  3. 3.School of Media and InformationUniversity of SiegenSiegenGermany

Personalised recommendations