Bibliography Approximately twenty of the following articles and some chapters in books are reprinted in the collection [Baecker87]; they are so noted. In the printed SEI Module, abstracts and tables of contents are available, but in the online version they are omitted because that and other information are available in the HCI Bibliography. A topic table has been placed at the end of the bibliography. The topics are in columns, and correspond to the topics in the module, with major topics in uppercase letters. Subtopics are listed to the right of their major topics. The topics are in columns and correspond to the topics in the module, with major topics emphasized. Subtopics are listed to the right of their major topics. The first two columns indicate whether the entry is a book (or conference proceedings, collection, or a large standards document) or a software tool manual. The final columns indicate if the entry has a focus on the Macintosh, IBM PC, or UNIX systems. To use the table, read down columns of topics to find references of interest, or read across lines to see what topics a reference is about. When a source is general, it may not be listed as covering more specific topics. The categorization has not been validated and is probably not perfectly reliable. General general source on user interface development Lifecycle the development process Design making decisions about design Task task analysis Psych psychological foundations Device input and output devices Dialogue dialogue types Guidelines design guidelines and standards Prototype rapid prototyping and screen design Specification formal specification Implementation building systems, producing code, documents UIMS user interface management systems Windows window systems, libraries Guidance online and printed guidance/documentation Evaluation usability testing Empirical collecting data Model formal models for explanation and prediction Tool software tools Mac Macintosh IBM IBM PC and compatibles UNIX UNIX systems and some similar workstations [AERA85] AERA, APA, and NCEA (1985) Standards for Educational and Psychological Testing. Washington, DC: American Psychological Association. Comments: An excellent source of information on measurement issues. [APA82] APA (1982) Ethical Principles in the Conduct of Research with Human Participants. Washington, DC: American Psychological Association. [Apple85] Apple (1985) Inside Macintosh. Reading, MA: Addison-Wesley. Comments: The "bible" for developers of software for the Macintosh, this book is too large to use as anything but a reference source. The section on user interface conventions is useful, but not very deep; most user interface conventions on the Mac are encoded in the toolbox, which is itself an important lesson. See [Apple87]. [Apple87] Apple (1987) Human Interface Guidelines: The Apple Desktop Interface. Reading, MA: Addison-Wesley. Comments: From the references section: "Note that the `User Interface Guidelines' chapter in Inside Macintosh is superseded by Human Interface Guidelines: The Apple Desktop Interface." [Arnold81] Arnold, K. C. R. C. (1981) Screen Updating and Cursor Movement Optimization: A Library Package. Berkeley, CA: Berkeley UNIX Software Distribution, University of California, Berkeley. Comments: This document describes a library of C functions for painting character-based screens on UNIX systems, and has been ported to PC systems. It is innovative in that it provides a simplified programmer interface to the terminal- independent screen-handling routines (termcap) developed by [Joy80]. [Baecker87] Baecker, R. A. and W. A. S. Buxton (Eds.) (1987) Readings in Human- Computer Interaction: A Multidisciplinary Approach. Los Altos, CA: Morgan Kauffman. Comments: A collection of important papers and chapters in human- computer interaction (the research field on which user interface development is based), with commentary by the editors. The best source of readings available. [Bailey82] Bailey, R. W. (1982) Human Performance Engineering: A Guide for System Designers. Englewood Cliffs, NJ: Prentice-Hall. Comments: This book is a reasonably comprehensive source of information on human factors in design. It has a section on computer systems but it is not particularly strong in that area. It would make a fair supplementary text for a course on user interface development, mainly because of its coverage of applied psychology. [Bailey83] Bailey, R. W. (1983) Human Error in Computer Systems. Englewood Cliffs, NJ: Prentice-Hall. [Barnard88] Barnard, P. & Grudin, J. (1988) Command Names. In M. Helander (Ed.) The Handbook of Human Computer Interaction. Amsterdam: North-Holland. 237-255. [Barth86] Barth, P. S. (1986) An Object-Oriented Approach to Graphical Interfaces. ACM Transactions on Graphics, 5, 2, 142- 172. [Bass85] Bass, L. J. (1985) An Approach to User Specification of Interactive Display Interfaces. IEEE Transactions on Software Engineering, 11, 8, 686-698. [Bass89] Bass, L. (1989) Serpent Overview. Report CMU/SEI-89-UG-2, Pittsburgh, PA: Software Engineering Institute. Comments: Serpent is a system for developing user interfaces. It manages the dynamic behavior of the interfaces. It consists of a language designed for the specification of user interfaces as well as the run time support for that language. This document provides an introduction to the Serpent system and includes a description of the Serpent system, the Serpent language and how Serpent is used to construct and manage user interfaces. [Beaudet88] Beaudet, D. B. & Williges, R. C. (1988) The Role of Screening Studies in Sequential Research Designs. Proceedings of the Human Factors Society 32nd Annual Meeting. 1174-1178. [Bennett87] Bennett, J. L. (1987) Collaboration of UIMS Designers and Human Factors Specialists. Computer Graphics, 21, 2, 102-105. [Berry85] Berry, R. E. & Meekings, B. A. E. (1985) A Style Analysis of C Programs. Communications of the ACM, 28, 1, 80- 88. Comments: This article provides a focus for discussion of many aspects of programming style and the construction of measures. [Borning86] Borning, A. & Duisberg, R. (1986) Constraint-Based Tools for Building User Interfaces. ACM Transactions on Graphics, 5, 4, 345-374. [Bricklin86] Bricklin, D. (1986) Demo Program User Manual. West Newton, MA: Software Garden. Comments: Dan Bricklin's DEMO program is the best-known tool for character screen design. It runs on the IBM PC and costs about $75. As a stand-alone tool for designing screens, or sequences of screens with some conditional switching, it is hard to beat, and it is well liked by most students. A new version is available from Peter Norton Company. [Brown88] Brown, C. M. (1988) Human-Computer Interface Design Guidelines. New York: Ablex Publishing. [Buxton83] Buxton, W. A. S., et al. (1983) Towards a Comprehensive User Interface Management System. Computer Graphics, 17, 3, 35-42. Comments: Reprinted in [Baecker87], p. 576. [Buxton86] Buxton, W. A. S. There's More to Interaction than Meets the Eye: Some Issues in Manual Input. (1986) In D. A. Norman and S. W. Draper (Eds.) User Centered System Design: New Perspectives in Human-Computer Interaction. Hillsdale, NJ: Lawrence Erlbaum Associates. Comments: In this paper, the author argues convincingly that functionally equivalent input devices are not equally well suited to different tasks. While discussing this paper, it is useful to have access to a variety of input devices, some of which can be purchased in toy stores (Etch-a- Sketch, Magnadoodle), and some not, because they are discontinued (Skeedoodle). Input devices to run on computers cost substantially more, over $100 each, but you may be able to find a variety you can borrow. Reprinted in [Baecker87], p. 366. [Campbell74] Campbell, S. K. (1974) Flaws and Fallacies in Statistical Thinking. Englewood Cliffs, NJ: Prentice-Hall. Comments: This is a popular, lively, and critical introduction to statistical reasoning. Students find it easy to read and useful for thinking about evaluation. [Card78] Card, S. K., English, W., & Burr, B. (1978) Evaluation of Mouse, Rate- Controlled Isometric Joystick, Step Keys, and Text Keys for Text Selection on a CRT. Ergonomics, 21, 8, 601-613. Comments: This is a good paper, which shows that the mouse input device is better than others for many tasks. Reprinted in [Baecker87], p. 386. [Card80] Card, S. K., Moran, T. P., & Newell, A. (1980) The Keystroke Model for User Performance Time with Interactive Systems. Communications of the ACM, 23, 7, 396-410. Comments: This paper describes a simple but powerful model for predicting task completion times based on the number of simple events, such as keystrokes. As a good example, it also provides detailed information about how to construct and interpret predictive models of human performance. Reprinted in [Baecker87], p. 192. [Card83] Card, S. K., Moran, T. P., & Newell, A. (1983) The Psychology of Human Computer Interaction. Hillsdale, NJ: Lawrence Erlbaum Associates. Comments: This book summarizes the influential work of the authors in basic research in human computer interaction. It begins with an excellent general chapter on a model of the human information processor; however, the material in it is probably beyond the interest of most software engineering students. [Card85] Card, S. K., Pavel, M., & Farrell, J. E. (1985) Window-Based Computer Dialogues. In B. Shackel (Ed.) Human- Computer Interaction: INTERACT '84. Amsterdam: North-Holland. Comments: A good source of information about the design issues, but not implementation issues, in using windows in user interfaces. Reprinted in [Baecker87], p. 456. [Carroll85] Carroll, J. M. (1985) Minimalist Design for Active Users. In B. Shackel (Ed.) Human-Computer Interaction: INTERACT '84. Amsterdam: North-Holland. 39-44. Comments: Reprinted in [Baecker87], p. 621. [Carroll87a] Carroll, J. M. & McKendree, J. (1987) Interface Design Issues for Advice- Giving Expert Systems. Communications of the ACM, 30, 1, 14-31. Comments: This paper discusses the use of intelligent tutors that would monitor usage and give advice about how to accomplish tasks. [Carroll87b] Carroll, J. M. (Ed.) (1987) Interfacing Thought: Cognitive Aspects of Human- Computer Interaction. Cambridge, MA: MIT Press. Comments: This is a collection of invited papers by leading researchers in the field of human- computer interaction. Many papers summarize the work of the authors, and so serve as a good starting point for learning about the research in the field. [Chi85] Chi, U. H. (1985) Formal Specification of User Interfaces: A Comparison and Evaluation of Four Axiomatic Approaches. IEEE Transactions on Software Engineering, 11, 8, 671-685. [Chin88] Chin, J. P., Diehl, V. A., & Norman, K. L. (1988) Development of an Instrument Measuring User Satisfaction of the Human-Computer Interface. CHI '88: Human Factors in Computing Systems. 213-218. [Cleveland85] Cleveland, W. S. (1985) The Elements of Graphing Data. Monterey, California: Wadsworth. Comments: This book has a chapter that covers good graphing practices. [Conklin87] Conklin, J. (1987) Hypertext: An Introduction and Survey. IEEE Computer, 20, 17-41. Comments: This paper provides a broad and detailed overview of several research and commercial hypertext systems. [Coutaz84a] Coutaz, J. (1984) The Box, A Layout Abstraction for User Interface Toolkits. Pittsburgh, PA: Carnegie Mellon University, Department of Computer Science. [Coutaz84b] Coutaz, J. (1984) A Paradigm for User Interface Architecture. Pittsburgh, PA: Carnegie Mellon University, Department of Computer Science. [Coutaz87] Coutaz, J. (1987) The Construction of User Interfaces and the Object Paradigm. Poster paper for the ACM Conference on Human Factors in Computing Systems, Toronto, Canada (Published in ECOOP '87). [Cox86] Cox, B. & Hunt, W. (1986) Objects, Icons, and Software IC's. BYTE, 11, 8. [DeSoi89] DeSoi, J. F., Lively, W. M., & Sheppard, S. V. (1989) Graphical Specification of User Interfaces with Behavior Abstraction. CHI '89: Proceedings of Human Factors in Computing Systems. 139-144. [DOD83] DOD (Department of Defense) (1983) MIL- STD-1472C Military Standard: Human Engineering Design Criteria for Military Systems, Equipment and Facilities. Washington, DC: Department of Defense. [DOD85] DOD (Department of Defense) (1985) DOD- HDBK-761 Military Handbook: Human Engineering Guidelines for Management Information Systems. Washington, DC: Department of Defense. Comments: This document provides fundamental information on human factors engineering guidelines for automated data systems. It contains guidelines regarding general design considerations; dialogue and display; language considerations; working in the file; forms, manuals and fiche; keyboard and input devices; screens and printers; and work stations. It should provide valuable information and guidance to personnel responsible for integrating human factors engineering considerations into the design of automated data systems. [DOD89] Department of Defense (1989) MIL-STD- 1472D, Human Engineering Design Criteria for Military Systems, Equipment and Facilities. Washington, DC: Department of Defense. Comments: This is an updated version of [DOD83] with substantially the same structure. Although it supersedes [DOD83] and intermediate updates, the old standard will be used under current contracts for years. [Drury87] Drury, C. G., et al. (1987) Task Analysis. In G. Salvendy (Ed.) Handbook of Human Factors. New York: Wiley. 370- 401. [Ehrich86] Ehrich R. W. and R. C. Williges (Eds.) (1986) Human-Computer Dialogue Design. Advances in Human Factors/Ergonomics, 2. Amsterdam: Elsevier Science Publishers B. V.. [Ericsson84] Ericsson, K. A. & Simon, H. A. (1984) Protocol Analysis: Verbal Reports as Data. Cambridge, MA: MIT Press. Comments: This book is the definitive source on analyzing verbal protocols. [Fairley85] Fairley, R. E. (1985) Software Engineering Concepts. New York: McGraw- Hill. Comments: This popular source of general software engineering instruction devotes some, but little space to user interface issues. [Felker81] Felker, D. B., et al. (1981) Guidelines for Document Designers. Washington, DC: American Institutes for Research. [Fischer89] Fischer, G. (1989) Human-Computer Interaction Software: Lessons Learned, Challenges Ahead. IEEE Software, 6, 1, 44-52. [Fisher88] Fisher, S. S., Wenzel, E. M. Coler, C., & McGreevy, M. W. (1988) Virtual Interface Environment Workstations. Proceedings of the Human Factors Society 32nd Annual Meeting. 91-96. [Fitts67] Fitts, P. & Posner, M. I. (1967) Human Performance. Belmont, CA: Brooks/Cole Publishing. Comments: This book presents summaries of many experiments on human performance. [Fleishman84] Fleishman, E. A. & Quaintance, M. K. (1984) Taxonomies of Human Performance: The Description of Human Tasks. New York: Academic Press. [Foley82] Foley, J. D. & van Dam, A. (1982) Fundamentals of Computer Graphics. Reading, MA: Addison-Wesley. Comments: This is an excellent source of information about graphical user interfaces. See Ch. 3 on graphics hardware, and Ch. 5 on devices and techniques. [Foley86a] Foley, J. D. (1986) Guest Editor's Introduction: Special Issue on User Interface Software. ACM Transactions on Graphics, 5, 2-4, 75-78, 175-178, or 279-282. [Foley86b] Foley, J. D. (1986) Managing the Design of User-Computer Interfaces. Washington, DC: Computer Graphics Consultants, Inc. [Foley88a] Foley, J. D., van Dam, A., Feiner, S. & Hughes (1988) Fundamentals of Computer Graphics (2nd Edition). Reading, MA: Addison-Wesley. Comments: The new edition will feature a chapter on user interface software, with sections on interaction handling software, window systems, and user interface management systems. [Foley88b] Foley, J., Gibbs, C., Kim, W. C., & Kovacevic, S. (1988) A Knowledge-Based User Interface Management System. CHI '88 Conference Proceedings, Human Factors in Computing Systems. 67-72. [Foley89] Foley, J., Kim W. C., Kovacevic S., & Murray K. (1989) Defining Interfaces at a High Level of Abstraction. IEEE Software, 6, 1, 25-32. [Fox89] Fox, J. A. & Smith, S. L. (1989) Dynamic Rules for User Interface Design. M89-22, Bedford, MA: The MITRE Corporation. Comments: This report includes a HyperCard stack of the [Smith86a] user interface design guidelines. It is available free of charge with liberal distribution rights for non- profit use. [Galitz81] Galitz, W. O. (1981) Handbook of Screen Format Design. Wellesley, MA: QED Information Sciences. [Goodman87] Goodman, D. (1987) The Complete HyperCard Handbook. New York: Bantam. Comments: HyperCard combines the best aspects of the direct manipulation user interface style with hypertext information processing. HyperCard differs from many systems in that it incorporates enticing visual effects that motivate users. Underlying HyperCard is the HyperTalk language, and an authoring system that makes it easy to prototype interesting applications. HyperCard comes with all new Macintoshes and costs $50 for old Mac users. It requires 700K memory. [Gould85] Gould, J. D. & Lewis, C. (1985) Designing for Usability: Key Principles and What Designers Think. Communications of the ACM, 28, 3, 300- 311. Comments: Reprinted in [Baecker87], p. 528. [Gould87] Gould, J. D., et al. (1987) Why Reading was Slower from CRT Displays than from Paper. CHI '87 Conference on Human Factors in Computing Systems. New York: Association for Computing Machinery. 7- 11. [Greenberg89] Greenberg, R. M. (1989) Faces of Unix. PC Magazine, 8, 15, 143-157. Comments: Long considered an operating system only an engineer could love, UNIX will need a friendlier interface to woo corporate America. [GreenM85a] Green, M. (1985) Design Notations and User Interface Management Systems. In G. E. Pfaff (Ed.) User Interface Management Systems. Berlin: Springer- Verlag. 89-107. [GreenM85b] Green, M. (1985) The University of Alberta User Interface Management System. Computer Graphics, 19. New York: ACM SIGGRAPH. 205-213. [GreenM86] Green, M. (1986) A Survey of Three Dialogue Models. ACM Transactions on Graphics, 5, 3, 244-275. [GreenP85] Green, P. & Wei-Haas, L. (1985) The Rapid Development of User Interfaces: Experience with the Wizard of Oz Method. Proceedings of the Human Factors Society 29th Annual Meeting. Santa Monica, CA: Human Factors Society. 470-474. [Grudin87] Grudin, J. T., Ehrlich, S. F., & Shriner, R. (1987) Positioning Human Factors in the User Interface Development Chain. CHI '87 Conference on Human Factors in Computing Systems. New York: Association for Computing Machinery. 125-131. [Grudin89] Grudin, J., Poltrock, S. E. (1989) User Interface Design in Large Corporations: Coordination and Communication Across Disciplines. CHI '89: Proceedings of Human Factors in Computing Systems. 197-203. [Guilford78] Guilford, J. P. & Fruchter, B. (1978) Fundamental Statistics in Psychology and Education (6e). New York: McGraw- Hill. Comments: This is a good introductory statistics text for the sorts of data collection and analysis activities used in empirical evaluations of system usability. [Hartson86a] Hartson, H. R., et al. (1986) Dialogue Management as Part of Software Engineering Methodology. In R. W. Ehrich and R. C. Williges (Eds.) Human- Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. 35- 107. [Hartson86b] Hartson, H. R., Ehrich, R. W., & Johnson, D. H. (1986) Introducing Dialogue Management. In R. W. Ehrich and R. C. Williges (Eds.) Human- Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. 11- 34. [Hartson89] Hartson, R. (1989) User-Interface Management Control and Communication. IEEE Software, 6, 1, 62-70. [HayesF89] Hayes, F. & Baran, N. (1989) A Guide to GUIs. BYTE, 14, 7, 250-257. Comments: This article introduces several others on GUI's (Graphical User Interfaces). There is some discussion of the Macintosh, work on GUI's for IBM machines, and the UNIX and workstation-based interfaces. [HayesP85] Hayes, P. J., Szekely, P. A., & Lerner, R. A. (1985) Design Alternatives for User Interface Management Systems Based on Experience with COUSIN. In L. Borman and B. Curtis (Eds.) Human Factors in Computing Systems. New York: Association for Computing Machinery. 169-175. [Helander88] Helander, M. (Ed.) (1988) The Handbook of Human Computer Interaction. Amsterdam: North-Holland. Comments: This is a large comprehensive reference source with dozens of papers written by subject areas. The handbook should be consulted for relevant material on any topic on user interfaces. At $250, it is well out of the range of a textbook or even a desktop reference. A table of which chapters cover which topics can be found at the end of the bibliography. [Henderson86a] Henderson, D. A. Jr. & Card, S. K. (1986) Rooms: The Use of Multiple Virtual Workspaces to Reduce Space Contention in a Window-Based Graphical User Interface. ACM Transactions on Graphics, 5, 3, 211-243. [Henderson86b] Henderson, D. A. Jr. (1986) The Trillium User Interface Design Environment. In M. Mantei and P. Orbeton (Eds.) Human Factors in Computing Systems. New York: Association for Computing Machinery. 221-227. Comments: Reprinted in [Baecker87], p. 584. [Hill86] Hill, R. D. (1986) Supporting Concurrency, Communication, and Synchronization in Human-Computer Interaction -- The Sassafras UIMS. ACM Transactions on Graphics, 5, 3, 179- 210. [Hill87] Hill, R. D. (1987) Event Response Systems - A Technique for Specifying Multi-Threaded Dialogues. CHI '87 Conference on Human Factors in Computing Systems. New York: Association for Computing Machinery. 241-248. [Hix86] Hix, D. & Hartson, H. R. (1986) An Interactive Environment for Dialogue Development: Its Design, Use, and Evaluation. In M. Mantei and P. Orbeton (Eds.) Human Factors in Computing Systems. New York: Association for Computing Machinery. 228-234. [Hopgood86] Hopgood F. and A. Robert (Eds.) (1986) Methodology of Window Management. (Proceedings of the April 1985 Alvey Workshop at Cosener's House, U.K.) Berlin: Springer-Verlag. [Houghton84] Houghton, R. C. (1984) Online Help Systems: A Conspectus. Communications of the ACM, 27, 3, 126-133. [Huff54] Huff, D. (1954) How to Lie with Statistics. New York: Norton. Comments: This classic little book takes humorous stabs at meaningless statistics, and teaches students about evaluating empirical research. [Hutchins86] Hutchins, E. L., Hollan, J. D., & Norman, D. A. (1986) Direct Manipulation Interfaces. In D. A. Norman and S. W. Draper (Eds.) User Centered System Design: New Perspectives in Human-Computer Interaction. Hillsdale, NJ: Lawrence Erlbaum Associates. Comments: Reprinted, in part, in [Baecker87], p. 468. [Jacob83a] Jacob, R. J. K. (1983) Using Formal Specifications in the Design of a Human Computer Interface. Communications of the ACM, 26, 4, 259-264. [Jacob83b] Jacob, R. J. K. (1983) Executable Specifications for a Human-Computer Interface. CHI '83 Human Factors in Computing Systems. New York: Association for Computing Machinery. 28-34. [Jacob86] Jacob, R. J. K. (1986) A Specification Language for Direct-Manipulation User Interfaces. ACM Transactions on Graphics, 5, 4, 283-317. [John89] John, B. E. & Newell, A. (1989) Cumulating the Science of HCI: From S-R Compatibility to Transcription Typing. CHI '89: Proceedings of Human Factors in Computing Systems. 109-114. [Johnson86] Johnson, D. H., et al. (1986) The Dialogue Author. 109-163. In R. W. Ehrich and R. C. Williges (Eds.) Human- Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. [Joy80] Joy, W. (1980) termcap: Terminal Independent Operation Routines. Berkeley, CA: Berkeley UNIX Software Distribution, University of California, Berkeley. Comments: This small library of routines works off a database of several hundred descriptions of terminal capabilities and allows the development of terminal-independent applications. It is surprisingly difficult to use and serves as an example of the importance of the human factors in the design of programming tools. [Kantowitz83] Kantowitz, B. H. & Sorkin, R. D. (1983) Human Factors: Understanding People- System Relationships. New York: Wiley. [Kieras85] Kieras, D. E. & Polson, P. G. (1985) An Approach to the Formal Analysis of User Complexity. International Journal of Man-Machine Studies, 22, 4, 365-394. [Kiger84] Kiger, J. I. (1984) The Depth/Breadth Trade-Off in the Design of Menu-Driven User Interfaces. International Journal of Man-Machine Studies, 20, 201-213. [Knox89] Knox, S. T., Bailey, W. A., & Lynch, E. F. (1989) Directed Dialogue Protocols: Verbal Data for User Interface Design. CHI '89: Proceedings of Human Factors in Computing Systems. 283-287. [Lantz87] Lantz, K. A., et al. (1987) Reference Models, Window Systems, and Concurrency. Computer Graphics, 21, 2, 87-97. Comments: Applications should have access to all levels of tools in UIMS; layering is not important, but modularity is. Thus, the application can access the dialogue manager, and each of those can access the workstation agent, and all of them can access device drivers. [Lincoln88] Lincoln, J. E. & Boff, K. R. (1988) Making Behavioral Data Useful for System Design Application: Development of the Engineering Data Compendium. Proceedings of the Human Factors Society 32nd Annual Meeting. 1021-1025. [Lindsay77] Lindsay, P. H. & Norman, D. A. (1977) Human Information Processing: An Introduction to Psychology (2e). New York: Academic Press. Comments: This lively introduction to information processing psychology makes a good supplementary text for user interface design. It is especially good at covering the perceptual and cognitive abilities of the human information processor. It has an experimental and theoretical orientation, so the instructor of a course on user interface development must make the material more concrete with examples. [Linton89] Linton, M. A., Vlissides J. M., & Calder P. R. (1989) Composing User Interfaces with InterViews. IEEE Computer, 22, 1, 8-22. [Litvin87] Litvin, Y. (1987) SKYLIGHTS 3.0. Bedford, MA: Skylights Software. Comments: This is a comprehensive toolkit for design and implementation, showing a good level of device independence. [Mackay89] Mackay, W. (1989) Video as a Research and Design Tool. SIGCHI Bulletin, 21, 2, 48-50. Comments: This article introduces a special issue with several papers on the uses of video for design and evaluation of human-computer interaction. [Mackinlay86] Mackinlay, J. (1986) Automating the Design of Graphical Presentations of Relational Information. ACM Transactions on Graphics, 5, 2, 110- 141. [Mantei88] Mantei, M. M. & Teorey, T. J. (1988) Cost/Benefit Analysis for Incorporating Human Factors in the Software Lifecycle. Communications of the ACM, 31, 4, 428-439. [McCormick85] McCormick, K. A. & Bleser, T. (1985) Developing a User Interface Styleguide. Washington, DC: Computer Graphics Consultants, Inc. [Melkus88] Melkus, L. A. & Torres, J. (1988) Guidelines for the Use of a Prototype in User Interface Design. Proceedings of the Human Factors Society 32nd Annual Meeting. 370-374. [MillerD88] Miller, D. P. (1988) Instant Prototyping Using HyperCard on the Macintosh. Proceedings of the Human Factors Society 32nd Annual Meeting. 362-369. [MillerG56] Miller, G. (1956) The Magical Number Seven Plus or Minus Two: Some Limits on Our Capacity for Processing Information. Psychological Review, 63, 81-97. Comments: This is one of the ten best-known papers in cognitive psychology. It shows the meaning of the limits of human short-term memory. The instructor must supply the implications for applied work. [Molesworth86] Molesworth, L. (1986) User Interface Management Systems. Wang Institute Software Engineering Review, 1, 2, 46- 65. Comments: This is a good survey of what goes into user interface management systems. As part of the survey of features, it goes into depth about a few systems. [Monk84] Monk, A. (1984) Fundamentals of Human- Computer Interaction. New York: Academic Press. Comments: Chapters 5 and 6 reprinted in [Baecker87], p. 138 and 143. [Morris86] Morris, J. H., et al. (1986) Andrew: A Distributed Personal Computing Environment. Communications of the ACM, 29, 3, 184-201. [Mosier86] Mosier, J. N. & Smith, S. L. (1986) Application of Guidelines for Designing User Interface Software. Behaviour and Information Technology, 5, 39-46. Comments: This paper reports on the results of a survey of the users of a comprehensive source of user interface design guidelines. [Myers86] Myers, B. A. & Buxton, W. A. S. (1986) Creating Highly-Interactive and Graphical User Interfaces by Demonstration. Computer Graphics, 20, 4, 249-258. Comments: Reprinted in [Baecker87], p. 595. [Myers87] Myers, B. A. (1987) Creating Dynamic Interaction Techniques by Demonstration. In J. M. Carroll and P. P. Tanner (Eds.) Human Factors in Computing Systems. New York: Association for Computing Machinery. 271-278. [Myers89a] Myers, B. A. (1989) User-Interface Tools: Introduction and Survey. IEEE Software, 6, 1, 15-23. [Myers89b] Myers, B. A. (1989) Encapsulating Interactive Behaviors. CHI '89: Proceedings of Human Factors in Computing Systems. 319-324. [NASA87] NASA (National Aeronautics and Space Administration) (1987) Man-System Integration Standards. NASA-STD-3000, Houston, TX: NASA Johnson Space Center. Comments: This document contains design considerations and example solutions to manned space programs. [Nickerson86] Nickerson, R. S. (1986) Computers: The Human Factors of Information Systems. Cambridge, MA: MIT Press. [Nievergelt80] Nievergelt, J. & Weydert, J. (1980) Sites, Modes, and Trails: Telling the User of and Interactive System Where He Is, What He Can Do, and How to Get Places. In R. A. Guedj, P. J. W. ten Hagen, F. R. A. Hopgood, H. A. Tucker, and D. A. Duce (Eds.) Methodology of Interaction. Amsterdam: North-Holland. Comments: Reprinted in [Baecker87], p. 438. [Norman81] Norman, D. A. (1981) Theory of Action Slips. Psychological Review, 88, 1, 1- 15. [Norman86] Norman D. A. and S. W. Draper (Eds.) (1986) User Centered System Design: New Perspectives in Human-Computer Interaction. Hillsdale, NJ: Lawrence Erlbaum Associates. [Norman88] Norman, D. A. (1988) The Psychology of Everyday Things. New York: Basic Books. Comments: This book is a thoughtful and easy-to-read survey about how devices are and should be designed. [Olsen83] Olsen, D. R. Jr. & Dempsey, E. P. (1983) Syngraph: A Graphical User Interface Generator. Computer Graphics, 17, 43-50. [Olsen86] Olsen, D. R. Jr. (1986) MIKE: A Menu Interaction Kontrol Environment. ACM Transactions on Graphics, 5, 4, 318- 344. [Perlman84] Perlman, G. (1984) Natural Artificial Languages: Low Level Processes. International Journal of Man-Machine Studies, 20, 373-419. Comments: This article shows the application of basic cognitive psychological experiments to the design of a user interface. [Perlman85a] Perlman, G. (1985) Electronic Surveys. Behavior Research Methods, Instruments, and Computers, 17, 2, 203-205. [Perlman85b] Perlman, G. (1985) Making the Right Choices with Menus. In B. Shackel (Ed.) Human-Computer Interaction: INTERACT '84. Amsterdam: North-Holland. 317-321. Comments: This paper shows how experimental evidence can be gathered and applied to the design of user interfaces. Reprinted in [Baecker87], p. 451. [Perlman85c] Perlman, G. (1985) An Overview of the SETOPT Command Line Option Parser Generator. Winter USENIX Conference. El Cerito, CA: Usenix Association. 160- 164. Comments: This paper describes a system that makes it easy for programmers to make their programs easy for people to use. It generates user interface handling code and documentation extracted from the same database, thus ensuring consistency and completeness of the user interface. [Perlman86] Perlman, G. (1986) Multilingual Programming: Coordinating Programs, User Interfaces, On-Line Help, and Documentation. ACM SIGDOC Fourth International Conference on Systems Documentation. New York: ACM Special Interest Group on Documentation. 123- 129. Comments: This paper presents a method based on using a central database from which all shared information about a user interface is drawn. [Perlman87a] Perlman, G. (1987) An Axiomatic Model of Information Presentation. Proceedings of the 1987 Human Factors Society Meeting. Santa Monica, CA: Human Factors Society. 1229-1233. Comments: This paper discusses a model of information presentation in which the structure of the information is represented, rules map differences in structure to differences in presentation attributes, and presentation attributes are mapped onto device- specific attributes. The paper discusses the limitations of approaches that ignore information structure. [Perlman87b] Perlman, G. (1987) The |STAT Handbook (3e). Columbus, OH: |STAT Software. Comments: This compact set of data manipulation and analysis programs is a reasonable data analysis package for educational purposes because it is easy to use and inexpensive. The software runs on the IBM PC ($15) and UNIX ($20) systems, and the handbook costs $10. Copying of the software, for non- profit purposes, is allowed. Available from |STAT Software, 2036 Neil Avenue, Columbus, OH 43210-1277 [Perlman88a] Perlman, G. & Moorhead, A. J. (1988) Applying Hypertext Methods for the Effective Utilization of Standards. Proceedings of the IEEE COMPSTAN '88 Conference on Computer Standards. New York: IEEE Computer Society. 55-59. Comments: This paper discusses a system for accessing the Smith & Mosier (1986) user interface design guidelines online. [Perlman88b] Perlman, G. & Moorhead, A. J. (1988) NaviText SAM 1.0 User Manual. Westford, MA: Northern Lights Software Corporation. Comments: NaviText SAM is an online interface to the Smith & Mosier (1986) user interface design guidelines. It supports a particular design and evaluation method: that of finding relevant guidelines, setting priorities for them, defining rules in terms of important guidelines, and evaluating designs with respect to important guidelines. It is a reasonable system for a design and evaluation assignment. It runs on IBM PC's and costs $295 ($147.50 with 50% educational discount). Available from Northern Lights Software, Box 1599, Westford, MA 01886 [Perlman88c] Perlman, G. (1988) Software Tools for User Interface Development. In M. Helander (Ed.) The Handbook of Human Computer Interaction. Amsterdam: North- Holland. 819-833. Comments: This paper surveys the tools for user interface development, but does not go into much detail about any particular tool. [Perlman88d] Perlman, G. (1988) Teaching User Interface Development to Software Engineers. Proceedings of the Human Factors Society 32nd Annual Meeting. 391-394. [Perlman89a] Perlman, G. (1989) The Checklist Method for Applying Guidelines to Design and Evaluation. Proceedings of INTERFACE 89. 271-276. [Perlman89b] Perlman, G. (1989) Coordinating Consistency of User Interfaces, Code, Online Help, and Documentation with Multilingual/Multitarget Software Specification. In J. Nielsen (Ed.) Coordinating User Interfaces for Consistency. Academic Press. 35-55. [Perlman89c] Perlman, G. (1989) Asynchronous Design/Evaluation Methods for Hypertext Technology Development. Proceedings of Hypertext '89: The Second ACM Conference on Hypertext. 61-81. Comments: This paper introduces the method of specific advantages that allows more plausible comparisons among complex systems. [Petzold89] Petzold, C., Simone, L., & Peterson, T. D. (1989) GUIs for DOS and OS/2. PC Magazine, 8, 15, 111-131. Comments: Microsoft Windows is the right interface for PC users today, but the Presentation Manager will be tomorrow's GUI of choice. [Pfaff85] Pfaff, G. E. (Ed.) (1985) User Interface Management Systems: Proceedings of the Seeheim Workshop. Berlin: Springer-Verlag. Comments: A report of the Seeheim conference on user interface management systems. [Polson87] Polson, P. G. (1987) A Quantitative Theory of Human-Computer Interaction. In J. M. Carroll (Ed.) Interfacing Thought: Cognitive Aspects of Human- Computer Interaction. Cambridge, MA: MIT Press. 184-235. [Poltrock88] Poltrock, S. E. & Foltz, G. S. (1988) APT PC and APT II: Experiment Development Systems for the IBM PC and Apple II. Behavior Research Methods, Instruments, and Computers, 20, 2. Comments: The APT systems are particularly good for doing classic memory experiments such as Peterson and Peterson, free-recall, paired- associate, recognition, etc. They are also good for doing reading comprehension studies or questionnaires. Costs $100. Source code available for an additional $100. Order from: 1423D Bellevue Way N.E., Bellevue, WA 98004 [Radin84] Radin, D. I. (1984) Effects of Command Language Punctuation on Human Performance. Tenth International Symposium on Human Factors in Telecommunications. [Reisner81] Reisner, P. (1981) Formal Grammar and Human Factors Design of an Interactive Graphics System. IEEE Transactions on Software Engineering, 7, 2, 229-240. Comments: This paper is a good example of how a formal model can be used to generate predictions about the usability of a system. It has some problems for practical use because of its flexibility; with so many ways to write a grammar describing a system, the model can adapt to almost any data. [Rich84] Rich, E. (1984) Natural-Language Interfaces. IEEE Computer, 17, 39-47. Comments: Reprinted in [Baecker87], p. 442. [Rose89] Rose, P. F. H. (1989) The Macintosh Finder: Pure GUI. PC Magazine, 8, 32, 133-140. What you've heard is true: Macintosh's Finder is indeed easy to use. But as Apple's developers get more innovative, will Finder stay the same? [Rubinstein84] Rubinstein, R. & Hersh, H. (1984) The Human Factor: Designing Computer Systems for People. Maynard, MA: Digital Press. [Rumelhart78] Rumelhart, D. E. & Norman, D. A. (1978) Accretion, Tuning, and Restructuring: Three Modes of Learning. In J. W. Cotton and R. L. Klatsky (Eds.) Semantic Factors in Cognition. Hillsdale, NJ: Lawrence Erlbaum Associates. [Rumelhart81] Rumelhart, D. E. & Norman, D. A. (1981) Analogical Processes in Learning. In J. R. Anderson (Ed.) Cognitive Skills and Their Acquisition. Hillsdale, NJ: Lawrence Erlbaum Associates. [Rushinek86] Rushinek, A. & Rushinek, S. F. (1986) What Makes Users Happy?. Communications of the ACM, 29, 7, 594-598. [Salvendy87] Salvendy, G. (Ed.) (1987) Handbook of Human Factors. New York: Wiley. Comments: This is a detailed handbook written by topic experts covering all aspects of human factors. Some chapters (each with several papers) deal specifically with computer systems. A table of which chapters cover which topics can be found at the end of the bibliography. [Samuelson89a] Samuelson, P. (1989) Why the Look and Feel of Software User Interfaces Should Not Be Protected by Copyright Law. Communications of the ACM, 32, 5, 563- 572. Comments: An attorney looks at how copyright law is applied to the protection of software user interfaces and makes a strong case for reevaluating the way the law views software. [Samuelson89b] Samuelson, P. (1989) Protecting User Interfaces Through Copyright: The Debate. CHI '89: Proceedings of Human Factors in Computing Systems. 97-103. [Scheifler86] Scheifler, R. W. & Gettys, J. (1986) The X Window System. ACM Transactions on Graphics, 5, 2, 79-109. Comments: This paper contains a high-level description of the influential X windows system. [Schmucker86a] Schmucker, K. (1986) MacApp: An Application Framework. BYTE, 11, 8, 189-193. Comments: Reprinted in [Baecker87], p. 591. [Schmucker86b] Schmucker, K. (1986) Object-Oriented Languages for the Macintosh. BYTE, 11, 8, 177-188. [Schneider88] Schneider, W. (1988) Micro Experimental Laboratory: An Integrated System for IBM PC Compatibles. Behavior Research Methods, Instruments, and Computers, 20, 2. Comments: Costs $495 for professional use, $295 for instructional use, $49 for additional versions to run experiments (without program development or analysis parts)). Order from: Psychology Software Tools, Inc., 511 Bevington Road, Pittsburgh, PA 15221, (412) 244-1908 [Seymour89] Seymour, J. (1989) The GUI: An Interface You Won't Outgrow. PC Magazine, 8, 15, 97-109. Comments: Graphical user interfaces are popping up all over the PC industry. This guide will help you make the move from today's command line interface to tomorrow's GUI. [Sherwin86] Sherwin, L. C. & Perlman, G. (1986) Designing Menu Format to Match Input Device Format. Wang Institute Software Engineering Review, 1, 2, 78-83. [Shneiderman80] Shneiderman, B. (1980) Software Psychology. Cambridge, MA: Winthrop. Comments: This book presents issues about software data collection and the best-known models of software complexity. It was the first such survey and has been the most cited source in the area of user interfaces; but it is now dated material and is superseded by Shneiderman (1986). [Shneiderman83] Shneiderman, B. (1983) Direct Manipulation: A Step Beyond Programming Languages. IEEE Computer, 16, 57-69. Comments: Reprinted (in part) in [Baecker87], p. 461. [Shneiderman87] Shneiderman, B. (1987) Designing the User Interface: Strategies for Effective Human-Computer Interaction. Reading, MA: Addison-Wesley. Comments: This is probably the best text book on user interface design, although I would be tempted to also use Smith & Mosier (1986). [Shulert85] Schulert, A. J., Rogers, G. T., & Hamilton, J. A. (1985) ADM - A Dialog Manager. In L. Borman and B. Curtis (Eds.) Human Factors in Computing Systems. New York: Association for Computing Machinery. 177-183. [Sibert86] Sibert, J. L., Hurley, W. D., & Bleser, T. W. (1986) An Object Oriented User Interface Management System. Computer Graphics, 20, 4, 259-268. [SIGGRAPH87] Seattle UIMS Workshop (1987) Special Issue on the Seattle UIMS Workshop. Computer Graphics, 21, 2, New York: Association for Computing Machinery. Comments: In November of 1986, the ACM SIGGRAPH Workshop on Software Tools for User Interface Management was held at the Battelle Conference Center in Seattle, Washington. The purpose was to synthesize new ideas and direction for future research through discussion and interchange. [SmethersBarnes88] SmethersBarnes (1988) Prototyper 1.0. Portland, OR: SmethersBarnes. Comments: A Macintosh tool for interactive prototyping with Pascal code generation. The 2.0 version also generates C. [Smith86a] Smith, S. L. & Mosier, J. N. (1986) Guidelines for Designing User Interface Software. Report #MTR-10090, ESD-TR-86- 278, Bedford, MA: The MITRE Corporation. Comments: A monumental work that is a required reference for any user interface designer. It is a reasonable textbook because of its thoughtful introductions. It contains 944 guidelines in six sections. [Smith86b] Smith, S. L. (1986) Standards Versus Guidelines for Designing User Interface Software. Behaviour and Information Technology, 5, 47-61. [Solso84] Solso, R. L. & Johnson, H. H. (1984) An Introduction to Experimental Design in Psychology: A Case Approach (3e). New York: Harper & Row. Comments: This is a great introduction to experimental design. It is very good at explaining the terminology and subtle logic. [Streveler85] Streveler, D. J. & Wasserman, A. I. (1985) Quantitative Measures of the Spatial Properties of Screen Designs. In B. Shackel (Ed.) Human-Computer Interaction: INTERACT '84. Amsterdam: North-Holland. 81-89. [Strunk79] Strunk, W. & White, E. B. (1979) The Elements of Style. (3e) New York: Macmillan Publishing Company. [Tennant83] Tennant, H. R., Ross, K. M., & Thompson, C. W. (1983) Usable Natural Language Interfaces Through Menu-Based Natural Language Understanding. CHI '83 Human Factors in Computing Systems. New York: Association for Computing Machinery. 154-160. [Thakkar90] Thakkar, U., Perlman, G., & Miller, D. (1990) Evaluation of the NeXT Interface Builder for Prototyping a Smart Telephone. ACM SIGCHI Bulletin, 21, 3, 80-85. [Thomas87] Thomas, J. and M. Schneider (Eds.) (1987) Human Factors in Computer Systems. New York: Ablex Publishing. [Thomas89] Thomas, J. C. & Kellogg, W. A. (1989) Minimizing Ecological Gaps in Interface Design. IEEE Software, 6, 1, 78-86. [Tufte83] Tufte, E. R. (1983) The Visual Display of Quantitative Information. Cheshire, CT: Graphics Press. Comments: This is a great book on making graphs. [Tullis81] Tullis, T. S. (1981) An Evaluation of Alphanumeric, Graphic, and Color Information Displays. Human Factors, 23, 541-550. [Tullis83a] Tullis, T. S. (1983) Predicting the Usability of Alphanumeric Displays. UCLA Dissertation. [Tullis83b] Tullis, T. S. (1983) The Formatting of Alphanumeric Displays: A Review and Analysis. Human Factors, 25, 6, 657. [Tullis85] Tullis, T. S. (1985) A Computer-Based Tool for Evaluating Alphanumeric Displays. In B. Shackel (Ed.) Human- Computer Interaction: INTERACT '84. Amsterdam: North-Holland. 719-723. [Tullis86] Tullis, T. S. (1986) Display Analysis Program User Manual. Lawrence, KS: Report Store. Comments: Tom Tullis's display analysis program runs on the IBM PC and costs about $90. It has more advanced capabilities than those described in Tullis' influential thesis, but it still lacks the intelligence software developers would want. It is useful for class demonstrations, but don't expect students to want it. [Tullis87] Tullis, T. S. An Evaluation of Screen-Building Systems for the IBM PC. Comments: Available from the author at: McDonnell Douglas Astronautics Company, 5301 Bolsa Avenue, Huntington Beach, CA 92647. [USC89] Usability Sciences Corporation (1989) TestLogr. Irving, Texas: Usability Sciences Corporation. Comments: This PC tool allows you to code, edit, and analyze temporal data such as that seen in video protocols. [Vo85] Vo, K.-P. (1985) IFS - A Tool to Build Integrated, Interactive Application Software. AT&T Technical Journal, 64, 9, 2097-2117. [Walker88] Walker, J. H. (1988) Supporting Document Development with Concordia. IEEE Computer, 21, 1, 48-59. [Wasserman79] Wasserman, A. I. (1979) USE: A Methodology for the Design and Development of Interactive Information Systems. In H. J. Schneider (Ed.) Formal Models and Practical Tools for Information System Design. Amsterdam: North-Holland. 31-50. [Wasserman85] Wasserman, A. I. (1985) Extending State Transition Diagrams for the Specification of Human-Computer Interaction. IEEE Transactions on Software Engineering, 11, 8, 699-713. Comments: Reprinted in [Baecker87], p. 561. [Wasserman86] Wasserman, A. I., et al. (1986) Developing Interactive Systems with the User Software Engineering Methodology. IEEE Transactions on Software Engineering, 12, 2, 326-345. Comments: Reprinted in [Baecker87], p. 508. [Webster89] Webster, B. F. (1989) The NeXT Book. Reading, MA: Addison-Wesley. Comments: This book provides a tutorial overview of the NeXT machine and its programming environment, notably NeXTStep and the Interface Builder. [Wickens84] Wickens, C. D. (1984) Engineering Psychology and Human Performance. Columbus, OH: Charles E. Merrill Publishing. Comments: This book attempts to "bridge the gap between the problems of systems design and much of the excellent theoretical research in cognitive experimental psychology and human performance." [Wiecha89] Wiecha, C., Bennett, W. Boies, S. & Gould, J. (1989) Generating Highly Interactive User Interfaces. CHI '89: Proceedings of Human Factors in Computing Systems. 277-282. [Williams82] Williams, M. & Tou, F. (1982) RABBIT: An Interface for Database Access. Proceedings of the 1982 ACM Conference. New York: Association for Computing Machinery. Comments: This system is reminiscent of the QBE (Query by Example) method of database access. Rabbit differs in that it always presents the user with an example of a record that matches the current query. The user can look at the possibilities for any field and require that attributes be present or absent, and during this process, Rabbit composes a query. [WilligesB84] Williges, B. H. & Williges, R. C. (1984) Dialogue Design Considerations for Interactive Computer Systems. In F. A. Muckler (Ed.) Human Factors Review: 1984. Santa Monica, CA: Human Factors Society. 167-208. [WilligesB86] Williges, B. H., et al. (1986) Using Speech in the Human-Computer Interface. In R. W. Ehrich and R. C. Williges (Eds.) Human-Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. 241-271. [WilligesR86a] Williges, R. C. & Hartson, H. Rex (1986) Human-Computer Dialogue Design and Research Issues. In R. W. Ehrich and R. C. Williges (Eds.) Human- Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. 367- 376. [WilligesR86b] Williges, R. C., et al. (1986) User Assistance in Human-Computer Interfaces. In R. W. Ehrich and R. C. Williges (Eds.) Human-Computer Dialogue Design. Amsterdam: Elsevier Science Publishers B. V.. 291-317. [Wong82] Wong, P. C. S. & Reid, E. R. (1982) Flair: User Interface Design Tool. Computer Graphics, 16, 3, 87-98. [Woodson87] Woodson, W. E. (1987) Human Factors Reference Guide for Electronics and Computer Professionals. New York: McGraw-Hill. Comments: This book is primarily concerned with physical operator interfaces, but there it does contain useful information about designing visual displays. [Wright83] Wright, P. (1983) Manual Dexterity: A User-Oriented Approach to Creating Computer Documentation. CHI '83 Conference on Human Factors in Computing Systems. New York: Association for Computing Machinery. Comments: Reprinted in [Baecker87], p. 613. |Lifecycle | |DESIGN | | |Task | | | |Psych | | | | |Device | | | | | |Dialogue | | | | | | |Guidelines | | | | | | | |Prototype | | | | | | | | |Specification | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | |UIMS | | | | | | | | | | | |Windows | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | |TOOL Helander_1______| |#|#| | | | | | | | | | | | | | | Helander_2______| |#|#| | | | | | | | | | | | | | | Helander_3______| |#|#| | | | | | | | | | | | | | | Helander_4______| | | | | | | | | | | | | | | | | | Helander_5______| | | | | | | | | | | | | | | | | | Helander_6______| |#| | |#|#| | | |#| | | | | | | | Helander_7______| | | |#| | | | | | | | | |#| |#| | Helander_8______| | | |#| | | | | | | | | | | |#| | Helander_9______| |#|#| | | | | | | | | | | | | | | Helander_10_____| |#| | | |#| | | | | | | | | | | | Helander_11_____| |#| | | |#| | | | | | | | | | | | Helander_12_____| |#| | | |#| | | | | | | | | | | | Helander_13_____| |#| | | |#| | | | | | | | | | | | Helander_14_____| |#| | |#|#| | | | | | | | | | | | Helander_15_____| |#| | |#|#| | | | | | | | | | | | Helander_16_____| | | | | | | | | | | | |#| | | | | Helander_17_____| |#| | | |#| |#| | | | | | | | | | Helander_19_____| |#| | | | | |#| | | |#| | | | | | Helander_19_____| |#| | | |#| | | | | |#| | | | | | Helander_20_____| |#| | |#| | | | | | | | | | | | | Helander_21_____| |#| | |#| | | | | | | | | | | | | Helander_22_____| |#| | |#| | | | | | | | | | | | | Helander_23_____| | | | |#| | | | | | | | | | | | | Helander_24_____| |#| | | | | | | | | | | | | | | | Helander_25_____| |#| | | | | | | | | | | | | | | | Helander_26_____| |#| | | | | | | | | | | | | | | | Helander_27_____| | | | | | | | | | | | |#| | | | | Helander_28_____| | | | | | | | | | | | |#| | | | | Helander_29_____| | | | | | | | | | | | | | | | | | Helander_30_____| | | | | | | | | | | | | | | | | | Helander_31_____| | | | | | | | | | | | | | | | | | Helander_32_____| | | | | | | | | | | | | | | | | | Helander_33_____| | | | | | | | | | | | | | | | | | Helander_34_____| | | | | | | | | | | | | | | | | | Helander_35_____| |#|#| | | |#| | | | | | |#|#| | | Helander_36_____| | | | | | | | | | | | | |#|#| | | Helander_37_____| |#| | | | | | | |#| | | |#| | |#| Helander_38_____| |#|#| | | | | | | | | | | | | | | Helander_39_____| |#| | | | | |#| | | | | | | | |#| Helander_40_____| |#| | | | |#| | | | | | | | | | | Helander_41_____| | | | | | | | | | | | | |#|#|#| | Helander_42_____| |#|#|#| | | | | | | | | |#|#|#| | Helander_43_____| | | | | | | | | | | | | | | | | | Helander_44_____| |#| | | |#| | | | | | | | | | | | Helander_45_____| | | | | | | | | | | | | | | | | | Helander_46_____| |#| | | | | | | | | | | | | | | | Helander_47_____| | | | | | | | | | | | | | | |#| | Helander_48_____| |#|#|#| | | | | | | | | | | | | | Helander_49_____| | | | | | | | | | | | | | | | | | Helander_50_____| | | | | | | | | | | | | | | | | | Helander_51_____| | | | | | | | | | | | | | | | | | Helander_52_____| | | | | | | | | | | | | | | | | | |Lifecycle | |DESIGN | | |Task | | | |Psych | | | | |Device | | | | | |Dialogue | | | | | | |Guidelines | | | | | | | |Prototype | | | | | | | | |Specification | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | |UIMS | | | | | | | | | | | |Windows | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | |TOOL Salvendy_1.2____|#| | | | | | | | | | | | | | | | | Salvendy_2.1____| |#| |#| | | | | | | | | | | | | | Salvendy_2.2____| |#| |#| | | | | | | | | | | | | | Salvendy_2.3____| |#| |#| | | | | | | | | | | | | | Salvendy_2.4____| |#| |#| | | | | | | | | | | | | | Salvendy_2.8____| |#| |#| | | | | | | | | | | | | | Salvendy_2.9____| | | |#| | | | | | | | | | | | | | Salvendy_2.10___| |#| |#|#| | | | | | | | | | | | | Salvendy_3.1____| |#|#| | | | | | | | | | | | | | | Salvendy_3.2____| |#|#| | | | | | | | | | | | | | | Salvendy_3.3____| |#|#| | | | | | | | | | | | | | | Salvendy_3.4____| |#|#| | | | | | | | | | | | | | | Salvendy_3.5____| | | |#| | | | | | | | | | | | | | Salvendy_4.4____| |#| | | | | | | | | | | | | | | | Salvendy_5.1____| |#| | |#| | |#| | | | | | | | | | Salvendy_5.2____| |#| | |#| | | | | | | | | | | | | Salvendy_5.3____| |#| | |#| | | | | | | | | | | | | Salvendy_6.3____| | | | |#| | | | | | | | | | | | | Salvendy_8.2____| | | | | | | | | | | | |#| | | | | Salvendy_8.3____| | | | | | | | | | | | |#| | | | | Salvendy_8.4____| | | | | | | | | | | | |#| | | | | Salvendy_8.5____| | | | | | | | | | | | |#| | | | | Salvendy_8.6____| | | | | | | | | | | | |#| | | | | Salvendy_9.1____| | | | | | | | | | | | | | | |#| | Salvendy_9.4____| | | | | | | | | | | | | | | |#| | Salvendy_9.5____| | | |#| | | | | | | | | | | |#| | Salvendy_9.6____| | | |#| | | | | | | | | | | |#| | Salvendy_10.1___| | | | | | | | | | | | | |#|#| | | Salvendy_10.2___| | | | | | | | | | | | | |#| | | | Salvendy_10.3___| | | | | | | | | | | | | |#| | | | Salvendy_11.1___| |#| | |#| | | | | | | | | | | | | Salvendy_11.4___| |#| | |#| | | | | | | | | | | | | Salvendy_11.5___| |#| | |#| | | | | | | | | | | | | Salvendy_11.7___| | | | | | | | | | | | |#| | | | | |book | |manual | | |GENERAL | | | |Lifecycle | | | | |DESIGN | | | | | |Task | | | | | | |Psych | | | | | | | |Device | | | | | | | | |Dialogue | | | | | | | | | |Guidelines | | | | | | | | | | |Prototype | | | | | | | | | | | |Specification | | | | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | | | | |UIMS | | | | | | | | | | | | | | |Windows | | | | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | | | | |TOOL | | | | | | | | | | | | | | | | | | | | |MAC | | | | | | | | | | | | | | | | | | | | | |IBM | | | | | | | | | | | | | | | | | | | | | | |UNIX AERA85___________|#| | | | | | | | | | | | | | | |#|#| | | | | | APA82____________|#| | | | | | | | | | | | | | | |#|#| | | | | | Apple85__________| |#| | | | | | | | | | |#| | | | | | |#|#| | | Apple87__________| |#| | |#| | | | |#| | | | | | | | | | |#| | | Arnold81_________| |#| | | | | | | | | | |#| | | | | | |#| | |#| Baecker87________|#| |#|#|#| |#|#| | |#|#|#|#|#|#|#|#|#|#| | | | Bailey82_________|#| |#| |#|#|#| | | | | | | | | |#| | | | | | | Bailey83_________|#| | | |#| | | | | | | | | | | | | | | | | | | Barnard88________| | | | |#| | | |#| | | | | | | | | | | | | | | Barth86__________| | | | | | | | |#| | | |#| | | | | | | | | | | Bass85___________| | | | |#| | | | | | |#|#| | | | | | | | | | | Bass89___________| | | | | | | | | | | |#|#|#|#| | | | |#| | |#| Beaudet88________| | | | | | | | | | | | | | | | |#|#| | | | | | Bennett87________| | | |#| | | | | | | | |#|#| | | | | |#| | | | Berry85__________| | | | | | | | | | | | | | | | |#| |#| | | | | Borning86________| | | | | | | | | | | | |#| | | | | | |#| | | | Bricklin86_______| |#| | |#| | | | | |#|#| | | | | | | |#| |#| | Brown88__________|#| | | |#| | | |#|#| | | | | | | | | | | | | | Buxton83_________| | | | | | | | | | | | |#|#| | | | | |#| | | | Buxton86_________| | | | |#| | |#| | | | | | | | | | | | | | | | Campbell74_______|#| | | | | | | | | | | | | | | |#|#| | | | | | Card78___________| | | | |#| | |#| | | | | | | | | | | | | | | | Card80___________| | | | | | | | | | | | | | | | |#|#|#| | | | | Card83___________|#| |#| |#| |#| | | | | | | | | |#| |#| | | | | Card85___________| | | | |#| | | |#| | | |#| |#| | | | | | | | | Carroll85________| | | | | | | | | | | | |#| | |#| | | | | | | | Carroll87a_______| | | | | | | | | | | | |#| | |#| | | | | | | | Carroll87b_______|#| | | |#| | | | | | | | | | | |#| | | | | | | Chi85____________| | | | |#| | | | | | |#|#| | | | | | | | | | | Chin88___________| | | | | | | | | | | | | | | | |#|#| | | | | | Cleveland85______|#| | | | | | | | | | | | | | | |#|#| | | | | | Conklin87________| | | | | | | | | | | | |#| | |#| | | | | | | | Coutaz84a________| | | | | | | | | | | | |#| | | | | | |#| | | | Coutaz84b________| | | | | | | | | | | | |#| | | | | | |#| | | | Coutaz87_________| | | | | | | | | | | | |#| | | | | | |#| | | | Cox86____________| | | | | | | | |#| | | |#| | | | | | |#| | | | DOD83____________|#| | | |#| | |#| |#| | | | | | | | | | | | | | DOD83____________|#| | | |#| | | | |#| | | | | | | | | | | | | | DOD85____________|#| | | |#| | | | |#| | | | | | | | | | | | | | DeSoi89__________| | | | |#| | | | | |#|#|#| | | | | | | | | | | Drury87__________| | | | |#|#| | | | | | | | | | |#|#| | | | | | Ehrich86_________|#| | | |#| | | | | | |#|#| | | | | | | | | | | Ericsson84_______|#| | | | | | | | | | | | | | | |#|#| | | | | | |book | |manual | | |GENERAL | | | |Lifecycle | | | | |DESIGN | | | | | |Task | | | | | | |Psych | | | | | | | |Device | | | | | | | | |Dialogue | | | | | | | | | |Guidelines | | | | | | | | | | |Prototype | | | | | | | | | | | |Specification | | | | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | | | | |UIMS | | | | | | | | | | | | | | |Windows | | | | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | | | | |TOOL | | | | | | | | | | | | | | | | | | | | |MAC | | | | | | | | | | | | | | | | | | | | | |IBM | | | | | | | | | | | | | | | | | | | | | | |UNIX Fairley85________|#| | | |#| | | | |#| | | | | | | | | | | | | | Felker81_________|#| | | | | | | | | | | |#| | |#| | | | | | | | Fischer89________| | | | | | | | | | | | |#| | | | | | |#| | | | Fisher88_________| | | | |#| | |#| | | | | | | | | | | | | | | | Fitts67__________|#| | | |#| |#|#| | | | | | | | | | | | | | | | Fleishman84______|#| | | |#|#| | | | | | | | | | | | | | | | | | Foley82__________|#| | | |#| | | | | | | |#| | | | | | | | | | | Foley86a_________| | | | | | | | | | | | |#| | | | | | | | | | | Foley86b_________| | | |#| | | | | | | | | | | | | | | | | | | | Foley88__________|#| | | |#| | | |#| | | |#| |#| | | | | | | | | Foley88b_________| | | | | | | | | | | |#|#|#| | | | | |#| | | | Foley89__________| | | | |#| | | | | | |#|#|#| | | | | | | | | | Fox89____________| | | | |#| | | | |#| | | | | | | | | |#|#| | | Galitz81_________|#| | | |#| | | | | |#| | | | | | | | | | | | | Goodman87________|#| | | |#| | | | | |#| |#| | | | | | |#|#| | | Gould85__________| | | |#|#| | | | | | | | | | | | | | | | | | | Gould87__________| | | | |#| | |#| | | | | | | | | | | | | | | | GreenM85a________| | | | |#| | | | | | |#|#|#| | | | | | | | | | GreenM85b________| | | | | | | | | | | | |#|#| | | | | |#| | | | GreenM86_________| | | | |#| | | | | | |#|#| | | | | | | | | | | GreenP85_________| | | | |#| | | | | |#| | | | | | |#| | | | | | Greenberg89______| | | | | | | | | | | | |#| |#| | | | |#| | |#| Grudin87_________| | | |#| | | | | | | | | | | | | | | | | | | | Grudin89_________| | | |#| | | | | | | | | | | | | | | | | | | | Guilford78_______|#| | | | | | | | | | | | | | | |#|#| | | | | | Hartson86a_______| | | |#| | | | | | | | | | | | | | | | | | | | Hartson86b_______| | | | |#| | | | | | | |#| | | | | | | | | | | Hartson89________| | | | | | | | | | | |#|#|#| | | | | | | | | | HayesF89_________| | | | | | | | | | | | |#| |#| | | | |#|#|#|#| HayesP85_________| | | | | | | | | | | | |#| | | | | | |#| | | | Helander88_______|#| |#|#|#|#|#|#|#|#|#|#|#| | |#|#|#|#| | | | | Henderson86a_____| | | | |#| | | | | | | |#| |#| | | | | | | | | Henderson86b_____| | | | |#| | | | | |#| |#| | | | | | |#| | | | Hill86___________| | | | | | | | | | | | |#|#| | | | | |#| | | | Hill87___________| | | | | | | | | | | | |#| | | | | | |#| | | | Hix86____________| | | | | | | | | | | | |#| | | | | | |#| | | | Hopgood86________|#| | | | | | | |#| | | |#| |#| | | | | | | | | Houghton84_______| | | | | | | | | | | | |#| | |#| | | | | | | | Huff54___________|#| | | | | | | | | | | | | | | |#|#| | | | | | Hutchins86_______| | | | |#| | | |#| | | | | | | | | | | | | | | Jacob83a_________| | | | |#| | | | | | |#|#| | | | | | | | | | | Jacob83b_________| | | | |#| | | | | | |#|#| | | | | | | | | | | Jacob86__________| | | | |#| | | | | | |#|#| | | | | | | | | | | |book | |manual | | |GENERAL | | | |Lifecycle | | | | |DESIGN | | | | | |Task | | | | | | |Psych | | | | | | | |Device | | | | | | | | |Dialogue | | | | | | | | | |Guidelines | | | | | | | | | | |Prototype | | | | | | | | | | | |Specification | | | | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | | | | |UIMS | | | | | | | | | | | | | | |Windows | | | | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | | | | |TOOL | | | | | | | | | | | | | | | | | | | | |MAC | | | | | | | | | | | | | | | | | | | | | |IBM | | | | | | | | | | | | | | | | | | | | | | |UNIX John89___________| | | | |#| |#| | | | | | | | | |#| |#| | | | | Johnson86________| | | | | | | | | | | | |#| | | | | | | | | | | Joy80____________| |#| | | | | |#| | | | |#| | | | | | |#| | |#| Kantowitz83______|#| |#| |#|#|#| | | | | | | | | |#| | | | | | | Kieras85_________| | | | | | |#| | | | | | | | | |#| |#| | | | | Kiger84__________| | | | |#| | | |#| | | | | | | | | | | | | | | Knox89___________| | | | | | | | | | | | | | | | |#|#| | | | | | Lantz87__________| | | | | | | | | | | | |#| | | | | | |#| | | | Lincoln88________| | | | |#| |#|#| |#| | | | | | | | |#| | | | | Lindsay77________|#| | | |#| |#| | | | | | | | | | | | | | | | | Linton89_________| | | | | | | | | | | | |#| |#| | | | |#| | | | Litvin87_________| |#| | |#| | | | | | | |#| | | | | | |#| |#| | Mackay89_________| | | | | |#| | | | | | | | | | |#|#| | | | | | Mackinlay86______| | | | | | | | | | | | |#| | | |#| | | | | | | Mantei88_________| | | |#| | | | | | | | | | | | | | | | | | | | McCormick85______| | | | |#| | | | |#| | | | | | | | | | | | | | Melkus88_________| | | | |#| | | | |#|#| | | | | | | | | | | | | MillerD88________| | | | |#| | | | | |#| | | | | | | | |#|#| | | MillerG56________| | | | |#| |#| | | | | | | | | | | | | | | | | Molesworth86_____| | | | | | | | | | | | |#|#| | | | | |#| | | | Monk84___________|#| |#| |#| | | | | | | |#| | | |#| | | | | | | Morris86_________| | | | | | | | | | | | |#|#|#| | | | |#| | |#| Mosier86_________| | | | |#| | | | |#| | | | | | | | | | | | | | Myers86__________| | | | |#| | | | | |#| |#| | | | | | |#| | | | Myers87__________| | | | |#| | | | | |#| |#| | | | | | |#| | | | Myers89a_________| | | | | | | | | | | | |#| | | | | | |#| | | | Myers89b_________| | | | |#| | | |#| | |#|#| | | | | | | | | | | NASA87___________|#| | | |#| | | | |#| | | | | | | | | | | | | | Nickerson86______|#| |#| |#| | | | | | | | | | | | | | | | | | | Nievergelt80_____| | | | |#| | | | | | | | | | |#| | | | | | | | Norman81_________| | | | |#| |#| | | | | | | | | | | | | | | | | Norman86_________|#| | | |#| | | | | | | | | | | | | | | | | | | Norman88_________|#| | | |#| | | | | | | | | | | | | | | | | | | Olsen83__________| | | | | | | | | | | | |#|#| | | | | |#| | | | Olsen86__________| | | | | | | | | | | | |#|#| | | | | |#| | | | Perlman84________| | | | |#| | | |#| | | | | | | | | | | | | | | Perlman85a_______| | | | | | | | | | | | | | | | |#|#| | | | | | Perlman85b_______| | | | | | | | |#| | | |#| | | | | | |#| | |#| Perlman85c_______| | | | | | | | | | | | | | | | |#|#| | | | | | Perlman86________| | | | | | | | | | | | |#| | |#| | | | | | | | Perlman87a_______| | | | | | | | | | | | | | | | |#| |#| | | | | Perlman87b_______| |#| | | | | | | | | | | | | | |#|#| |#| |#|#| Perlman88a_______| | | | |#| | | | |#| | | | | | |#|#| |#| |#| | |book | |manual | | |GENERAL | | | |Lifecycle | | | | |DESIGN | | | | | |Task | | | | | | |Psych | | | | | | | |Device | | | | | | | | |Dialogue | | | | | | | | | |Guidelines | | | | | | | | | | |Prototype | | | | | | | | | | | |Specification | | | | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | | | | |UIMS | | | | | | | | | | | | | | |Windows | | | | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | | | | |TOOL | | | | | | | | | | | | | | | | | | | | |MAC | | | | | | | | | | | | | | | | | | | | | |IBM | | | | | | | | | | | | | | | | | | | | | | |UNIX Perlman88b_______| |#| | |#| | | | |#| | | | | | |#|#| |#| |#| | Perlman88c_______| | | | |#| | | | | | | |#| | | |#| | |#| | | | Perlman88d_______| | | | | | | | | | | | | | | | | | | | | | | | Perlman89a_______| | | | |#| | | | |#| | | | | | |#| | |#| | | | Perlman89b_______| | | | |#| | | |#| |#|#|#| | |#| | | | | | | | Perlman89c_______| | | |#|#|#| | | |#| | | | | |#|#|#| |#| |#| | Petzold89________| | | | | | | | | | | | |#| |#| | | | |#| |#| | Pfaff85__________|#| | | | | | | | | | | |#|#| | | | | |#| | | | Polson87_________| | | | | | |#| | | | | | | | | |#| |#| | | | | Poltrock88_______| | | | |#| | | | | | | | | | | |#|#| |#| |#| | Radin84__________| | | | |#| | | |#| | | | | | | | | | | | | | | Reisner81________| | | | | | | | | | | | | | | | |#| |#| | | | | Rich84___________| | | | |#| | | |#| | | | | | | | | | | | | | | Rose89___________| | | | |#| | | | | | | |#| |#| | | | |#|#| | | Rubinstein84_____|#| | | |#|#| | | | | | | | | | | | | | | | | | Rumelhart78______| | | | |#| |#| | | | | | | | | | | | | | | | | Rumelhart81______| | | | |#| |#| | | | | | | | | | | | | | | | | Rushinek86_______| | | | | | | | | | | | | | | | |#| | | | | | | SIGGRAPH87_______|#| | | | | | | | | | | |#|#|#| | | | |#| | | | Salvendy87_______|#| |#|#|#|#|#|#|#|#| | | | | |#|#|#| | | | | | Samuelson89a_____| | | | |#| | | | | | | | | | | | | | | | | | | Samuelson89b_____| | | | |#| | | | | | | | | | | | | | | | | | | Scheifler86______| | | | | | | | | | | | |#| |#| | | | |#| | |#| Schmucker86a_____| | | | | | | | | | | | |#| | | | | | |#|#| | | Schmucker86b_____| | | | | | | | | | | | |#| | | | | | |#|#| | | Schneider88______| | | | |#| | | | | | | | | | | |#|#| |#| |#| | Seymour89________| | | | | | | | | | | | |#| |#| | | | |#| | | | Sherwin86________| | | | |#| | | |#| | | | | | | | | | | | | | | Shneiderman80____|#| | | |#| | | | | | | | | | | |#|#| | | | | | Shneiderman83____| | | | |#| | | |#| | | | | | | | | | | | | | | Shneiderman87____|#| |#| |#|#|#|#|#|#|#| | | | |#|#|#|#| | | | | Shulert85________| | | | | | | | | | | | |#|#| | | | | |#| | | | Sibert86_________| | | | | | | | | | | | |#|#| | | | | |#| | | | SmethersBarnes88_| |#| | |#| | | |#| |#| |#| | | | | | |#|#| | | Smith86a_________|#| | | |#| | | |#|#| | | | | | | | | | | | | | Smith86b_________| | | | |#| | | | |#| | | | | | | | | | | | | | Solso84__________|#| | | | | | | | | | | | | | | |#|#| | | | | | Streveler85______| | | | | | | | | | | | | | | | |#| |#| | | | | Strunk79_________|#| | | | | | | | | | | |#| | |#| | | | | | | | Tennant83________| | | | |#| | | |#| | | |#| | | | | | | | | | | Thakkar90________| | | | | | | | | | |#| |#| | | |#|#| |#| | | | Thomas87_________|#| |#| | | | | | | | | | | | | | | | | | | | | Thomas89_________| | | | |#| | | | | | | | | | | | |#| | | | | | |book | |manual | | |GENERAL | | | |Lifecycle | | | | |DESIGN | | | | | |Task | | | | | | |Psych | | | | | | | |Device | | | | | | | | |Dialogue | | | | | | | | | |Guidelines | | | | | | | | | | |Prototype | | | | | | | | | | | |Specification | | | | | | | | | | | | |IMPLEMENTATION | | | | | | | | | | | | | |UIMS | | | | | | | | | | | | | | |Windows | | | | | | | | | | | | | | | |Guidance | | | | | | | | | | | | | | | | |EVALUATION | | | | | | | | | | | | | | | | | |Empirical | | | | | | | | | | | | | | | | | | |Model | | | | | | | | | | | | | | | | | | | |TOOL | | | | | | | | | | | | | | | | | | | | |MAC | | | | | | | | | | | | | | | | | | | | | |IBM | | | | | | | | | | | | | | | | | | | | | | |UNIX Tufte83__________|#| | | | | | | | | | | | | | | |#|#| | | | | | Tullis81_________| | | | | | | | | | | | | | | | |#| |#| | | | | Tullis83a________| | | | | | | | | | | | | | | | |#| |#| | | | | Tullis83b________| | | | | | | | | | | | | | | | |#| |#| | | | | Tullis85_________| | | | | | | | | | | | | | | | |#| |#|#| | | | Tullis86_________| |#| | | | | | | | | | | | | | |#| |#|#| |#| | Tullis87_________| | | | |#| | | | | | | |#| | | | | | |#| |#| | USC89____________| |#| | |#| | | | | | | | | | | |#|#| |#| |#| | Vo85_____________| | | | | | | | | | | | |#|#| | | | | |#| | |#| Walker88_________| | | | | | | | | | | | |#| | |#| | | | | | | | Wasserman79______| | | | | | | | | | | | |#| | | | | | |#| | |#| Wasserman85______| | | | |#| | | | | | |#|#| | | | | | |#| | |#| Wasserman86______| | | | |#|#| | | | | |#|#| | | | | | |#| | | | Webster89________|#|#| | | | | | | | |#| |#| |#| | | | |#| | | | Wickens84________|#| | | |#| |#| | | | | | | | | | | | | | | | | Wiecha89_________| | | | |#| | | | | | | |#|#| | | | | |#| | | | Williams82_______| | | | |#| | | |#| | | | | | | | | | | | | | | WilligesB84______| | | | |#| | | | | | | | | | | | | | | | | | | WilligesB86______| | | | |#| |#|#| | | | | | | | | | | | | | | | WilligesR86a_____| | | | |#| | | | | | | |#|#| | | | | | | | | | WilligesR86b_____| | | | | | | | | | | | |#| | |#| | | | | | | | Wong82___________| | | | |#| | | | | | | |#| | | | | | |#| | | | Woodson87________|#| | | |#| |#| | | | | | | | | | | | | | | | | Wright83_________| | | | | | | | | | | | |#| | |#| | | | | | | |