CSIS 672 – Human Computer Interaction

Course Syllabus

Spring 2002



Dr. Bill Manaris


Room: 210 J.C. Long Building
Phone: (95)3-8159

E-mail: manaris@cs.cofc.edu

Office Hours:

Monday 1:30-4:30pm, Wednesday 1:30-3:30pm, and by appointment.  Feel free to come in with questions and problems you may have.  I may also be available for a few minutes after class.


Introduction to human computer interaction and user interface development. Topics include definitions of Human-Computer Interaction, importance of good interfaces, psychological foundations, user-interface design examples, interaction models and dialog types for interfaces, user interface life-cycle, user-centered design and task-analysis, prototyping and the iterative design cycle, prototyping tools and environments, user interface implementation, and interface quality and methods of evaluation.


This course stresses the importance of good interfaces and the relationship of user interface design to human-computer interaction. It is intended to provide an adequate basis in software design and implementation for user interfaces. There will be content on both the issues and engineering process for user interface development.

Each student must have completed CSCI 330 (230) or an equivalent or higher course, or have permission of the instructor.  Minimally, each student should have strong background in software development (at least two years) in terms of software engineering principles, data structures, and algorithms; also strong background in C/C++, Java, or Visual Basic.



Preece, J. et al. (1994), Human-Computer Interaction, Addison-Wesley, ISBN: 0201627698.



Additional materials will be made available via handouts and the class webpage  at www.cs.cofc.edu/~manaris/spring02/cs672.html .



·                To understand how HCI relates to other aspects of software engineering.

·                To understand basic human and machine factors that influence the development of interactive computing systems.

·                To gain basic skills and knowledge for user interface design.

·                To acquire skills in integrating HCI into the system development life-cycle (analysis, design, implementation, evaluation).

·                To develop an appreciation for user-centered design.

·                To learn at least one development methodology and one toolkit for prototyping/implementing user interfaces.

·                To gain awareness of other tools and methods available.

·                To develop at least one user interface.

·                To gain additional experience with team work and collaborative development efforts.



Scale: A: 90-100; B: 80-89; C: 70-79; D: 60-69, F: <60. The grades of B+ and C+ may be given at the professor's discretion.

Final Grade Computation: Assignments (4-8) 25%, Tests (2) 40%, Comprehensive Final Exam 25%, and Class Participation 10%.


Course Policies:

·       Attendance at tests is mandatory.  You are expected to attend all classes.  Regardless of actual attendance, you are responsible for announcements made in class, assignment due dates, etc.

·       You are expected to do all reading assignments promptly.

·       Students are expected to participate in the educational experience through questions and invited comments/discussion.  However, you should respect your classmates right to learn (e.g., raise your hand, keep comments and discussions contained to the subject at hand, etc.).

·       Programming assignments are to be submitted to the instructor by the due date and time.  If the instructor is unavailable, they may be turned in at the CSCI department office (Long 216).

·                You must do your assignments alone (or with your teammates, for group assignments) but you may discuss assignments and possible solutions with classmates.   If you discuss the assignment with others, you must report this accurately.  Not doing so is an honor offense.  Specific details will be announced when the first assignment is given.

·                To receive a passing grade for the course, you must average a passing grade (70% or higher) on each of the following: assignments, tests, and final exam.

·       24-hour blackout period: You may ask questions about an assignment up until 24-hours before it is due.

·       Upon return of graded work, you have one week to ask questions regarding your grade.

·       To receive a passing grade for the course, you must average a passing grade (70% or higher) on each of the following: assignments, tests, and final exam.

·       You have four “late” days for the whole semester to use when submitting your assignments.  Once you use up these days, no late assignments will be accepted. However, partial solutions submitted on time will be graded.

·       If at the end of the semester you still have all 4 “late” days unused and have completed all assignments, 2.5 bonus points will be added to your final course grade.