CS 241 - Assessment Guidelines

02 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 - Functionality
/20 - Use of Functions
/20 - General Code Quality
/10 - Style
-------
/100 - Total

Overall Scoring

For each of the categories the following general scoring guidelines apply:

100% - Correctly implemented
85% - Minor error exists
70% - A major error or multiple minor errors exist
50% - A good attempt was made.
0% - No attempt made.

If necessary, scores in between the above classifications can be assigned.

Examples of Major/Minor errors

Functionality

Attempt - On the right track, but didn't find high or low rate
Major - Missing the high or the low rate, but have the other
Major - Found the high and low rates, but missing company details
Minor - Slightly incorrect average
Minor - Formatting errors

Use of Functions

In general, they sould have three or more functions where at least one of the functions is the main.
Attempt - There is only one function in the code.
Major - There are only two functions one of which is the main function.
Minor - There are three or more functions but no main function

General code quality

Major - Excessive use of global variables
Minor - Slight use of global variables
Minor - Reading through the file multiple times, rather than computing both the high and low simultaneously.
Minor - Loops that are exiting using a "break" statement.
Note: If the program doesn't have something like "if __name__ == "__main__"", don't deduct points, but mention this as a suggestion.

Style