Capstone Grading Rubric
| Group Participation (60%) | |
| Tier IV (1) | full participation in all stand up meetings and scrums, except in the case of an EXCUSED absence from class shows strong willingness to cross over and help classmates with other tickets useful and complete Git commit messages on all commits no complaints have been brought to instructor or staff attention that have resulted in instructor action |
| Tier III (0.75) | full participation in all stand up meetings and scrums, except in the case of an EXCUSED absence from class shows moderate willingness to cross over and help classmates with other tickets useful and complete Git commit messages on most commits no complaints have been brought to instructor or staff attention that have resulted in instructor action |
| Tier II (0.5) | missed one stand up meeting or scrum (EXCUSED absences from class excluded) shows little or no willingness to cross over and help classmates with other tickets inconsistent Git commit messages no complaints have been brought to instructor or staff attention that have resulted in instructor action |
| Tier I (0.25) | missed two stand up meetings or scrums (EXCUSED absences from class excluded) shows little or no willingness to cross over and help classmates with other tickets inconsistent or missing Git commit messages complaints brought to instructor or staff attention have resulted in instructor action |
| Tier 0 (0) | missed three or more stand up meetings or scrums (EXCUSED absences from class excluded) shows little or no willingness to cross over and help classmates with other tickets inconsistent or missing Git commit messages complaints brought to instructor or staff attention have resulted in instructor action |
| Coding Standards & Documentation (10%) | |
| Tier IV (1) | all classes, interfaces, functions, and methods have doc blocks all major blocks of code are commented all comments make it so any developer can easily discern what the code is doing all variable names are sensical and consistently in camelBack capitalization all blocks consistently indented all line endings are Unix style (i.e., \n and not \r\n) One True Bracing Style (1TBS) is strictly adhered to |
| Tier III (0.75) | all classes, interfaces, functions, and methods have doc blocks most major blocks of code are commented most comments make it so any developer can easily discern what the code is doing all variable names are sensical and consistently in camelBack capitalization all blocks consistently indented line endings may be inconsistent 1TBS is strictly adhered to |
| Tier II (0.5) | most classes, interfaces, functions, and methods have doc blocks most major blocks of code are commented comments are often notes to the developer and serve no purpose to an external audience variable names may or may not be sensical and consistently in camelBack capitalization blocks are indented with an inconsistent mix line endings may be inconsistent 1TBS is strictly adhered to |
| Tier I (0.25) | doc blocks are missing from two or more classes, interfaces, functions, or methods major blocks of code are inconsistently commented comments are often notes to the developer and serve no purpose to an external audience variable names may be inconsistent blocks are indented with an inconsistent mix line endings may be inconsistent 1TBS rules are violated |
| Tier 0 (0) | doc blocks are missing from four or more classes, interfaces, functions, or methods five or more major blocks of code are not commented variable names are inconsistent variable names use a notation other than camelBack 1TBS rules are violated |
| Code Correctness &; Efficiency (10%) | |
| Tier IV (1) | database calls are used wisely (e.g., no database calls in a loop) all database methods have an accompanying unit test with full coverage of all MySQL methods all pages are mobile-first, cross browser compatible look-and-feel of all pages are consistent, coherent, and professional |
| Tier III (0.75) | some complicated processes may use database calls within a loop most database methods have an accompanying unit test with full coverage of all MySQL methods one cross browser problem is present look-and-feel is inconsistent or layout errors are present |
| Tier II (0.5) | some complicated processes may use database calls within a loop most database methods have an accompanying unit test with full coverage of all MySQL methods one cross browser problem is present look-and-feel is inconsistent or layout errors are present |
| Tier I (0.25) | some complicated processes may use database calls within a loop most database methods have an accompanying unit test with full coverage of all MySQL methods general purpose code is copied and pasted where it's used two cross browser problems are present look-and-feel has major problems in consistency |
| Tier 0 (0) | no regard is given to efficiency or performance three or more database methods are missing accompanying unit test with full coverage of all MySQL methods general purpose code is copied and pasted and often diverges from its original purpose three or more cross browser problems are present look-and-feel has no consistency or cohesion, or is incomplete |
| Security (20%) | |
| Tier IV (1) | all user input and output is filtered all forms are validated XSRF is used on all forms using the POST method all properties are read from an encrypted file |
| Tier III (0.75) | all user input and output is filtered most forms are validated XSRF is used on all forms using the POST method all properties are read from an encrypted file |
| Tier II (0.5) | most user input and output is filtered most forms are validated all properties are read from a file outside the web directory |
| Tier I (0.25) | no input sanitization is performed on the front end all properties are read from a file inside the web directory |
| Tier 0 (0) | no input santitization is performed at all properties can be found ANYWHERE in GitHub's history |