---
# System prepended metadata

title: HW5 GitHub URL3 rubric Assessment

---

# HW5 GitHub URL3 rubric Assessment
https://github.com/sohambapat/SWE-Group-32-Assignments
|Notes|Score (Total= 58)|evidence|
|-----|-----------------|-------------|
|Video1| 0 |Not applicable|
|Video2| 0 |Not applicable|
|Workload is spread over the whole team (one team member did far less than other teammates)|2|evidence in GH|
|Number of commits|3|in GH|
|Number of commits: by different people|3|in GH|
|Issues reports: |0|no issue|
|Issues are being closed|0|no issue|
|DOI badge: exists|3|in GH|
|Docs: doco generated, format not ugly|3|in this [link](https://sohambapat.github.io/SWE-Group-32-Assignments/src/)|
|Docs: what: point descriptions of each class/function (in isolation) |3|
|Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z|3|doc page entries|
|Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing|2|
|Docs: short video, animated, hosted on your repo. That convinces people why they want to work on your code.|0|
|Use of version control tools|3|using GitHub|
|Use of style checkers |3|
|Use of code formatters. |3|
|Use of syntax checkers. |3|
|Use of code coverage |0|not shown in GitHub|
|Other automated analysis tools|0|None|
|Test cases exist|3|
|Test cases are routinely executed|3|
|The files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up|3|
|Issues are discussed before they are closed|0|no issue|
|Chat channel: exists|0|
|Test cases: a large proportion of the issues related to handling failing cases.|0|no issue
|Evidence that the whole team is using the same tools: everyone can get to all tools and files|3|
|Evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)|3
|Evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)|3|
|Evidence that the members of the team are working across multiple places in the code base|3|
|Short release cycles | 3|