Software engineering and the CHI & CSCW communities

  • Jonathan Grudin
  • Steven Poltrock
Invited Papers
Part of the Lecture Notes in Computer Science book series (LNCS, volume 896)


The ACM Special Interest Group on Computer and Human Interaction (CHI) has flourished for ten years. The lack of direct interaction between CHI and the discipline of Software Engineering was not entirely an oversight: the two groups have distinct missions. However, a natural bridge is forming from both sides. Considerable work has appeared in CHI conferences and journals that could interest one or another segment of Software Engineering. The potential overlap grew with the emergence in the mid-1980s of a Computer-Supported Cooperative Work (CSCW) focus. CSCW has been dominated by contributors from the CHI community, particularly in the United States. This essay is intended to guide a software engineer into the CHI and CSCW literature. It begins with a CHI perspective on the history of interaction between software engineering and human-computer interaction.


User Interface Software Engineer Interface Design Product Developer Spiral Model 
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. [Boeh98]
    Boehm, B., 1988. “A spiral model of software development and enhancement.” IEEE Computer, 21, 5, 61–72.Google Scholar
  2. [DeMa78]
    De Marco, T., 1978. Structured analysis and system specification. NY: Yourdon Press, Inc.Google Scholar
  3. [Frie89]
    Friedman, A.L., 1989. Computer systems development: History, organization and implementation. Chichester, UK: Wiley.Google Scholar
  4. [Goul88]
    Gould, J.D., 1988. “How to design usable systems.” In M. Helander (Ed.) Handbook of Human-Computer Interaction. Amsterdam: North-Holland.Google Scholar
  5. [GoLe83]
    Gould, J.D., & Lewis, C.H., 1983. “Designing for usability-key principles and what designers think.” Proc.CHI'83, 50–53.Google Scholar
  6. [Grud90]
    Grudin, J., 1990. “The computer reaches out: The historical continuity of interface design.” Proc. CHI'90, 261–268. New York: ACM.Google Scholar
  7. [Grud91a]
    Grudin, J., 1991a. “Interactive systems: Bridging the gaps between developers and users.” IEEE Computer, 24, 4, 59–69.Google Scholar
  8. [Grud91b]
    Grudin, J., 1991b. “Systematic sources of suboptimal interface design in large product development organizations.” Human-Computer Interaction, 6, 2, 147–196.Google Scholar
  9. [Grud94]
    Grudin, J., 1994. “Computer-Supported Cooperative Work: History and focus.” IEEE Computer, 27, 5, 19–26.Google Scholar
  10. [Jack83]
    Jackson, M., 1983. System development. Englewood Cliffs, NJ: Prentice-Hall.Google Scholar
  11. [MoCa94]
    Moran, T.P., & Carroll, J.M. (Eds.), 1994. Design Rationale: concepts, techniques, and use. Hillsdale, NJ: Lawrence Erlbaum Associates.Google Scholar
  12. [PoGr94]
    Poltrock, S.E., & Grudin, J., 1994. “Organizational obstacles to interface design and development: Two participant observer studies.” ACM Transactions on Computer-Human Interaction, 1, 1, 52–80.Google Scholar
  13. [Royc70]
    Royce, W.W., 1970. “Managing the development of large software systems: concepts and techniques.” Proc. IEEE Wescon, 1970, 1–9.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Jonathan Grudin
    • 1
  • Steven Poltrock
    • 2
  1. 1.Department of Information and Computer ScienceUniversity of CaliforniaIrvine
  2. 2.Boeing Computer ServicesSeattle

Personalised recommendations