The designer as user: building requirements for design tools from design practice

Software tools that support the design and development of interactive computing systems are an exciting possibility. The potential pay-off is great: user interface management systems, for example, promise not only to speed the process of specifying, implementing and maintaining user interface code, but also to guide the content of the user interfaces they support. As for any tool intended for human use, however, the success of software design tools will hinge on a thorough understanding of the problems they seek to address—design as it is practiced in the real world.

[1]  Stephen J. Payne,et al.  Task-Action Grammars: A Model of the Mental Representation of Task Languages , 1987, SGCH.

[2]  Clayton Lewis,et al.  Designing for usability—key principles and what designers think , 1983, CHI '83.

[3]  Susanne Maaß,et al.  The Adaptation of Virtual Man-Computer Interfaces to User Requirements in Dialogs , 1981, Lecture Notes in Computer Science.

[4]  John M. Carroll,et al.  Softening Up Hard Science: Reply to Newell and Card , 1987, ACM SIGCHI Bull..

[5]  R. L. Campbell,et al.  Artifacts as psychological theories: the case of human-computer interaction , 1989 .

[6]  P. Barnard,et al.  Design practice and interface usability: Evidence from interviews with designers , 1983, CHI '83.

[7]  Ludwig Slusky.  Integrating software modelling and prototyping tools , 1987 .

[8]  John L. Sibert,et al.  An object-oriented user interface management system , 1986, SIGGRAPH.

[9]  Dan R. Olsen,et al.  SYNGRAPH: A graphical user interface generator , 1983, SIGGRAPH.

[10]  Dennis R. Wixon,et al.  Improving human-computer interaction—a quest for cognitive science , 1987 .

[11]  Joyce J. Elam,et al.  A methodology for studying software design teams: an investigation of conflict behaviors in the requirements definition phase , 1987 .

[12]  M. Rosson,et al.  Designing for designers: an analysis of design practice in the real world , 1986, CHI '87.

[13]  David Lorge Parnas,et al.  A Rational Design Process: How and Why to Fake It , 1985, TAPSOFT, Vol.2.

[14]  S Lammers,et al.  Programmers at Work: Interviews with 19 of Today's Most Brilliant Programmers , 1986 .

[15]  Allen Newell,et al.  Human Problem Solving. , 1973 .

[16]  Wendy A. Kellogg,et al.  CONCEPTUAL CONSISTENCY IN THE USER INTERFACE: EFFECTS ON USER PERFORMANCE , 1987 .

[17]  John D. Gould,et al.  The 1984 Olympic Message System: a test of behavioral principles of system design , 1987, CACM.

[18]  P. P. Tanner,et al.  Some Issues in Future User Interface Management System (UIMS) Development , 1985 .

[19]  Mary Beth Rosson,et al.  Usability Specifications as Tool in Iterative Development. , 1984 .

[20]  Mark Green,et al.  The University of Alberta user interface management system , 1985, SIGGRAPH.

[21]  William Buxton,et al.  Towards a comprehensive user interface management system , 1983, SIGGRAPH.

[22]  William Buxton,et al.  Creating highly-interactive and graphical user interfaces by demonstration , 1986, SIGGRAPH.

[23]  Peter T. L. Popkowski Leszczyc,et al.  The university of alberta. , 1969, Canadian family physician Medecin de famille canadien.

[24]  Barry W. Boehm,et al.  Prototyping Versus Specifying: A Multiproject Experiment , 1984, IEEE Transactions on Software Engineering.

[25]  William L. Bewley,et al.  Human factors testing in the design of Xerox's 8010 “Star” office workstation , 1983, CHI '83.

[26]  Carolanne Fisher.  Advancing the study of programming with computer-aided protocol analysis , 1987 .

[27]  Mary Beth Rosson,et al.  Benutzerfreundlichkeit, Systemkonsistenz und andere schwer definierbare Prinzipien: Interviews mit Systementwicklern , 1987, Software-Ergonomie.

[28]  Stephen S. Yau,et al.  A survey of software design techniques , 1986, IEEE Transactions on Software Engineering.