Software Development -- CS 121

Grading Fall 2012

Game Project
The game project is driven by a number of detailed phases, sub-phases, and rubrics. Project grading is more qualitative based than quantitative based; and is thus more subjective than I would like. As far as course grade, the quizzes will provide quantitative values.
There are points assigned for each project subphase. Grades will be distributed based on four values (note, we will round up):

Plus
100% - Very close to perfect
Check
80% - Satisfactory: Some significant omissions, sometimes clarity is the missing ingrediant. Remember you should write for the appropriate audience: sometimes someone technical, sometimes teachers; sometimes middle school students; sometimes everyone.
Minus
30% - Many significant omissions. The team probably missed understanding the rubric or bailed.
Zero
0% - Team bailed.

Individual grades of each team member will be determined by the evaluation of the other team members. We will provide a survey about team performance after completion of each phase and as part of the Final. Team members will use these surveys to evaluate individual team member performance and contribution. We accept that Johnny may not contribute much in early phases, but then be the output leader in later phases. The team will decide the overall percentage for each team member.
Quizzes
The idea of quizzes is to keep you reading the course material along with the team project. Quizzes will come from the readings and the lectures. The will have the same grading approach (Plus, Check, Minus, Zero).
Class Participation
At various times, one team will evaluate the work product of another team. The efforts of each individual of the reviewing team will be evaluated, e.g., if you were suppose to review the UI of another team, you should have something of value to say.
Class participation also includes being part of any class discussions and being awake for questions.

Mike Erlinger

Last Modified Thursday, 30-Aug-2012 15:06:15 PDT