| The Introduction to multidisciplinary Computer Science II by James Tam | Return to the course web page |
Item |
Effect on grade |
| Uses static methods (other than the static methods specified in the assignment description) | Divide functionality marks by two (rounded down)1 |
| Program consists of only a single class | Divide marks functionality marks by two (rounded down)1 |
Missing contact information in submission (name and student number) |
-8 marks (assuming the source of the submission can be determined) |
1 These two penalties are cumulative: a program with 1 class and was full of static methods would have the functionality marks quartered.
How often are general style requirements followed (approaches that applies to all programming paradigms O-O or procedural) e.g., good naming conventions, appropriate use of named constants, code uses alignment and whitespace to make it easier to read and understand, methods/functions implement one well defined task and don't exceed a screen in length |
Actual mark |
Max |
||||
| Never (0 marks) |
Sometimes (2 marks) |
Mostly (4 marks) |
Always (6 marks) |
|||
| Sub-total | 6 | |||||
How often are Object-Oriented style requirements followed e.g., appropriate decomposition into classes, class definition encapsulate appropriate attributes and behaviours, information hiding employed, decomposition relatively balanced among classes (i.e., there isn't one class that includes all or most of the functionality) |
Actual mark |
Max |
||||
| Never (0 marks) |
Sometimes (2 marks) |
Mostly (4 marks) |
Always (6 marks) |
|||
| Sub-total | 6 | |||||
TOTAL FOR STYLE |
12 |
|||||
|
|
|
|
|
|
|
|
DOCUMENTATION: INTERNAL TO PROGRAM |
|
|||||
Example things to include: some sort of versioning system, a description of the features of the program (what it does rather than how it does it), limitations of the program (features not implemented or cases that it can't handle). |
Actual mark |
Max |
||||
|
|
No documentation (0 marks) |
Major omissions (4 marks) |
Minor omissions (10 marks) |
Appropriate level (12 marks) |
||
TOTAL FOR DOCUMENTATION |
12 |
|||||
DOCUMENTATION: EXTERNAL README FILE (formats allowed: text, doc, html, pdf. |
|
|||||
Includes instructions about how to run the program (especially important if there's additional multimedia requirements such as images), what functional requirements (listed in the assignment) were actually implemented. Your mark for this component will be determined by the completeness (e.g., don't omit crucial instructions) and correctness (e.g., don't list features that you didn't complete) of the README file. |
Actual mark |
Max |
||||
TOTAL FOR EXTERNAL DOCUMENTATION |
10 |
|||||
PROGRAM STRUCTURE |
|
|||||
Marks will be awarded for defining the classes in the fashion specified in the assignment description |
Actual mark |
Max |
||||
| Lotr | 1 | |||||
| CommandProcessor | 4 | |||||
| MEWorld | 4 | |||||
| Hobbit | 2 | |||||
| Human | 2 | |||||
| Goblin | 2 | |||||
| UrukHai | 2 | |||||
TOTAL FOR STRUCTURE |
17 |
|||||
PROGRAM FUNCTIONALITY2 |
||||||
| Marks can be awarded for the preceding categories (style, documentation and structure) independent of program functionality (e.g., you could theoretically receive up 64 marks for a non-functional program assuming that the program demonstrated how the above requirements were met (e.g., it would be difficult to demonstrate good style with a completely empty program). However functionality marks will be awarded as the marker runs your program (non-compiling programs or programs with excessive amounts of run time errors will be awarded few, if any marks for functionality). | Actual mark | Max | ||||
| Displays intro | 1 | |||||
| Displays conclusion | 1 | |||||
| Program can read starting positions from input file | 2 | |||||
| Displays simulation world with numbered grid around elements | 2 | |||||
| Game runs until the user quits from the menu (credit for checking the win/lose game conditions are given separately) | 3 | |||||
| A turn is broken down into correctly ordered sub-turns with the program pausing and displaying the world as appropriate | 6 | |||||
| The main (movement) menu is displayed | 1 | |||||
| The attack menu is displayed | 1 | |||||
| The cheat menu can be accessed from the main menu | 2 | |||||
| Debug mode can be toggled from the cheat menu | 4 | |||||
| Cheat mode can be toggled from the cheat menu | 4 | |||||
| Boromir can move based on player's input (you get more marks as you refine this feature as specified below) | 8 | |||||
| Can move to adjacent squares (4 marks) | ||||||
| Can only move to empty squares, not even the exit (2 marks) | ||||||
| Checks for array bounds (2 marks) | ||||||
| The hobbits can automatically move (you get more marks as you refine this feature as specified below) | 8 | |||||
| Can move the prescribed: west-east, north-south fashion (4 marks) | ||||||
| Can only move to empty squares (2 marks) | ||||||
| Checks for array bounds (2 marks) | ||||||
| The orcs (goblins and Uruk-hai) can automatically move (you get more marks as you refine this feature as specified below) | 8 | |||||
| Randomly move to an adjacent square (4 marks) | ||||||
| Can only move to empty squares (2 marks) | ||||||
| Checks for array bounds (2 marks) | ||||||
| Game displays updated and correct statistics for Boromir and the hobbits | 2 | |||||
| Can detect win game condition: the game should immediately end with a suitable congratulatory message | 4 | |||||
| Can detect lose game condition: the game should immediately end with a suitable consolation message | 4 | |||||
| Player can get Boromir to attack orcs that are adjacent | 6 | |||||
| Computer automatically has the hobbits attack an adjacent orc | 6 | |||||
| Computer automatically has the goblins attack one adjacent good guy (Boromir or hobbits) | 6 | |||||
| Computer automatically has the Uruk-Hai attack a good guy (Boromir or hobbits). You can get marks for both of the features specified below. | 12 | |||||
| Uruk-Hai attack adjacent only (6 marks) | ||||||
| Uruk-Hai can attack up to two squares distant (6 marks) | ||||||
| Hobbits can blend into terrain (50% chance each attack does no damage) | 4 | |||||
| Game processes the slaying of Boromir: You can get marks for both of the features specified below. | 6 | |||||
| Boromir is removed from the game (4 marks) | ||||||
| Game runs on automatic, attack and move menus no longer displayed (2 marks) | ||||||
| Goblins can be slain | 3 | |||||
| Uruk-Hai can be slain | 3 | |||||
| 2 For the most part you can implement these features in whatever order that you wish. In some cases order is obviously important e.g., you need to implement orc combat before you could get credit for implementing invulnerability mode or you need to implement hobbit movement before you get credit for checking the win game condition | ||||||
| TOTAL FOR PROGRAM FUNCTIONALITY |
107 |
|||||
PROGRAM OVERVIEW |
|
|
||||
| Actual mark | Max | |||||
UML diagram (should be the 'full' version that shows method signatures, return values and all the relationships) |
|
13 |
||||
EXTRA BONUS |
||||||
| Actual mark | Max | |||||
Program displays output graphically instead of using text |
10 |
|||||
| Total score | Letter |
| A+ | 162 - 1713 |
| A | 152 - 161 |
| A- | 142 - 151 |
| B+ | 130 - 141 |
| B | 118 - 129 |
| B- | 106 - 117 |
| C+ | 93 - 105 |
| C | 80 - 92 |
| C- | 67 - 79 |
| D+ | 52 - 66 |
| D | 37 - 51 |
| D- | 22 - 36 |
| F | 0 - 21 |
3 Although the max score is 171, this can be further increased by implementing the extra bonus (graphical output) of 10 marks
TOTAL MARKS |
LETTER GRADE |