Teaching Assistant:	Mike Neilsen
Email:	neil0056@d.umn.edu
Web Site:	http://www.d.umn.edu/~neil0056
Consulting Hours:	In HH 314: Monday 4-5 pm, Tuesday 3-4 pm

CAC (Computng Accreditation Commission) Course Description: http://www.d.umn.edu/cs/asse/desc/5551.pdf

Bulletin Description:
Design and layout of interactive programs using components, containers, events, menus, and dialogs. The use of graphics primitives, color and images; 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.

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. The practical will involve discussion of and programming in the Java language and its user interface components such as top-level containers, menus, dialogs, and pop-ups, and will include design and implemention of 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 Office of Disability Resources, 258 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.

Mental Health Statement:
As a student you may experience a range of issues that can cause barriers to learning, such as strained relationships, increased anxiety, alcohol/drug problems, feeling down, difficulty concentrating and/or lack of motivation. These mental health concerns or stressful events may lead to diminished academic performance or reduce a student's ability to participate in daily activities. University of Minnesota services are available to assist you with addressing these and other concerns you may be experiencing. You can learn more about the broad range of confidential mental health services available on campus via the UMD Health Service Counseling website at http://www.d.umn.edu/hlthserv/counseling/.

Student Academic Integrity Policy Academic dishonesty tarnishes UMD's reputation and discredits the accomplishments of students. UMD is committed to providing students every possible opportunity to grow in mind and spirit. This pledge can only be redeemed in an environment of trust, honesty, and fairness. As a result, academic dishonesty is regarded as a serious offense by all members of the academic community. In keeping with this ideal, this course will adhere to UMD's Student Academic Integrity Policy, which can be found at http://www.d.umn.edu/conduct/ This policy sanctions students engaging in academic dishonesty with penalties up to and including expulsion from the university for repeat offenders.

Student Conduct The instructor will enforce and students are expected to follow the University's Student Conduct Code ( http://www.d.umn.edu/conduct/ ). Appropriate classroom conduct promotes an environment of academic achievement and integrity. Disruptive classroom behavior that substantially or repeatedly interrupts either the instructor's ability to teach, or student learning, is prohibited. Disruptive behavior includes inappropriate use of technology in the classroom. Examples include ringing cell phones, text-messaging, watching videos, playing computer games, doing email, or surfing the Internet on your computer instead of note-taking or other instructor-sanctioned activities.

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, Fifth Edition, Addison Wesley (March 8, 2009), ISBN-10: 0-321-53735-1, ISBN-13: 978-0-321-53735-5

Course Requirements:
Although attendance is not required, 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.

Lab Assignments and Course Project:
There will be small, weekly lab assignments, each worth from 10 to 20 points, to be demonstrated and turned in during the lab session. Near the end of the course, there will be a more involved class project worth 30 to 40 points.

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 UMD Final Examination Policy web page explains the UMD policy about having more than two final exams on a single day, among other things.

Exam Schedule:

Scores and total points will be maintained by the TA. When appropriate, distributions of points will be posted on the "Distributions" page of the class web site:
http://www.d.umn.edu/~ddunham/cs5551f09/distribs

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

• Lab assignments, homework, and class project (approx. 200 points)
• Midterm Exam (100 points)
• Final Examination (200 points)

• The A- cutoff is 90%
• The B- cutoff is 80%
• The C- cutoff is 70%
• The D cutoff is 60%
• Below 60% is an F