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 main method) | Divide marks for Part II by two (rounded down)1 |
Program consists of only a single class: | Divide marks for Part II by two (rounded down)1 |
Missing contact information in submission (name and student number) |
-6 marks (assuming the source of the submission can be determined) |
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.
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 (2 marks) |
Minor omissions (8 marks) |
Appropriate level (10 marks) |
||
TOTAL FOR DOCUMENTATION |
10 |
|||||
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 |
||||
CommandProcessor | 3 | |||||
Mode | 1 | |||||
RaceSim | 1 | |||||
Runner | 3 | |||||
Track | 3 | |||||
Weather | 3 | |||||
TOTAL FOR STRUCTURE |
14 |
|||||
PROGRAM FUNCTIONALITY |
||||||
Marks can be awarded for the preceding categories (style, documentation and structure) independent of program functionality (e.g., you could theoretically receive up 46 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 runs until the user quits | 1 | |||||
Program can determine when the end of the race has occurred (1+ runner finishes) and the end segment of the track is displayed | 2 | |||||
Tie condition can be determined3 | 2 | |||||
Win condition can be determined | 2 | |||||
Loss condition can be determined | 2 | |||||
Shows menu | 1 | |||||
Shows track with numbered grid (display is paused) | 4 | |||||
Shows each runner's status (2 marks for each piece of information: mode, distance, state) | 6 | |||||
Strength affects sprinting speed | 4 | |||||
Endurance affects burnout and getting winded | 4 | |||||
Discipline affects ability to maintain speed | 4 | |||||
The default allocation of points among strength, endurance, discipline can be changed (program checks that constraints are met and allows the user to opt of customization and accept the defaults) | 6 | |||||
Weather: wind affects distance traveled | 4 | |||||
Weather: temperature affects endurance modifier | 4 | |||||
Running speed of 'P' competitor can be determined by the user each turn (checks for burnout and getting winded) | 6 | |||||
Running speed of each 'X' competitor is randomly determined by the program (checks for burnout and getting winded) | 6 | |||||
Debug mode implemented | 4 | |||||
TOTAL FOR PROGRAM FUNCTIONALITY |
64 |
|||||
Extra bonus |
||||||
Actual mark | Max | |||||
Program displays output graphically instead of using text | 6 |
Total score | Letter |
A+ | 100+ |
A | 94 - 99 |
A- | 88 - 93 |
B+ | 82 - 87 |
B | 76 - 81 |
B- | 70 - 75 |
C+ | 60 - 69 |
C | 50 - 59 |
C- | 40 - 49 |
D+ | 30 - 39 |
D | 20 - 29 |
D- | 10 - 19 |
F | 0 - 9 |
TOTAL MARKS |
LETTER GRADE |