Grading Scheme

Grade components:
Students are expected to complete and submit all assigned coursework in good faith; those who fail to do so may be assigned a failing grade.

class participation 5 %
classroom exercises and journal10 %
homeworks 20 %
two quizzes (short exams) 10 %
two midterm exams 20 %
final exam 15 %
term project 20 %
Class participation:
Students are expected to contribute to learning by asking questions and making relevant comments in class and on the class newsgroup. Quality is more important than quantity. Disruptive activity contributes negatively (see policies).
Classroom exercises and journal:
Our work in the classroom will include a number of short group exercises, meant to solidify understanding of the concepts being discussed. One or more such exercises are likely to be part of most class meetings. Students must maintain a journal of their progress through the course and submit the journal near the end of the semester for grading. The journal consists of neatly organized classroom exercises and other material as announced in class. The exercises and journal will be graded primarily for effort, group work, and other contributions, and less so for simple correctness. Since attendance is not mandatory (see policies below), some low-scoring exercises will be dropped for each student. Please see me if you have concerns about the interaction of this component and the attendance policy.
Homeworks:
Homeworks include programming and non-programming ones, often mixed. No collaboration is permitted. You are encouraged to discuss the problems and solution strategies at a high level, but the final solution and details must be your individual work. If you are unclear on the boundary between permissible and non-permissible interactions in this regard, please ask me.
Exams and Quizzes:
All exams and quizzes are open book, open notes. You are free to bring with you any resources that you find useful. However, no communications are permitted other than between students and me. The use of computers during exams is strongly discouraged, but brief use is permitted provided it does not cause a disturbance. You may use the Internet, but only as a library to look up material you may find useful. As above, check with me if you are unclear on what is permitted. The exams are designed to require no equipment other than a pen and paper, along with the textbook and assigned readings.

Midterm exams will be held during regular class meetings, and will be roughly an hour long. Each quiz is a short exam, roughly half an hour long, held during part of a class meeting. The final exam follows the usual university schedule, and is thus held outside of regular class meetings.

Project:
In addition to the programming and other homeworks, the course features a semester-long group project. Students will work in groups of three or more to design and implement a substantial database application. Projects will be graded based on a written project report, the submitted source code, a demonstration, and a question-and-answer session following the demo. These materials will be due two weeks before finals week, but may be submitted earlier—there is no penalty for early submissions. Further details will follow.
COS 580:
There will be additional readings assigned to COS 580 students. The readings will be a mix of some classic papers of the database field and more recent publications. COS 580 students are expected to be comfortable reading such papers. There will also be additional and/or different questions on the exams and homeworks. Similarly, COS 580 students will be held to a higher standard during the question-and-answer session following the project demo.