Homework
| Homework | Due Date | |
|---|---|---|
| Homework #1 | Tuesday October 13th @ 11:59pm CT | |
| Homework #2 | Tuesday October 20th @ 11:59pm CT | |
| Homework #3 | Tuesday October 27th @ 11:59pm CT | |
| Homework #4 | Tuesday November 3rd @ 11:59pm CT | |
|
Homework #5 Homework #5 Images (Download this!Place this inside hw5/blackjack directory) |
Tuesday November 10th @ 11:59pm CT | |
| Homework #6 | Tuesday November 17th @ 11:59pm CT |
Projects
| Project | Due Date |
|---|---|
| Final Project | Thursday December 10th @ 11:59pm (No Extensions!) |
Project/Homework Rubric
The following general rubric will be used to grade your coding problems in your homework and projects. The rubric allows for more transparency on how your assignments are graded. Short answer questions and written work will be more subjective.-
Completeness (30-75% of grade): This score will be determined by the result of running a series of automated tests on your code. The tests check whether your code implements the tasks we ask you to implement in the assignment and, thus, are a good measure of how complete your code is. On some occassions, you will be given a few test cases to check against your implementation.
-
Correctness (10-60% of grade): This score encompasses issues with your code that, while not explicitly captured by the tests, could lead to incorrect behaviour (or simply neglect to implement something we told you to implement).
We will usually provide you some hints on what we will be looking out for in this component of the rubric. Please note that this section of the rubric will never re-penalize you for a failure that is already captured by the tests. So, if your code fails to implement something we told you to implement, but that is already captured by the tests, we would not re-penalize you here.
-
Design (0-20% of grade): This score will be determined by “qualities, many of which are intangible, that don’t have to do with (and exist to some extent independently of) the correct operation of your code.” (thanks to Adam Shaw for this concise phrasing). For example, in many assignments you will have to decompose your code into multiple functions, where that decomposition is up to you. Whether your decomposition makes sense and is well designed would be evaluated in this score.
-
Style (10-20% of grade): For style, we will generally be looking at the following:
- Documenting functions: Every top-level function written by you must have a comment documenting its purpose.
- Clarity: Your code must be easy to read and understand. This is a fairly subjective aspect, but common deductions for lack of clarity include using variables without descriptive names, writing convoluted code that would be easier to understand with more code comments, using magic numbers, etc.