Grading Guidelines
Our goal is to have your homework grades entered in blackboard within 48 hours of the due date, but please allow our graders some flexibility in meeting this deadline (they're overworked students too). For example, if an assignment is due Monday at midnight, your grade should be visible in blackboard by the following Wednesday at midnight. Assignments that are submitted more than 24 hours late are graded on a case-by-case basis and we cannot guarantee the turnaround time for your grade (but we will do our best).
Late Work
As stated in the syllabus, homework that is submitted within 24 hours of the original due date will lose 10% of the possible points. Homework that is submitted within 7 days of the original due date will lose 25% of the possible points. No assignments are accepted that are more than 7 days late.
For example, if an assignment is due Monday by midnight and you turn it in on Tuesday (before midnight) and your work meets all rubric requirements, you will receive a 90%. If you were to submit that assignment on Wednesday (or Thursday, etc) you would receive a 75% grade.
Homework resubmissions due to incorrectly submitted homework may be penalized according to this late work policy.
Rubric Guidelines and Grading Thresholds
All homework assignments are due by midnight the day of the deadline.
Each assignment has a rubric associated with it. The rubric describes in detail how many points are allotted to different elements of complete and correct solution. These include such requirements as naming the source or supporting files correctly, sufficient commentary, formatting code with indentation and {} structure that visually reflects the instruction logic, as making sure a solution tests correctly and provides the correct output for many different input combinations.
An example rubric might look like this:
Requirements |
Points |
Notes |
Name the main routine assignment.cpp |
1 |
|
Correct variable types |
2 |
|
Correct use of const for applicable variables |
2 |
|
Clear prompts specifying correct units of measurement |
2 |
|
Correct cin statements |
2 |
|
Labeled output |
2 |
|
Calculations displayed are correct |
4 |
|
Sufficient commentary describing application |
2 |
|
Sufficient commentary for key equations, data (magic numbers), and logic |
2 |
|
Uses cleanly written and easily read control structures |
4 |
|
This means that erroneous calculations will not deduct more than 4 points from the total score, and poorly formatted source will not result in more than 4 points lost.
There are two exceptions to these rubric guidlines:
- All submitted work must compile. Compiling with warnings is acceptable. Submitted work that does not compile cannot earn more than 65% of the total points for the assignment. This does not include the final project, which has its own set of grading guidelines.
- A work (>=90%) must meet all programming project requirements. The application must not demonstrate any logic bugs. A "perfect" assignment with a demonstrable logic bug can earn at most 89% of the total points for the assignment.
Working around Submission Mistakes
Blackboard does allow students to re-submit a previously submitted assignment. If you realized you have submitted the wrong ZIP file, or a version your solution that does not meet all the rubric requirements, then submit the assignment again as long as the due date has not passed. Be aware that your most recent submission is the work that will be graded. If this causes an issue for some reason, address the problem with your instructor.
Resubmitting Graded Work
Resubmissions of graded work are not accepted in this class. However, if you received a 0 for an assignment that you did not submit correctly, you may resubmit the correct work for grading. Note that in this specific case, late work deductions will be applied. Be sure to know how to submit homework correctly.
Portions © Keith Hellman, Yong Joseph Bakos.