Course Syllabus,
CS 5551 User Interface Design
Fall Semester 2006

Course Data:
Instructor: Doug Dunham
Email: ddunham@d.umn.edu
Web Site: http://www.d.umn.edu/~ddunham
Office:311 Heller Hall
Phone:726-7510
Office Hours: M, W 3-4, Tu 2-4, F 1-1:50, and by appointment
Lectures: M, W, F 2-2:50 p.m. in HH 306
Lab: M 6-6:50 p.m. in MWAH 177
Course Web Site: http://www.d.umn.edu/~ddunham/cs5551f06

Teaching Assistant: Shruti Pandey
Email: pande019@d.umn.edu
Web Site: http://www.d.umn.edu/~pande019
Consulting Hours: In HH 314: Monday 10-11 am, 5-6 pm, Tuesday 7-8 pm

Course Outcomes: A detailed list of course outcomes is at: http://www.d.umn.edu/cs/asse/outc/CS5551.pdf

Bulletin Description:
Design and layout of interactive programs using menus, dialogs, and the event loop. The use of color, text, fonts, and bitmaps; giving user feedback and help. Rapid prototyping and interface management systems. Design for accessibility and usability.

Prerequisites:
CS 2511, Math 1297, or the equivalent if you are a transfer student.
We will be using the Java programming language for this course.

Important note: The computer science bachelor's degree program at UMD is accredited by CAC (the Computing Accreditation Commission). One of the CAC requirements is that all students must satisfy the prerequisites in order to be admitted to a course, so if you have not passed the prerequisite courses, you must drop this course (if you have any questions about this, please see the instructor after the lecture or during office hours).

Course Objectives and Content:
This course provides an introduction to the theory and practice of designing a user interface to an application program. The following is a rough outline of the material that I hope to cover in the course. From the theoretical point of view, we will cover general principles, theories, and guidelines for interface development, software tools, direct manipulation and virtual environments, multiple-window strategies, and information search and visualization. On the practical side, we will discuss the Java language and its user interface components, and we will design and implement applications with user interfaces that use those components.

Equal Opportunity:
The University of Minnesota is committed to the policy that all persons shall have equal access to its programs, facilities, and employment without regard to race, color, creed, religion, national origin, sex, age, marital status, disability, public assistance status, veteran status, or sexual orientation. As instructor, I am committed to upholding University of Minnesota's equal opportunity policy. I encourage you to talk to me in private about any concerns you have related to equal opportunity in the classroom. To inquire further about the University's policy on equal opportunity, contact the Office of Equal Opportunity, 269-273 DAdB, (http://www.d.umn.edu/equaloo), phone: (218) 726-6827 or (218) 726-6849, email: equaloo@d.umn.edu.

Students with Disabilities:
If you have any disability (either permanent or temporary) that might affect your ability to perform in this class, please inform me at the start of the quarter. I may adapt methods, materials, or testing so that you can participate equitably. To learn about the services that UMD provides to students with disabilities, contact the Disability Services and Resources Office, 236 Kirby Student Center, (http://www.d.umn.edu/access), phone: (218) 726-8217 or TTY (218) 726-7380, email: access@d.umn.edu or contact the Office of Equal Opportunity, 269-273 DAdB, (http://www.d.umn.edu/equaloo), phone: (218) 726-6827, email: equaloo@d.umn.edu.

Required Texts:

  1. Kathy Walrath, Mary Campione, Alison Huml, Sharon Zakhour, The JFC Swing Tutorial: A Guide to Constructing GUIs, Second Edition Addison-Wesley Professional; (February 27, 2004) ISBN 0-201-91467-0.
  2. Ben Shneiderman, Catherine Plaisant, Designing the User Interface, Fourth Edition, Addison Wesley (March 31, 2004), ISBN 0-321-19786-0.

Recommended Text:

  1. David Geary, Graphic Java 2, Volume 2: Swing (3rd Edition) , Prentice Hall PTR; (March 12, 1999), ISBN 0-13-079667-0.

Course Requirements:
You are responsible for reading assigned text material and for material covered in class, including:

  1. doing the reading assignments from the text
  2. the material covered in the lectures
  3. obtaining assignments and handouts
  4. turning in programming assignments and homework

If you are unable to attend a class meeting, it is your responsibility to obtain class notes, assignments, and extra copies of handouts from your study partner. Note: all assignments are due at the beginning of class on the due date (unless otherwise specified) -- they will be docked 25% per day if turned in late.

Examinations and Grading:

There will be a midterm exam, worth 100 points and a final exam worth 200 points. These exams are closed book. The final exam will be comprehensive. Exams will not be given early, and makeups must be justified by dire circumstances described to the instructor before the time of the exam. It is Department of Computer Science policy not to return final exams, however they are kept and you can look at your exam in the instructor's office. The section Final Examination Conflicts on the Final Examination Policy web page explains the UMD policy about having more than two final exams on a single day.

Exam Schedule:

ExamPointsDate and Time
Midterm Exam 100 points Wednesday, October 25, 2-2:50 p.m. in HH 306
Final Exam 200 points Monday, December 18, 2-3:55 p.m. in HH 306

Scores and total points will be posted periodically on the "Grades" page of the class web site:
http://www.d.umn.edu/~ddunham/cs5551f06/grades
using the last digits of your student id number. If you wish to have your scores posted using a number other than the last digits of your student id, you may email your request to the instructor.

Grading Procedures: Final grades are based on total points distributed approximately as follows:

Grades are assigned based on a percentage of the total points. These percentages may be lowered slightly but they will not be raised.
Important note: In the past, students have tended to do better on the lab and homework assignments (average > 90%) than on the midterm (80%) and final (78%) exams. Thus class averages going into the final exam tend to be higher than after the final exam. This leads to the following two pieces of advice: (1) keep your average as high as possible by doing well on the lab/homework assignments, and (2) study carefully for the exams, using the review sheets, so that your average isn't brought down by poor exam scores.
The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.
Page URL: http://www.d.umn.edu /~ddunham/cs5551f06/syllabus.html
Page Author: Doug Dunham
Last Modified: Tuesday, 26-Sep-2006 17:26:57 CDT
Comments to: ddunham@d.umn.edu