01 Prove : Assessment Guidelines
Overview
This document outlines the guidelines for instructors and teaching assistants to use as they assess the assignment. It is intended to give structure and guidance to the grading process to ensure that the most important components of the assignment are highlighted, and to promote consistency across sections.
In all cases, the instructor has the latitude to deviate from this rubric on a case-by-base basis to provide the holistic assessment that, in their judgment, best matches the assignment.
Fundamental Concepts
This assignment is designed to highlight the following fundamental concepts:
Using functions
Working with files
Scoring
The following categories are used to score this assignment:
/50 - Correct Functionality /50 - Code Quality / Design -------- /100 - Total
Functionality
The following are examples of the types of things to look for, along with a recommendation for the points associated with it.
-15 if play again functionality not working
-15 if higher / lower not working
-7 if the number of guesses isn't working
-5 for formatting / whitespace issues with testbed
-5 if random seed doesn’t work out with testbed
Code Quality / Design
The following are examples of the types of things to look for, along with a recommendation for the points associated with it.
-10 if variable names are very bad (e.g., a, b, c)
-5 if variable names are too short / abbreviated / not really descriptive (“cnt" should be “count”, "gss" instead of "guess"). It is fine to use "num" for "number"
-5 if using recursion for playing again, suggest that it would be simpler to use a loop
-5 if using a break statement to leave a loop instead of letting the condition naturally terminate it
-2 for statements that could be simplified quite a bit (provide for them what they could have done)
-0, but make suggestion if they used camelCase instead of underscore_names (e.g., playAgain should be play_again)
-0, no comments are required for this program