Computer Science 181-F Grading - Fall 2012

Instructor: Mark Kampe

Computation of Course Grade

Category Item Weight
Exams daily quizzes 10%
midterm exam 20%
final exam 20%
Projects Proj 1: concept proposal 12.5%
Proj 2: Architecture 12.5%
Proj 3: Planning and Design 12.5%
Proj 4: Implementation and Testing 12.5%

While a weight is shown for each project, there will not be a "single grade" for each project. Each of the projects will involve a great many activities and deliverables, each of which will be individually graded (and many of which will each be the subject of an entire lecture).

For each graded submission most of the grade will be a group-score (based on the overall quality of the submission). A smaller portion of the grade will be personal, based on and divided (more or less equally) between the share and quality of each person's individual contributions to the overall effort.

Rationale

I have two goals in grading:

  1. to assess your mastery of the material.
  2. to encourage you go get as much as possible out of this class.

The greatest portion of the grade is evenly divided between exams (your mastery of concepts) and projects (your ability to apply skills and techniques). On the projects, I am weighting the overall result more than the individual components because:

  1. in the real world you will be judged, not on the basis of your individual efforts, but on the overall quality of your results.
  2. teams are not merely a technique for allowing individuals to do less work. A well functioning team can do work that none of the individuals would have been able to do.
  3. work division and cooperation are skills that are taught in this class. I expect to see the results of the applications of those skills.

I am using 10% of the grade as a coercive tool, to encourage you to get the maximum benefit out of the course: