Assessment (Tentative!)
Here is my suggestion for how we assess your progress in the course. I traditionally wait for comments from you before finalizing this.
- Iterations (30%, graded by clients)
- Presentations (20%, graded by instructor)
- Product (20%, graded by clients and instructor)
- Exams (10%, graded by instructor)
- Participation (10%, graded by instructor)
- Peer Review (10%, graded by students)
Sorry for making this so complicated, but there simply are a lot of different components to address. If you compare this rubric to Spring 2006, you'll see that I made quite a few changes. The highlights are that I introduced an exam component and got rid of the formal reports (which are rolled into the product now where we expect some sensible documentation).
Important Notes
Stuff is due when indicated on the Schedule, late submissions are not accepted. Not ever! You don't want to submit code that doesn't compile, you don't want to submit writing that's full of spelling errors, etc. Just be professional!
Exams are cumulative, closed-book, closed-notes, open-mind and cover material from lectures and readings. Participation covers all kinds of stuff including (but not limited to) attending lectures, doing in-class exercises, taking part in discussions, helping others (without cheating of course!) in class and on the discussion list, performing code and design reviews, etc.
Final Grade
Each grade item is measured as a percentage relative to the highest actually achieved score for that item. Grade items in each category (Iterations, Product, Presentations, Exams, etc.) are averaged, multiplied by the weight of their category, and added together to yield your final percentage score in the course. Your final grade is determined according to the following scale: 100-90: "A", 89-80: "B", 79-70: "C", 69-60: "D", 59-0: "F". Plus and minus grades fall at the extreme ends of these ranges, for example 89 is a "B+" grade but 88 is a "B" grade. There is no curve! There are no "I" grades either!
