SWE 632 Course Syllabus

User Interface Design and Development
SWE 632 Course Syllabus
Fall 2007 (R B228, Monday @ 4:30)

 TA:                  Shuang Wang
 Office:             S&T II 335
 Email:               swangb[AT]gmu[DOT]edu             
Office Hours:    Wed 1:30pm - 3:30pm

TEXTS:

• Ben Shneiderman, Designing the User Interface, fourth edition, Addison Wesley. (required)
  Also look at U. Maryland's Guide to Usability for Software Engineers.
• Alan Cooper, About Face: 3.0 The Essentials of Interaction Design, IDG Books. (required)
• Lecture notes available on the class web page.
• And don't forget to look at User Friendly, the comic strip.

OBJECTIVE:

To explore the role of the human in the design and implementation of software. To prepare students to design and evaluate the quality of an interface between computer software and the human user. After completing this course, students should understand how to design software interfaces that are appropriate for the user, be familiar with a variety of interface design strategies, and be able to evaluate the quality of a software interface.

CONTENT:

This course will focus on the software interface between the computer and the human. Concepts in human factors will be covered, specifically in terms of designing software interfaces. We will cover theories of human-computer interaction, including human cognitive limitations, syntactic versus semantic knowledge, transitionality, and the "outside-in" design approach. We will also study guidelines for designing computer interfaces of various models, including command interfaces, menus, desktop views, and GUI interfaces.

READING:

We will read from both Shneiderman and Cooper. The schedule for the readings are given on the schedule web page.

EXAMS:

There will be a midterm and a final exam, both closed-book in class.

MAKEUPS:

Unless arrangements are worked out in advance, missed tests cannot be made up, and 10% per week will be deducted for late homework and project submissions. I understand that your job may occasionally take you out of town; so does mine. If you are going to be forced to miss class on the day something is due, let me know ahead of time by email or in writing.

EVALS:

Each student will evaluate six software interfaces from a human factors standpoint. During the semester, I will offer several software interfaces to evaluate; you will choose which ones to evaluate.

PROJECT

Each student will implement a small project to build a user interface system. More details on the project will be given the 2nd week of class.

HONOR CODE STATEMENT:

As with all GMU courses, SWE 632 is governed by the GMU Honor Code. In this course, all assignments, exams, and project submissions carry with them an implicit statement that it is the sole work of the author, unless joint work is explicitly authorized. Help may be obtained from the instructor or other students to understand the description of the problem and any technology, but the solution, particularly the design portion, must be the student's own work. If joint work is authorized, all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation, and as a minimum, will result in failure of the submission and as a maximum, failure of the class.

DISABILITIES:

If you are a student with a disability and you need academic accommodations, please see me and contact the Disability Resource Center (DRC) at 993-2474. All academic accommodations must be arranged through the DRC.

GRADING:

Grades will be (approximately): 20% the evaluations, 25% the project, 25% the midterm, and 30% the final.