
"User Interface design is hard work.
|
| Lecture: | MTRF 2:00-2:50, AK 233 |
| Prof: |
David C. Brown, FL 131, x5618,
dcb@cs.wpi.edu Office Hour: Wed 6 pm, or by appointment, in FL 131. Role: Help with HCI content; projects reqs; Qs about grading. |
| TAs: |
Bin Liu, FL 316,
binliu@cs.wpi.edu Office Hour: Thu 1:00, in room GL 05, CS Annex (Gordon Library). Asima Silva, FL A21, asima@cs.wpi.edu Office Hour: Fri 10:00, in room GL 05, CS Annex (Gordon Library). TAs Role: Help with projects; VISUAL BASIC (Bin); initial Qs about grading. |
| Mail sent to cs3041_ta@cs.wpi.edu will go to the professor, TAs and SA. | |
| SA: |
Tim Sutherland,
tims@wpi.edu Office Hour: Tue 3:00, in room GL 05, CS Annex (Gordon Library). SA Role: Help with VISUAL BASIC; Help with projects. |
| Course Web Page: | http://www.cs.wpi.edu/~dcb/courses/CS3041/ |
| Text: |
Designing the User Interface (3rd Edn.), Ben Shneiderman, Addison Wesley Longman, 1997. |
| Supplementary Text: |
Microsoft Visual Basic 6.0 Professional (Step by Step), Michael Halvorson, Microsoft Press, 1998. |
| Class Schedule: | Classes, dates, topics, subjects |
| Class Outline: | What gets covered by the class |

Basic Stuff:The intent of this course is to address the problem of how to improve the quality of interaction between an individual and a computer. Some of the material will come from the text, some from other books, much from experience (yours and mine), and the rest from research literature (Information sources). I expect the course to be fairly interactive, with lots of questions from me, and lots of answers from you; and vice versa too. Here are the introductory slides (.pdf) from the start of the course. The facts in this course are quite simple to grasp. The hard part is using them. This requires the right attitude, experience, and good taste. This requires learning and practice, which the course should provide. This course differs from many other CS courses, as in interface design there are often no right answers, and no best solution. The topics that will probably be covered in the course are given in an accompanying web page, The Story So Far.... We will try to follow the book quite closely, in order to make your reading of the book easier, and to make the book as useful as possible during the course. You will be expected to read the book (even if I
don't remind you), concentrating on the material covered in lectures.
We will try to cover about 2 chapters per week. In addition, you
will on occasion be given other material to read. This material will
reinforce the lectures and present additional topics.
ALL of this material will be examinable.
My expectation is that you will spend at least 15 hours per week on this course (i.e., at least 2 hours per day). This is WPI's standard expectation for the time spent on each 1/3 unit. With the exception of the group project all work should be done by yourself. A problem with the subject matter is that HCI is a rapidly changing field, with many small research results. However, there is only a limited amount of core knowledge that is applicable under all situations. It is also a field where "common sense" can play a large part. Much of what appears obvious, however, is being carefully tested to discover under which conditions (e.g., types of users) the assumptions are actually true, and why. Obviously, the intent of this course is to expose you to the concepts being addressed in this swiftly growing field. This is not primarily a programming course. Programming is merely one aspect. There will be one programming project, to be done in Visual Basic. Perhaps a more important additional aspect of this course is to try to make you "more sensitive" to the needs of the user -- i.e., most programs are not being used by their authors; many users of computers do not know much about computer science; naive users have different demands and expectations than experienced users. There will be at least one HCI-related video shown during the course. Everyone is expected to attend. One that may be shown includes some quite rare footage of "early" interface developments, such as the first mouse, and first bit-mapped display [Kay]. Another is a very good, general overview of the design of interfaces [Trower].
Exams and Projects:There will be two examinations, four projects and a possible presentation. Projects may include reading current research literature, evaluating experts' opinions & evaluating interfaces, an HCI experiment, a challenging interface design problem, and an interface design and implementation. Other handouts/pages will explain the projects. Project 3, and the associated presentations, will be done in TA-generated random groups. The other projects are to be done alone (see Academic Honesty section below). Exam 1 will cover all the material up to that date (book, handouts & lectures), while Exam 2 will concentrate on the material presented since the first exam but will not necessarily exclude other material. Note that the exams are based mostly on material from the book, but will also include material from the lectures -- some of which is not in the book -- so class attendance is strongly encouraged. Grading:The grading is assigned as follows:
Project 1 10% {1 week }
Project 2 20% {2 weeks}
Note: projects 3 & 4 overlap in time.
Project 3 20% {4 weeks} Note: group project.
Project 4 20% {3 weeks} Note: programming project.
Exam 1 15% {Closed book}
Exam 2 15% {Closed book}
Late Work:
Exam Policy:There will be two in-class exams. Good preparation for the final exam is the video by Tandy Trower. The format for each exam will be announced in class prior to the exam. The exams are closed-book.
If you are unable to be at an exam, you will receive an `incomplete' grade
for the course, and you will be able to take a make up exam during the next term.
Important Dates:
Standards:The highest standards of programming, writing, and presentation will be expected. In addition, use of appropriate sections of the Computer Science Department Documentation Standard will be enforced. We will expect you to deliver what is requested (e.g., answer all questions asked as part of the project description). The TAs will grade all the work according to a precise grading scheme that I will provide them. The presentations at the end of term will be made by selected groups
that worked together on Project 3 and will show the results from that
Project, plus some of the rationale for the decisions made. The
presentations and their content will be evaluated by everyone
in the class.
Academic Honesty:Cheating, defined as taking credit for work you did not do, is strictly forbidden. Offenders will receive a zero grade for the assignment or exam in question. In addition their case will be presented to the Computer Science Department Head (see the WPI Academic Honesty Policy). Course Grades:With respect to grading, an "A" is reserved for Excellent work, with a very rough expectation of a better than 90% score over the whole class. A grade of "B" represents high quality work, with a very rough expectation of a score at least higher than 60% and perhaps higher than 70%, depending on how hard the exams are and how hard the grading is. Above 50% but below the B boundary will probably be a "C" grade, which indicates reasonable but undistinguished work. Below 50% will probably get you an NR. Please note that these boundaries are meant merely as an indication of my expectations, and may change according to circumstances.
Possible Additional General Reading:WWW and HCI texts include:
|

http://www.cs.wpi.edu/~dcb/courses/CS3041/intro-B01.html