Category
|
Effect on grade
|
|
Submission guidelines |
|
| |
Incomplete contact information on printout |
-2 points |
| |
Missing electronic submission |
No marks will be received for program
functionality (the only marks granted may come from documentation and
programming style) |
| |
Missing or incorrect title in the subject line of email |
-4 points |
| |
|
|
| Program
documentation |
|
| |
High level description of what the program is
supposed to do |
1 mark |
| |
Describes the limits of the program |
1 mark |
| |
Describes the algorithm employed by the program
(e.g., the effects of the different gestures on the outcome of the game). |
2 marks |
| |
The electronic and paper README file includes
contact information and correctly lists the features that were implemented |
4 marks |
| |
Version number or date of the program |
1 mark |
| |
Features implemented in this version |
1 mark |
| |
Paper printout includes all of the source code |
4 marks |
| |
|
|
| Style marks |
|
| |
Naming conventions (e.g., variables, constants) |
2 marks |
| |
Appearance and whitespace |
2 marks |
| |
Consistency of formatting |
2 marks |
| |
Initialization of variables before they are
used |
2 marks |
| |
Program uses global variables |
-4 point for all (and not each) case |
| |
|
|
|
Program functionality |
|
| |
Displays a proper introduction |
1 mark |
| |
Display a proper conclusion |
1 mark |
| |
Displays a menu that shows the allowable
gestures |
1 mark |
| |
Reads in a gesture for each player |
1 mark |
| |
Checks if an incorrect gesture has been
selected and if so gives the player a forced rock as their gesture |
4 marks |
| |
Upper or lower case input is allowed |
4 marks |
| |
Can correctly determine if a win, lose or tie
has occurred |
12 marks |
| |
The program replays the game if it is desired
by the player |
4 marks |
| |
The game allows for computer vs. human mode |
2 marks |
| |
The game allows for computer vs. computer mode |
2 marks |
Total points
|
|
ASSIGNMENT GRADE |