CPSC 546 - User Interface Development    Spring 2003

CPSC 546:      TT 4:00-5:15 Grote 205

Prerequisites: CPSC 420 and 450, or permission of instructor

Instructor:       Dr. Stephanie Smullen               Office: 209B Grote Hall

Email:  Stephanie-Smullen@utc.edu

Telephone: 425-4395 Office or 425-4349 Secretary

Office Hours: as posted or by appointment

Catalog Description: User interface design requirements; special user requirements; device types; dialog types and interaction types; empirical evaluation of user interfaces; the use of predictive modeling; interface design and implementation tools; examples.

Course Objectives: The student who completes this course will have mastered the issues, information sources, and methods used in the design, implementation, and evaluation of user interfaces, the parts of a software system that interact with people. The student will appreciate the great effort needed to develop a user interface, and the large potential costs of a bad interface, both human and financial. A practical approach will be used. The student will learn the importance of the user interface; the impact of good and bad interfaces; the diversity of users and applications; the design tradeoffs involving different dialog types and input/output devices. The student will understand the benefits and costs of developing tools for user interface development; how to evaluate system usability; the role of human factors engineering in interfaces; available design and evaluation tools. The student will have first-hand experience with various user interfaces and their evaluation, and will be required to design and build a part of a user interface for a software system.

Text:     Interaction Design, Preece, Rogers, Sharp, 2002, Wiley, 0-471-49278-7.

 

References:

The Design of Everyday Things, Norman, 1988, Doubleday, 0-385-26774-6.

Designing the User Interface: Strategies for Effective Human-Computer Interaction, 3rd 1997 Edition, Schneiderman, Addison-Wesley, ISBN 0-2016-94972

The Psychology of Human-Computer Interaction, Card, Moran and Newell, 1983, Erlbaum, 0-89859-859-1.

Reading in Human-Computer Interaction: Toward the Year 2000, 2nd 1995 Edition, Baecker (Editor), Academic Press, ISBN 1-5586-02461  

Grading Policy: Midterm (100 points), Final (100 points), Assignments and group projects (150 points), Two reports (50 points), Individual Project (50 points) and  Instructor Evaluation (50 points) based on attendance and participation in class and group projects.  Your grade will be determined by the percentage of points you earn out of the 500 possible points, as follows:  90-100% A, 80-89% B, 70-79% C, LESS THAN 70% F.

Reports: During the term you must describe and analyze two significant user interfaces. The reports must describe the interface in technical terms, analyze the design, and evaluate the success of the interface. They may be based on experience, professional journal articles, scholarly reports, and books. The second analysis report will be in written and oral form. You will share your interface with the class in a 5-10 minute informal demonstration and html presentation outlining the "high" and "low" points.  Important due dates for reports:

            Report 1 topic due – January 21

            Report 1 due – February 4

            Report 2 topic due – February 11

            Report 2 presentation – March 4 and 6

Project: During the term you must (1) select a process/program to design an interface for (submit your proposed project for approval by March 4) and complete (2) the design for a user interface (written design description – due March 20), (3) implement the user interface and enough of the application so that the user can effectively evaluate the interface (store the code and executable file), and (4) analyze its performance (written analysis report – due April 21).

Homework And Assignment Policy: All programs and assignments must be your own work, done individually. Each is due at the start of class on the stated date; late assignments will be accepted, but discounted in value, until the assignment is discussed in class. No credit will be given for any answers after the assignment is discussed in class. It is your responsibility to read the material in the textbook as it is covered, even if no specific reading assignments are made. Assignments must be stored in your directory on juno.utc.edu.  Note that all home directories have been copied from genesis to juno.   Go to https://secure.utc.edu/forgotpw to determine your new password on juno (use passwd to change it).  The account name is the same.   The assignments must be indexed by an html file stored in your directory and named portfolio546.htm

Online Resources: The course web site may be accessed through the course web site at http://utconline.utc.edu

Examination Policy: It is the responsibility of the student to take the examinations at the scheduled times, except in very unusual circumstances. Some unacceptable reasons for missing an examination include: No time to study for the examination; Another examination on the same day; Going on vacation that day; Oversleeping. If you must miss an examination you must inform the instructor in advance; if the instructor requests, you must present proof of the reasons for your absence.

ADA Statement: If you are a student with a disability (e.g. physical, psychiatric, vision, hearing, etc.) and think that you might need special assistance or a special accommodation(s) in this class or any other class, call the Office for Students with Disabilities/College Access Program at 425-4006 or come by the office at 110 Frist Hall.

If you find that personal problems, career indecision, study and time management difficulties, etc. are adversely impacting your successful progress at UTC, please contact the Counseling and Career Planning Center at 425-4438.