IRLS575 Outline.
Last altered 6/11/06 Summer outline, under review (I will bring it completly up to date within d2l.)
|
|
The course is conceived of as discussions on 15 (or so) topics. A lecture course in the University of Arizona amounts to 37 1/2 hours of instruction spread through a semester. Our 'discussions' will be the virtual counterpart of 30 (or so) one and a quarter hour lectures, delivered at a rate of two a week. There will be notes, readings, discussion groups, and (of course) assignment. |
General |
We do not really use a set text. But were we to do so, we might have chosen one or more of
You may also read
And you perhaps should read
Also very good are any of the writings of Donald Norman, for example
The first four of these are available on a single Voyager-CD (which is certainly available for the Macintosh platform, I am unsure of its status for other operating systems).
Another useful book is Shneiderman, Ben. [1997], Designing the User Interface: Strategies for Effective Human-Computer Interaction, Reading, Mass. : Addison-Wesley Pub. Co. (ISBN: ?). The text contains extensive bibliographies and lists of information resources. There is a useful Website devoted to this. Designing the User Interface And we will make extensive use of electronic sources (which will be recommended piecemeal, when needed). A start (and a finish) is The HCI Bibliography: Human-Computer Interaction Publications and Resources Also good for consulting is Helander, Martin ed. (1988), Handbook of Human-Computer Interaction ACM Curricula for Human-Computer Interaction And you should not miss Bad Human Factors Designs (but not updated for a while) Apparently many of the readings are available from EBSCO Host. Other good sources include Alan Cooper on Interaction Design (see the Website http://www.cooper.com/content/insights/cooper_books.asp) E reserves are at http://eres.library.arizona.edu and use the password 'xxx'. |
The Topics |
|
1: What is HCI? |
Designing computer systems to support people safely and productively (some see this as making more money). Nowadays everyone is a User, not just experts. Should be designed to meet the needs and capabilities of those for whom they are intended. HCI design, evaluation, and implementation of interactive computer systems and study of major phenomena surrounding their use. New challenges-- keeping up with the technology, putting it to good use What is it that makes easy to use systems easy to use? Why is a car so good and a video recorder so bad? |
Readings |
Clark, Andy [2003] Natural Born Cyborgs: Introduction (E-Reserves) Have a look at The HCI Bibliography: Human-Computer Interaction Publications and Resources and follow through the Definition and Field of HCI
|
2: Cognitive Psychology and HCI |
Cognition involves perception, memory, attention, learning and reasoning. HCI needs to take account of the views and theories covering these cognitive processes in order to exploit our cognitive strengths and avoid our weaknesses. |
Readings |
I occasionally use Robert A. Wilson and Frank C. Keil (eds.) [1999], MIT Encyclopaedia of the Cognitive Sciences but there is no need for you to unless you are following something up.
|
3: Social and Organizational Psychology and HCI |
For a large part, computers are used in a social setting, for example the workplace, so designers would be wise to pay some attention to social context. Also for computers that are used within organizations there are organizational issues such as the impact of automation on work practices. Finally, groupware-- which allow a number of people cooperate to a common end using computers-- is an important and developing area. |
Readings |
Have a look around Donald Normans site, including his essays, a very light (perhaps worthless) review of Andy Clark and Emotion and design: attractive things work better
|
4: Input and Output Devices, and Interaction Styles |
The User and the computer need to communicate with each other. Quite what devices are best for this depends on a) the user (eg elderly hampered by arthritis, children cannot do fine manipulations, Users with disabilities), b) the task (eg drawing, which is continuous, is different from typing or selecting from a menu, which is discrete), and c) the environment (eg speech no good where it is noisy). Many possibilities for input: keyboards, mice, trackballs, joysticks, cursor keys, touchscreens, 3-d trackers. datagloves, pens, speech, tablets... Many possibilities for output: screens, GUI, laptop palmtop, hypermedia (animations, sound). Virtual reality, 3 dimensional, speech and sound output, touch (eg braille). experimental, sound. Some time ago the interactions between a user and a computer were like a conversational dialog: input text was typed in then output text was displayed then input text typed in etc. (in turns). Now, with GUI computers and the like, the interactions are much richer (and they don't have the my-turn-your-turn sequencing). |
Readings |
|
5: Direct Manipulation Interfaces |
Users usually have knowledge of the target task domain-- be it desktop publishing, wordprocessing, or financial planning-- and perhaps some knowledge of computers and computer tasks. Direct manipulation interfaces aim to make the computer invisible to the User so that no knowledge of computer concepts or tasks is required and thus that the User's knowledge of the target domain is available of full without any obfuscating intermediaries. |
Readings |
Hodgson, J. (1995). Direct Manipulation. [http://www.sju.edu/~jhodgson/gui/manip.html].
|
6: Help Systems and Training |
Users need to be able to learn how to use the system, there should be help available, and the system should be designed to accommodate error (assuming that the User is going to make lots of them). |
Readings |
|
8: Group Work and Virtual Environments |
|
Readings |
|
9: Software Engineering |
The problem of software engineering is to obtain high quality software within known resource constraints (time, money, equipment, effort). Ideas of what 'high quality' amounts to have changed. Some time ago it meant meeting the specification, and a specification was largely a statement of engineering requirements. A well-known technique here was the 'waterfall model' in which if the Users featured at all, they came in once only and early in the piece before the User requirements were really known. Nowadays most specifications would included the need to be User friendly. And this has led to User-centred design in which Users feature early and often in the design process. |
Readings |
|
10: User-centred Design |
Involve the Users early and often, and iterate. Some suggestions have been made as to how to involve the Users a) Soft Systems Methodology, b) cooperative design, c) multiview, d) an HCI design approach, and e) life cycle models for Website design. |
Readings |
|
11: Task Analysis and Task Centered User Interface Design |
|
Readings |
|
12: More on design, including prototyping |
|
Readings |
|
13: Individuals and their Differences |
|
Readings |
|
14: Evaluation |
Evaluation or testing is vital during the design and for ensuring that the end product performs as it should. There are many and varied techniques for testing. |
Readings |
|
15: Graph theory, Network theory, and the Web |
Graphs. Random networks. Degrees of separation. Small worlds. Hubs and connectors. Scale-free networks. The four continents of the Web. |
Readings |
|
16: Hypertext and Hypermedia |
Explanation of hypertext. History.Why do hypertext? Basic Elements of Hypertext .The Architecture of Hypertext Systems. Current Systems. Internet Systems With Hypertext or Hypermedia. Applications of Hypertext. Navigating Large Information Spaces. Multimedia. Usability and Intelligent Hypertext |
Readings |
|
17: Web Technologies and Their Interfaces 1: Introduction |
Plain vanilla Web service. Server, Client. HTML the language of the Web. Pages and page editors. File types. Absolute and Relative addresses. Browsers. |
Readings |
|
18: Web Technologies and Their Interfaces 2: Standard Practice |
Stylesheets. CSS. Server includes SSI. CGI |
Readings |
|
19: Web Technologies and Their Interfaces: 3 Standard Practice: Client Includes |
Client includes. Dynamic HTML. Java and Javascript |
Readings |
|
20: Web Technologies and Their Interfaces: 4 Standard Practice: XML |
XML |
|
|
|
21:Web Technologies and Their Interfaces: 5 Additional Techniques and Review |
Website and Database integration .Net, PhP, SQL, mySQL |
Readings |
|
22: Web Design: Introduction |
Philosophy. Interface Design. Site Design. Page Design. Web Graphics. Web Multimedia and Animation. The law. |
Readings |
Jakob Nielesn [2000], Designing Web Usability, New Riders Publishing (Page Design: Chapter 2) (E-Reserves)
|
23:Data Mining |
Data-Mining: Can user behaviors be used to predict user behaviors? |
|
|
|
24. Information Architecture |
What is Information Architecture? |
Readings |
|