HFDSYLL99

HUMAN MACHINE INTERFACE SYSTEMS

Jean B. Gasen

BUS 659

Fall 1999

Wed Evenings 7 pm – 9:40 pm

CONTACT INFORMATION

Office: Business Building Room 4163

Box 844000 (mailing address), Richmond 23284-4000

Phone: 934-7920 / 828-7128

Office hours: Wed 6 – 7 pm, and by appointment

e-mail: jean.gasen@capitalone.com, jbgasen@vcu.edu

COURSE OVERVIEW:

This course is designed to provide an in-depth analysis of factors that are important in designing information systems for users. Topics to be covered include: definition and rationale for human factors design, conceptual and theoretical issues in the approach to HFD, analysis and evaluation of different system design components with respect to HFD, and the application of HFD to real-world business information systems. The class will be held in a graduate seminar format. Students will be expected to lead and participate in discussions on weekly topics.

COURSE PHILOSOPHY AND OBJECTIVES:

Despite all the recent advances in technology, the design of usable systems is often left out of the system development life cycle. Many user interfaces are not evaluated for their usability or acceptability. This often results in critical design failure or interfaces which contribute to stress, fatigue, and increased human error. In sum, user interfaces are central to the success of software products, and developers must know how to ensure that people can actually use their software.

Students completing BUS 659 should have gained the following:

1) Perspective on the field of human-computer interaction (HCI) including an appreciation for the:

z variety of theoretical and methodological approaches to the study of HCI

z importance of the user interface, and the costs and benefits of incorporating an HCI perspective in the system development life cycle impact of social, economic, political and cultural factors on the design user interfaces;

z impact of good and bad user interfaces on the people and organizations in which they are implemented;

z diversity of users and HCI applications

2) Knowledge of methods and tools for integrating an HCI perspective into the system development life cycle in:

z system analysis - including task analysis and various information gathering methodologies;

z systems design and development - including I/O selection and design graphic design; ergonomic design; dialogue, screen and error design; and tools (rapid prototyping, UIMS etc.) to assist in the process;

z system implementation and evaluation - including methods for implementing and testing usability of products; measurement and empirical evaluation techniques; theoretical and predictive modeling techniques, product survey methods etc.

3) Knowledge of references and resources for further independent study in the field including:

z Outstanding books, journals, proceedings, design guidelines and other print resources in the field;

z Leading R & D labs and researchers in the field;

z Software tools and products which support user interface design;

TEXTS:

Shneiderman, B. (1999) Designing the User Interface (3^rd edition)

Reading, MA: Addison-Wesley.

Norman, D. (1990) The design of Everyday Things. New York: Doubleday.

Occasional Readings - as assigned during the semester

EVALUATION & GRADING:

The course will consist of 3 different types of activities: Short class assignments and projects which emphasize current topics in the course , a final project, and a one exam. The specific expectations for each type of activity will be provided during the semester. The weighting of these activities will be:

Class Assignments 40%

Exam (Take Home) 30%

Final Project 30%

BUSINESS 659 COURSE OUTLINE

Date	Topics	Readings	Assignments
9/1	Introduction/Rationale	Chap 1 – Shneiderman (S)	Assignment 1 Given
9/8	Theories, Principles, Guidelines	Ch 2 - S
9/15	User Centered Design Principles	Norman’s book	Assignment 1 - Due Assignment 2 - Given
9/22	Managing the Design Process	Ch 3 - S
9/29	Review and Testing	Ch 4 - S	Assignment 2 Due
10/6	Software Tools & Virtual Environments	Ch 5, 6 - S	Project Proposals Due
10/13	Interaction Styles: Menus, Commands and Natural Language	Ch 7,8 - S	Take Home Exam Given
10/20	Interaction Devices, Response Time and Display Rate	Ch 9,10	Take Home Exam Due Assignment 3 Given
10/27	Presentation Styles, Manuals, Help and Tutorials, Multiple Window Strategies	Ch 11,12,13 - S
11/3	Computer Supported Cooperative Work	Ch 14 - S	Assignment 3 - Due
11/10	Information Search and Visualization	Ch 15 - S	Interim Project Reports / Consultation
11/17	Class Canceled – Meet at Cap One for Interfaces 99		Assignment 4 – Trip Report Summary (or alternate assignment)
11/24	Thanksgiving Recess
12/1	Hypermedia and the Web, Societal and Individual Impacts	Ch 16, Afterward - S	Assignment 4 Due
12/8	Project Presentations
12/15	Project Presentations		Projects Reports Due

FINAL PROJECT DESCRIPTION

OBJECTIVE: The final project is designed to integrate your knowledge of material learned in the course by applying it to a specific human computer interface application. There are four requirements to complete the final project.

REQUIREMENTS:

1) Proposal: A short proposal (2-3 pp.) describing the objectives, activities, required resources, and anticipated outcomes.

2) Interim Report /Consultation: A brief interim report and at least one meeting with me during the semester to discuss progress and get any needed assistance/feedback.

3) Final Project Report: A final report that should include the following sections: Objectives/Goals and Rationale, Methods/Activities Outcomes/Products, Summary/Recommendations

4) Class Presentation of Project: This will be completed during the last two weeks of class. The summary may include a demonstration of software, if applicable. Plan on at least 15 minutes. If you would like more time, please let me know and I will adjust the schedule accordingly. (The time limit will depend on the nature of the presentations and the number of presentations.)

GENERAL GUIDELINES:

The focus of the project should be based on your specific interests within the course. However, I would like the following additional guidelines to be followed:

1) The project should involve some hands-on or direct interaction with the computer (not merely reading). Real people must be used to test out your ideas.

2) The project definition should be based upon the application of information presented in readings or class discussion.
3) The project should also include readings/materials outside of required reading, e.g. some review of the literature.

4) The project may be completed individually or in a small group (3 maximum).Obviously, the scope will be larger if done in a group. Include a description of how you see the project activities shared among the group to strengthen your proposal.

POSSIBLE PROJECT APPROACHES: (Not an exhaustive list)

1) Design a pilot study to test some aspect of an interface design. Use existing research to guide your design (e.g. study errors which users make, compare cognitive strategies for interaction patterns, assess impact of computer mediated communication on content and pattern of communication etc.)

2) Complete a comparative evaluation of several application packages within one area of interest (e.g. spreadsheets, word processing, etc.). Use existing knowledge/research on interface design/characteristics and focus on one or more design interface features. Develop or include a taxonomy of evaluation criteria, including the rationale for the development of such criteria based upon research literature.

3) Develop/modify existing software to improve its interaction quality. Use models, principles etc. discussed in class & readings to guide your efforts. Test out and evaluate these features with a sample of users.

4) Develop/evaluate a teaching/learning aid (e.g. documentation or a demonstration software program) to enhance the initial learning of existing software. Incorporate discussion of documentation design, naive user characteristics, etc. into the development of the aid.

5) Based upon knowledge and direct interaction of existing software, design a new piece of software (application or operating system). Include descriptions of system model, menu/screen design layouts, logic and rationale for all aspects of design: choice of interaction style, logic of syntax naming conventions, choice of specific input requirements, types of feedback provided to users etc.