| Instructor: | Chris Prince (http://www.d.umn.edu/~cprince) |
| Email: | cprince@d.umn.edu |
| Office: | 313 Heller Hall |
| Phone: | 726-6514 |
| Office Hours: | 13:30-14:30 MF, 13:00-14:00 Tue, 16:00-17:00 W, and by appointment
(Prince)
13:30-14:30 W, 14:00-15:00 Tue, and by appointment (Maclin) |
| Text: | Forouzan and Gilberg, Computer Science: A Structured Programming Approach Using C (Second Edition), PWS Publishing |
| Item | Points | Date and Time |
|---|---|---|
| Midterm Exam 1 | 100 points | October 9 (Monday), in class |
| Midterm Exam 2 | 100 points | November 20 (Monday), in class |
| Final Exam (both lectures) | 200 points | December 16 (Saturday), 10:00-11:55 |
| In-Lab Assignments (14) | 60 points | weekly |
| Programming Assignments (8) | 260 points | TBA |
| Homework Assignments (10) | 80 points | TBA |
| Total | 800 points | Grade based on total points |
In assigning grades I will use the cutoffs shown below. Note that these cutoffs may go lower if I feel that exams or programming assignments were particularly difficult but they will not go higher (if everyone gets over 90% of the total points then everyone gets at least an A-). Further note that no matter how low the cutoffs move, the cutoff for a D will likely never go as low as 50%.
Cutoffs:
On Thursdays (noon lecture) or Tuesdays (3pm lecture) you will meet with your recitation group in HH 306. In these sessions, you will discuss the material presented in lecture, go over exams, hand out and discuss programming assignments, and work problems from the text. Your lab supervisor and recitation instructor will be a Computer Science Department graduate student. Dates of all important lab and recitation events are also given on the term schedule.
On Tuesdays (noon lecture) or Thursdays (3pm lecture) you will meet in lab (MWAH 177). During the lab sessions you will have an opportunity to apply what you learn from the lectures and reading by designing, writing, and testing programs under the supervision of your recitation instructor. Each lab day will have a short lab assignment you must complete as part of your lab. You will also have time to work on your programming assignments. For all but the simplest programming assignments, the one hour of supervised lab will not be enough to complete them. You will also need to work on them outside of your scheduled lab hour.
Cheating: Programming assignments and homework must be your own work. You may discuss general ideas with other students, but should not discuss actual code with others. If you are having problems with an assignment, please come and see me or send me email.
Late Assignments: Homework assignments are due at the start of class on the due date. Since you will generally review some of the problems from the homework during class, homework assignments can not be handed in late. All programming assignments will be collected by 4:00 on the due date. You may hand in the assignment during class or you may them in to the Computer Science TA on duty in HH 314. Please make sure to include your TA's name, the class (CS 1511) and section (e.g., Recitation 3) on the assignment so that it is placed in the right box.
For the semester you will be allowed a total of three late days for programming assignments. This means that you may hand in one programming assignment three days late or one assignment two days late and one one day late or three assignments one day late. An assignment is late if it is handed in past 4:00 on the due date. One late day will then be charged if the assignment is handed in by 4:00 on the next school day, two late days will be charged if the assignment is handed in by 4:00 on the second school day after the assignment is due, etc. Note that once you use up your three late days you must turn in all assignments on the due date.