HCI
From GSLISWiki
Human Computer Interaction concerns itself with examining how people interact with computers, in order to design systems around the users needs and capabilities, rather than for an abstract conception of the user. In this manner it is similar to the study of Use and Users of Information by people who approach problems of information storage, retrieval, presentation, and use from a Library Science perspective. It is a sub-field of Computer Science that overlaps with what a number of people in Library and Information Science do. Both Mike Twidale and Cameron Jones do HCI research in our department.
Contents |
[edit] Use Cases: an example of an HCI Technique
The purpose of Use Cases along with other HCI techniques is to provide programmers with tools which will help them design better programs by focusing on user needs. The problem is that when programmers do not use such tools, they tend to build programs (web pages, whatever) that are designed for themselves, rather than for a particular user. This is especially a problem when the users are non-techies, and when they have domain specific knowledge which programmers do not share.
The advantage of Use Cases is that they provide a formal framework which encourages programmers to start thinking about user needs before they start programming--before they have invested any effort in code which may be wasted or made irrelevant (before they have a vested interest in a particular design). The problem with Use Cases, as with any logical/rational/formal systems approach, is that it is not grounded in empirical evidence, and therefore may not be grounded in reality. It is simply an elaboration of what the programmer *thinks* the user will want to do or need to do, not what they actually *do* do and want to do.
A number of HCI approaches attempt to close this gap, the most thorough one being Participatory Design, where the users and all stakeholders in the project are involved in the design process, so that all knowledge, tacit and explicit, is captured. While this is an extremely effective method, it is also extremely expensive, and as a result, not used very often. Various forms of Scenario Based Design attempt to develop low-cost bridges of this gap.
It is important to keep in mind that simply asking people what they do, what they need, or what they want, is often remarkably unsuccessful. Reasons for this include: (1) they fail to mention the tacit knowledge that is absolutely vital to be incorporated in the program, (2) they fail to mention domain specific knowledge that is obvious to them but not to an outsider, (3) often they do not know what they want until they try out the program, and (4) the introduction of the program into the environment changes the nature of the environment, and changes the needs of the users. The iLabs project is an experimental attempt at addressing these concerns by creating a program that is constantly evolving with user needs and wants. If you are curious about this project, talk to Cameron Jones or Ingbert Floyd.
[edit] Related Links
- The HCI Bibliography:
[edit] Sub-disciplines withing HCI:
- (though not exclusive to the HCI category)
