Course web page: Introduction to Computer Science for non-majors II James Tam | Return to the course web page |
Programming style (credit may be awarded independent of functionality) | Student grade | Max grade |
Follows good programming conventions common to all programs (e.g., Appropriate source code white space, self documenting names, clear/simple expressions, methods implementing one task/max 30 lines of code, appropriate used of named constants): Never (0), Sometimes (2), Often (6), Mostly (8), Always (10) | 10 | |
Information hiding: Never (0), Sometimes (1), often (2), Mostly (3), Always (4) | 4 | |
Each class (save the "Driver") consists of at least 3 methods | 3 | |
Static variables employed (debugging flags excepted), -4 marks each instance with a max of 12 marks lost | -12 | |
The code for the classes are not included in its own file | -15 | |
Sub-total: Style | 0 | 17 |
Documentation (credit may be awarded independent of functionality) | Student grade | Max grade |
Header documentation includes full name and tutorial section | 2 | |
Some form of versioning system is demonstrated in the header documentation | 2 | |
Program limitations documented | 1 | |
Program features documented (cut and paste out of the assignment specifications acceptable but it MUST be detailed, clear and specific...the marker must be able to know exactly what features in this marking key were actually working) | 6 | |
Each function/method is documented (similar to documentation for the entire program but applies only to that function/method) | 10 | |
Sub-total: Documentation | 0 | 21 |
Program functionality (program must run to be awarded credit) | Student grade | Max grade |
Able to quit game | 2 | |
Debug 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 | 14 | |
Biosphere case 8 properly handed | 14 | |
Sub-total: Functionality | 0 | 68 |
UML class diagram | ||
Class Biosphere | 4 | |
Class Critter | 4 | |
Relationship and multiplicity | 2 | |
Sub-total: UML | 0 | 10 |
Design requirements (may modfiy the functionality score) | ||
Implements static methods other than 'main()': halve marks | ||
Program consists of only one class (style marks will also be lost): halve marks | ||
Functionality not assigned to the appropriate class as specified in the assignment description (e.g., the attacker implements a task that belongs to the defender): max 10 marks lost | ||
Sub-total: Design requirements modifiers | ||
Assignment: total raw score | 0 | 116 |
Assignment: grade point | 0 | 4 |
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.
Raw score min | Grade point |
0 | 0 |
20 | 0.7 |
30 | 1 |
40 | 1.1 |
50 | 1.2 |
55 | 1.3 |
58 | 1.4 |
61 | 1.5 |
64 | 1.6 |
67 | 1.7 |
70 | 1.8 |
72 | 1.9 |
74 | 2 |
76 | 2.1 |
78 | 2.2 |
80 | 2.3 |
82 | 2.4 |
84 | 2.5 |
86 | 2.6 |
88 | 2.7 |
90 | 2.8 |
92 | 2.9 |
94 | 3 |
96 | 3.1 |
98 | 3.2 |
100 | 3.3 |
102 | 3.4 |
104 | 3.5 |
106 | 3.6 |
108 | 3.7 |
110 | 3.8 |
112 | 3.9 |
114 | 4 |