|
Department of Mathematical Sciences C SC 481.06 Winter 2004 Syllabus |
|
| Class | lecture: MWF 10:00 - 10:50 a.m. in Towers 115 |
| Instructor | Pete Sanderson |
| Office | Towers 131 |
| Office Hours | MW 5:00-6:00 p.m., TR 1:30-3:00 p.m. or by appointment |
| PSanderson@Otterbein.edu | |
| Phone | 823-1317 |
| Home Phone | 784-8930 (no later than 9 p.m., please) |
| Objectives | By the end of this course you will be familiar with major principles, guidelines and issues of human computer interaction and user interface design. You will be able to design graphical user interfaces for the desktop and/or web that are consistent with these principles and guidelines. You will gain experience with a user-centered software design process by designing a GUI-based system on paper. You will gain experience programming GUI-driven desktop applications in C# and Java. | ||||||||||||||||||||||||||||||
| Description | Because this is a special topics course, there is no course description other than the two sentence generic description in the catalog. We will be guided by the course objectives and schedule. | ||||||||||||||||||||||||||||||
| Prerequisites | C SC 205. This prerequisite is specific to the topic of User Interface Design. It was determined by me and approved by Dr. Buck and Mr. Stucki. | ||||||||||||||||||||||||||||||
| Texts | Designing from Both Sides of the Screen, Isaacs and Walendowski, New Riders Publishing, 2002.
Other readings will be provided as needed. Additional resources are available on the course web site http://faculty.otterbein.edu/PSanderson/CSC481/ |
||||||||||||||||||||||||||||||
| Labs | This course has no formal laboratory component. You will work on several design and programming projects. Some will be pair or team projects, and lecture time will be devoted to these as needed. | ||||||||||||||||||||||||||||||
| Homework | In addition to the course projects, I will assign individual homework exercises throughout the quarter. These will for the most part be written summaries of assigned readings. | ||||||||||||||||||||||||||||||
| Exams | There will be no exams. | ||||||||||||||||||||||||||||||
| Academic
Integrity Policy |
All members of the Otterbein College community of learners are expected
to follow the rules and customs of proper academic conduct. Proper conduct
includes avoiding academic
misconduct as defined in the Campus
Life Handbook. You are encouraged to help each other learn the
course material. This course involves both individual and team assignments.
Feel free to discuss individual homework and projects with one another. Participants in these discussions enjoy the benefit of deeper and greater learning. However, all work submitted for evaluation that is based on discussions with others must be your own work, created yourself while thinking it through. Any work submitted for evaluation that includes work done by another, copying of another's work, or the result of following another's step-by-step keystrokes and mouse clicks, is a case of academic misconduct. For team assignments, you are of course expected to work collaboratively. However each team assignment includes a listing of individual credits. Claiming individual credit for work done by one or more teammates constitutes academic misconduct. When academic misconduct is found in any assignment you submit, you will receive a zero grade for that assignment. The misconduct may also be reported to the Office of the Academic Dean. If a previous academic misconduct offense is on your record, you will receive a grade of F for this course and a referral to the judicial system. |
||||||||||||||||||||||||||||||
| Grading | Your grade is based on a final course score in the range 0 to 100.
The components of this score and their weights are as follows: Design projects
30%, Programming projects 30%, Readings summaries and discussion participation
20%, Final presentation 20%.
|