| Documentation (25%) | Readme | Is the documentation easy to understand? | 2% |
| Does the documentation have clear and concise sections? | 2% | ||
|
Does the documentation provice a clear
general overview of the project?
|
2% | ||
| Grammar/Spelling | Is the documentation free of grammatical and spelling errors? | 2% | |
| Is the comments free of grammatical and spelling errors? | 2% | ||
| Is the code free of grammatical and spelling errors? | 2% | ||
| Code Formatting | Is the code adhereing to the Oracle Java Style Guide Standard? | 2% | |
| Are variables/functions named appropriately? | 2% | ||
| Are comments placed appropriately and adhering to the style gude? | 2% | ||
| Are classes/packages/files named appropriately? | 2% | ||
| Is outside code cited? | 5% | ||
| Implementation (35%) | Version Control | Is a branch created to address each requirement or feature? | 4% |
| Are only functional branches merged into master? | 5% | ||
| Are comment messages informative? | 4% | ||
| Is the master branch free of direct work? | 5% | ||
| Architecture | Are effective and efficient data structures used? | 4% | |
| Was the code designed and constructued in a modular fashion? | 5% | ||
| Were generally sound decisions made with regard to architecture? | 4% | ||
| Is the code DRY (Don't repeat yourself)? | 4% | ||
| Exectution (40%) | Parsing | Does the program pass complilation with no warnings? | 6% |
| Safety | Does invalid input cause the program to crash? | 6% | |
| Does invalid input cause the program to act inappropriately? | 6% | ||
| Requirements | Were all requirements met? | 10% | |
| Were all inputs parsed correctly and yield the correct output? | 6% | ||
| Performance | Does the program execute in a timely manner? | 6% |