Code | Points | Description |
---|---|---|
A1 | 2 | Submission is zip containing q1.py, q2.py and q3.py |
A2 | 2 | Zip is named after uni, unzips to folder with uni-hw1 |
A3 | 2 | q1.py is plain text file with pseudocode commented |
A4 | 2 | q2.py is plain text file with pseudocode commented |
A5 | 2 | q3.py is plain text file with pseudocode commented |
Each one all-or-nothing
Code | Points | Description |
---|---|---|
B1 | 3 | Valid Pseudocode |
B2 | 3 | Handles Monday-Sunday |
B3 | 3 | No problematic duplication of tasks (e.g. getting dressed twice, etc) |
B4 | 3 | Style and Effort |
Style and Effort: Clean, well structured, organized, no typos, well thought-through, etc
Code | Points | Description |
---|---|---|
C1 | 3 | Valid, Well-formed Pseudocode |
C2 | 3 | Valid Python code |
C3 | 3 | Clean Python code |
C4.1 | 3 | Test case 1 - pseudocode |
C4.2 | 3 | Test case 2 - pseudocode |
C4.3 | 3 | Test case 3 - pseudocode |
C5.1 | 3 | Test case 1 - python |
C5.2 | 3 | Test case 2 - python |
C5.3 | 3 | Test case 3 - python |
C6 | 3 | Style and Effort |
Can either print result or return result.
Style and Effort: Pseudocode is clean, well structured, organized, no typos, well thought-through, etc. Python code is clean and well structured, no superfluous content, no dead code, no debugging steps, no excessive steps or printing, etc.
Code | Points | Description |
---|---|---|
D1 | 3 | Valid, Well-formed Pseudocode |
D2 | 3 | Valid Python code |
D3 | 3 | Clean Python code |
D4.1 | 3 | Test case 1 - pseudocode |
D4.2 | 3 | Test case 2 - pseudocode |
D4.3 | 3 | Test case 3 - pseudocode |
D5.1 | 3 | Test case 1 - python |
D5.2 | 3 | Test case 2 - python |
D5.3 | 3 | Test case 3 - python |
D6 | 3 | Style and Effort |
Can either print result or return result.
Style and Effort: Pseudocode is clean, well structured, organized, no typos, well thought-through, etc. Python code is clean and well structured, no superfluous content, no dead code, no debugging steps, no excessive steps or printing, etc.