|
Introduction to Computer Science II for non-majors by James Tam |
|
|
Actual mark |
Max |
|||||
| Naming conventions | Poor -2 | Some poorly named identifiers +0 | Good and clear throughout +2 | 2 | |||
| Code layout (alignment, formatting, whitespace) | Very cluttered, no whitespace -2 | Slightly too much/too little +0 | Appropriate use of whitespace: +2 | 2 | |||
| Program output layout | Very cluttered, no whitespace, formatting -2 | Slightly too much/too little +0 | Appropriate use of whitespace: +2 | 2 | |||
| Appropriate use of named constants | 1 | ||||||
| Each method implements one well defined task | Never -4 | Seldom +1 | Sometimes +2 | Usually +3 | Always +4 | 4 | |
| Each class (save the Driver) consists of at least 3 methods | Never -4 | Seldom +1 | Sometimes +2 | Usually +3 | Always +4 | 4 | |
| Each method doesn't exceed a screen size in length, 40 lines | Never -4 | Seldom +1 | Sometimes +2 | Usually +3 | Always +4 | 4 | |
| TOTAL | 19 | ||||||
|
|
|
|
|
|
|
|
|
DOCUMENTATION1 |
|
||||||
|
|
Actual mark |
Max |
|||||
| Header documentation. 'Driver' class (Program limitations) | 1 | ||||||
| Header documentation. 'Driver' class (Program versioning) | 1 | ||||||
| Header documentation. 'Driver' class (Assignment features implemented) | 8 | ||||||
| Header documentation. All classes other than the Driver | 4 | ||||||
| Missing contact information in submission (name and student number). Other marks will be granted only if we can determine authorship | -4 | ||||||
| TOTAL | 14 | ||||||
PROGRAM DESIGN1 |
|||||||
| Actual mark | Max | ||||||
| Definition of class User Interface | 2 | ||||||
| Definition of class Critter | 1 | ||||||
| Definition of class Biosphere | 2 | ||||||
| Definition of class GameOfLife | 1 | ||||||
| TOTAL | 6 | ||||||
PROGRAM FUNCTIONALITY2 |
|||||||
| Actual mark | Max | ||||||
| Able to quit the game | 2 | ||||||
| Debugging mode employed | 6 | ||||||
| Biosphere case 1 properly handed | 2 | ||||||
| Biosphere case 2 properly handed | 4 | ||||||
| Biosphere case 3 properly handed | 4 | ||||||
| Biosphere case 4 properly handed | 6 | ||||||
| Biosphere case 5 properly handed | 8 | ||||||
| Biosphere case 6 properly handed | 8 | ||||||
| Biosphere case 7 properly handed (includes 16 marks for cases 1 - 4, 14 marks are unique to handling this case) | 30 | ||||||
| Biosphere case 8 properly handed (includes 46 marks for cases 1 - 7, 14 marks are unique to handling this case) | 60 | ||||||
| TOTAL |
68 |
||||||
TOTAL RAW SCORE FOR ASSIGNMENT |
107 | ||||||
2 These marks will only be awarded if the correctness of implementation can be determined as the program is running.
Item |
Effect on grade |
| Uses static methods (other than the main method) | Divide functionality marks by two1 |
| Program consists of only a single class: | Divide functionality marks by two1 |
| Functionality not assigned to the appropriate class as specified in the assignment description | Max loss of 8 marks (tallied after the above two modifiers, if applicable) |
1 These two penalties are cumulative so if a program was written using only one class and was full of static methods then the student's program functionality mark would quartered.
| Min raw score | Grade point |
| 0 | 0 |
| 20 | 0.7 |
| 25 | 1 |
| 30 | 1.1 |
| 33 | 1.2 |
| 36 | 1.3 |
| 39 | 1.4 |
| 42 | 1.5 |
| 45 | 1.6 |
| 48 | 1.7 |
| 51 | 1.8 |
| 54 | 1.9 |
| 56 | 2 |
| 58 | 2.1 |
| 60 | 2.2 |
| 62 | 2.3 |
| 64 | 2.4 |
| 66 | 2.5 |
| 68 | 2.6 |
| 70 | 2.7 |
| 72 | 2.8 |
| 74 | 2.9 |
| 76 | 3 |
| 78 | 3.1 |
| 80 | 3.2 |
| 84 | 3.3 |
| 86 | 3.4 |
| 88 | 3.5 |
| 90 | 3.6 |
| 92 | 3.7 |
| 94 | 3.8 |
| 96 | 3.9 |
| 98 | 4 |
| 100 | 4.1 |
| 102 | 4.2 |
| 104 | 4.3 |