-
-
Notifications
You must be signed in to change notification settings - Fork 15
Suggested Scoring Rubric for the Projects
Chan Ju Ping edited this page Jan 31, 2023
·
6 revisions
Here is our suggested rubric for scoring on projects created with Python. Elements can be added or removed where necessary.
Poor (1) | Average (2) | Good (3) | |
---|---|---|---|
Hosting | Program not hosted anywhere. | Program not hosted on an accessible git server. Git commands unavailable for downloading project. | Project properly hosted on a publicly accessible git server. git clone <url> function pulls in a complete project. |
README.md | No README.md found or contents of README.md file are irrelevant. | A rudimentary README.md file is included but fails to adequately cover how to run the program. | A README.md file is included with the project, fully describing its purpose and instructions to get the program to run. |
Wiki | Wiki documentation not done. | Wiki documentation is rudimentary, and does not provide more guidance than that already found in the README.md file. | Wiki properly used to document additional background and usage of project with examples, notes on limitations, and other pieces of information. |
Functionality | Program does not work. | Program mostly works and fulfils some requirements. | Program works and fulfils all requirements. |
In-line Comments | None or irrelevant comments. | Inconsistent comments, but what is there is useful. | Clear comments that explain what the learner was trying to achieve. |
Improvements | No improvements based upon the upstream project was made. | At least one area of improvement was made to the project based on the upstream project it is based on. | Project was improved upon above and beyond what was expected of the learner. |
Elements | Included none of the following elements:
|
Included some of the following elements:
|
Included all of the following elements:
|
Presentation | No clear explanation provided. | Presentation is mostly understandable, but missing crucial details that require further clarification. | Provides a clear and thorough explanation of the project such that no additional questions are required. |
Additional scoring rubric for group efforts:
Poor (1) | Average (2) | Good (3) | |
---|---|---|---|
Bug Reports | No bug reporting ever used to address issues. | Bug reports filed, but lack actionable details. | Bug reports used to highlight important issues with proper debugging information for developers to attempt to duplicate. |
Pull Requests | No usage of pull request feature. | Usage of pull request feature not done appropriately to address issues. | Proper use of pull request feature that allows improvements to the project efficiently. |
Merge | No merging of branches or pull requests. | Improper merging of branches or pull requests resulting in faulty code. | Proper usage of merging of branches and pull requests that improves the main project branch without causing unexpected faults. |