Loading...
Loading...
Loading...
Repository link: https://github.com/agupta15k/ncsu_se_fall22_22_pr_2
Repository link: https://github.com/agupta15k/ncsu_se_fall22_22_pr_2 Total Score: 83 |Notes|Points|evidence| |-----|---------|---------| |Video1|3|Video can be found [here](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/execution/video) | |Bonus: Xfold improvement|2|We have tackled scalability from various avenues. First we added a functionality to onboard new doctors and hospitals allowing for a higher availability of the application. Also, we tackled scalability from the perspective of time spent by a customer. Previously, when user wanted to book an appointment, it'd have taken over a minute, but now it takes 18 seconds.| |Docs: what: point descriptions of each class/function (in isolation)|3|[Frontend](https://htmlpreview.github.io/?https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/frontendDocs/wolfcare/0.1.0/index.html) and [Backend](https://htmlpreview.github.io/?https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/backendDocs/index.html) 'what' documentation exists| |Use of style checkers |3|Using eslint for [frontend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/frontendGitActions.yml) and flake8 for [backend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/backendGitActions.yml)| |Use of code formatters. |3|Using default code formatters provided by vscode. Some formatting configuration present in the [.vscode folder](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/.vscode)| |Use of syntax checkers. |3|Using eslint for [frontend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/frontendGitActions.yml) and flake8 for [backend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/backendGitActions.yml)| |Use of code coverage |3| Codecov badge present. Codecov run automatically using Github Actions| |Other automated analysis tools| 3 | Github actions used for [frontend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/frontendGitActions.yml) and [backend](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/.github/workflows/backendGitActions.yml)| |Workload is spread over the whole team (one team member is often Xtimes more productive than the others but nevertheless, here is a track record that everyone is contributing a lot)| 3 | Responsibilites of individual modules were deligated to different subgroups, thus all of the group members have contributed to the project. [Contributors](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/graphs/contributors)| |Number of commits|2 | There are a total of [446 commits](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/commits/main) in the repo while 90 were done only for project 2| |Number of commits: by different people|3|The number of commits are balanced across all [contributors](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/graphs/contributors)| |Issues reports: there are **many**|2 | Most of the discussion happened over meetings and chat channels, thus not a lot of issues were needed |Issues are being closed| 3 | All open issues are closed| |DOI badge: exists|3 | DOI badge exists| |Docs: doco generated, format not ugly |3 | [Documentation](https://agupta15k.github.io/ncsu_se_fall22_22_pr_2/) present| |Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z|3 | Execution screenshots can be found [here](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/execution/screenshots). [Video](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/execution/video) showing the execution is also available| |Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing| 3 | 'why' documentation present in the [README](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/README.md) file |Docs: short video, animated, hosted on your repo. That convinces people why they want to work on your code.|3 | [Video](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/execution/video) and [execution screenshots](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/execution/screenshots) available |Use of version control tools|3 | Git is used in this project |Test cases exist|2 | Dozens of test cases exist | |Test cases are routinely executed|3 | Github actions used| |The files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up|3|Descriptive [CONTRIBUTING.md](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/blob/main/CONTRIBUTING.md) file present| |Issues are discussed before they are closed|2 | Closed issues do have little discussion || |Chat channel: exists|3 | Private chat channel exists, some discussion screenshots can be found [here](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/docs/chatChannel/screenshots) |Test cases: a large proportion of the issues related to handling failing cases.|1 | Some issue related to failed test cases discussed | |Evidence that the whole team is using the same tools: everyone can get to all tools and files|3 | All the code is in github. The dependency closure is available for both frontend and backend. Also, vscode IDE [configuration](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/.vscode) present| |Evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)|3 | vscode IDE [configuration](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/tree/main/.vscode) present| |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 | Everybody contributed to development| |Evidence that the members of the team are working across multiple places in the code base|3 | Though the responsibility of developing the modules was divided among team members, everybody contributed to the code base, design, testing, and documentation.| |Short release cycles | 3 | There are regular [commits](https://github.com/agupta15k/ncsu_se_fall22_22_pr_2/commits/main) on the repository|
* [Zoom Meeting for Lectures](https://washington.zoom.us/j/848704242)
The sprint challenge is your chance to independently work through material and build on what you learned this week. In today's project you will build a form for Lambda Eats, a website designed to bring food to hungry coders.
{: .no_toc .text-delta }
- Document number: P1253R0