CS373 Group 2 Presentation

JINWOOK KIM
BEN NGUYEN
FAISAL ALDILAIJAN
SEAN WANG
AHMED AL NABIL

https://github.com/JinwookKim/cs373-idb

Transcript

1. Group 2 Presentation Collegedb.me
2. Group Members ▪ JINWOOK KIM ▪ BEN NGUYEN ▪ FAISAL ALDILAIJAN ▪ SEAN WANG ▪ AHMED AL NABIL
3. Demonstration http://collegedb.me
4. Issue Tracker Stats Total number of issues: 45 Resolved: 45/45 Per member: ▪ JINWOOK KIM: 9 ▪ BEN NGUYEN: 12 ▪ FAISAL ALDILAIJAN: 5 ▪ SEAN WANG: 10 ▪ AHMED AL NABIL: 9
5. Unit Test Stats Total number of unit tests: 30 Per member: ▪ JINWOOK KIM: 3 ▪ BEN NGUYEN: 3 ▪ FAISAL ALDILAIJAN: 8 ▪ SEAN WANG: 8 ▪ AHMED AL NABIL: 8
6. Our Own Critiques What did we do well? ▪ Incorporated a lot of APIs on the front end including Google Maps to locate universities. ▪ Choosing a reliable and official government API that did not have rate limits ▪ Using smart-table.js on the front end to make tables easier ▪ Chose GCP as our host option which did not cost us anything because we had a $300 free credit. ▪ Used angular-chart.js to make nice graphs using the smashdb.me API.
7. Our Own Critiques What did we learn? ▪ We learned how to use: - Flask - SQLAlchemy - PostgreSQL - Apiary - Smart-table.js - angular-chart.js ▪ How to run a database on Travis CI ▪ Defining our own routing functions ▪ Running unit tests from flask ▪ Learned how to effectively use Slack to communicate and received updates from github
8. Our Own Critiques What can we do better? ▪ Do pagination on the backend. ▪ Add more options for how many rows show per table. ▪ Optimize images on the website for web. ▪ Make website more phone compatible. ▪ Improve homepage to have more content. ▪ Have better naming conventions between front-end and back-end ▪ Improve how we serve JSON data
9. Our Own Critiques What puzzles us? ▪ Why it is hard to test a flask app that uses different database credentials from the testing database? ▪ Why does GCP crashes randomly? (See http://bit.ly/2pSeZ0p) ▪ Why is CSS hard? ▪ Why is it hard to run unit tests from another python module? ▪ Why doesn’t the UTCS machines have PostgreSQL? ▪ Why is it hard to setup the same environment on each member’s machine?
10. Group 3 Critiques smashdb.me What did they do well? ▪ Really nice About page that summarizes all the data in an easy to read table. ▪ They took the time to create their own customized favicon ▪ Row highlighting to know which row you’re pointing to. ▪ They made images appear in tables while still having them fit well. ▪ Using more than one datasource. ▪ Having sanitized tournament names in their API ▪ The navigation header moves with the user when scrolling up or down.
11. Group 3 Critiques smashdb.me What did we learn from their website? ▪ Row highlighting which we later implemented on our own website. ▪ You can add images to rows in tables. ▪ You can add a column to a table without having a header (e.g. the “More Info” column) ▪ That we could have used sanitized strings in our API ▪ We could have used more than one source for our main data
12. Group 3 Critiques smashdb.me What can they do better? ▪ Sorting tournaments by date could have used sanitized dates or a custom compare function. ▪ Tournaments table could have listed the number of entrants. ▪ Re-include the vertical scrolling bar on the website.
13. Group 3 Critiques smashdb.me What puzzles us about their website? ▪ Why does each participant only has one tournament? ▪ Why does the participants table list the sponsor before the participants tag? ▪ Why does the characters’ API list the moves as a string and not as an array.
14. Running Unit Tests http://collegedb.me/runtests