Comp527: Soda Machine Project Grading
To address some ambiguity in the project spec, and the soda machine project
counts for 30% of your final grade in the class, here's how I expect the project
will be graded. The numbers here add up to 100%, which will then be scaled appropriately.
- Milestone 1 (40%)
-
- Threat model: is the model reasonable? (5%)
- Design: does the (paper) design address the threats? (15%)
- Formal analysis: does the cryptyc model correspond meaningfully
to the paper design? Or, where it diverges from the paper design, is there
good reason for it? (5%)
- Is the cryptyc analysis reasonable (e.g., are the begin/end assertions
right) (15%)
- Milestone 2 (20%)
-
- Is the analysis reasonable? If the analyzed protocol is robust, does
the analysis bear out that robustness or does it just blindly agree with
what was written before? If the analyzed protocol is broken, does the
analysis explain why, give counter-examples, or otherwise provide helpful
feedback to the original authors? (20%)
- Milestone 3 (40%)
-
- Were any design revisions, made necessary by the analysis, addressed
properly? (10%)
- Does the code implement the protocol as newly specified? (20%)
- Does the project "work", including getting all the GUI elements
functioning? (10%)
Dan Wallach, CS
Department, Rice University
Last modified:
Thu 19-Sep-2002 18:51