Group 3 - goodbooksfor.me

Transcript

1. goodbooksfor.me
2. Team Members • Vanessa Alexandra - Frontend • Wade Bribach - Frontend • Jorge Caviedes - Backend • Michael Gurch - Backend • Vincent Truong - Frontend
3. Demonstration goodbooksfor.me
4. Issue Tracker Statistics Name Issues Authored Jorge Alejandro 10 Michael Gurch 8 Vanessa Alexandra 17 Vincent Truong 10 Wade Bribach 10 Gitlab Issues 55 issues resolved 0 issues unresolved
5. Unit Test Statistics Author Unit Tests Jorge Alejandro 2 Michael Gurch 3 Vanessa Alexandra 8 Vincent Truong 5 Wade Bribach 9 Everyone 27 Unit Tests
6. Unit Test Report Name Stmts Miss Branch BrPart Cover createdb.py 107 0 24 0 100% main.py 96 71 34 1 20% models.py 55 0 0 0 100% test.py 244 21 155 19 83% TOTAL 502 92 213 20 76%
7. Critique - goodbooksfor.me What did we do well? • The detail and quantity of information provides for an informing experience for our users. • Easy to navigate and visually pleasing • Categories that were N/A are not shown What did we learn? • How to work effectively as a team to produce a quality website • How to be flexible, communicate, and efficiently distribute workload • How to use PostgreSQL and host a website on GCP
8. Critique - goodbooksfor.me What can we do better? • Place the navigation links to our three categories at the center of the splash page • Allow users to sort with other categories besides title/name What puzzles us? • How to normalize the books data • There’s still a lot to learn about GCP and web development • Unit tests delete database
9. Critique - Group 4 pokedb.me What did they do well? • Clean navigation • Uniform design What did we learn from the website? • Vue.js can be used to make a nice and simple website
11. Critique - Group 4 pokedb.me What can they do better? • Have more data for the pokemons • Improve the visual experience What puzzles us about the website? • Website does not look like it has been updated since Project #3 • No global search bar or sort function • No unit tests on about page