4thToLife Group - Final Presentation

Transcript

1. Group 2 - 4th to Life Website Link: http://www.nflarrests.me/ Repo link: https://github.com/c4k9c0/cs373-idb
2. Team Members Team Stats: Commits 227 | Issues 54 | Unit Tests 12 Charlie Cox Andy Medina Gabriel Moreira Hunter DeGroot Jena Cameron # of Commits: 63 # of Issues: 21 # of Unit Tests: 4 Back-end, Database, Report, Data Scrapping # of Commits: 54 # of Issues: 13 # of Unit Tests: 6 Carina, Docker, Server Admin, Database # of Commits: 43 # of Issues: 12 # of Unit Tests: 2 Front end, About page, presentation # of Commits: 51 # of Issues: 8 # of Unit Tests: 1 Angular, Bootsrap, JavaScript, API # of Commits: 16 # of Issues: 1 # of Unit Tests: 1 Report, Front-end
3. NFL Crime Stats The stats they don't show during the game. Our project aims to inform users on the actual crime statistics for NFL players. Allowing one to search for their favorite teams and players and view their criminal track record.
4. UML Diagram • Teams have a 1 to many relationship with players • Teams have a 1 to many relationship with crimes • Players have a 1 to many relationship with crimes
5. www.nflarrests.me Live Demonstration
6. Tools 1. API: a. Apiary 2. Front-end: a. Boostrap b. AngularJS c. Flask d. Pie Chart e. Data Tables f. jQuery Data Tables g. HighMaps 3. Collaboration: a. Github b. Slack 4. Database: a. SQL Alchemy 5. Data Modeling: a. yUML 6. Server and Hosting a. Namecheap b. Carina
7. Critiques 1. Criticizing our own application 2. Criticizing group 3’s application
8. Criticizing our own application 1) What did we do well? We believe that overall we implemented all parts of the project well. But if we had to focus on a specific aspect of the project, we are particularly proud of our backend. Our flask, python, models, and angular were well implemented and clean. This made our code to run mostly smoothly and made it easy to follow. 2) What did we learn? We learned lots about Docker containers, MySQL, HTTP requests, and how real world applications are mostly developed. 3) What can we do better? Our API could use some work. It currently returns some null fields and we also do not allow for very specific queries such as (give me all the DUI crimes that this player did in the past year). 4) What puzzles us? What puzzles us a little is the inner workings of Carina/Docker and Angular. Despite being successful in having our application run correctly and smoothly, we believe that a better understanding of those two components would be useful perhaps for more complex future applications.
9. Criticizing group 3’s application 1) What did they do well? We believe that group 3 implemented their models and API well. Their website is rich in content and easy to navigate between models. Their website is insightful. Additionally, they allow their API calls to be very customizable. 2) What did we learn from their website? We learned that you can allow your API call to have more specific search parameters by providing more than a single id on your call. Example: http://sweography.me/api/v1/country{?id,region_id,currency_id,language_id, subregion_id}. Beforehand we were under the impression that your API call had to be less specific. 3) What can they do better? We believe that they could would have displayed more "media" for each model page. Something as simple as a picture of the country's flag would've been cool. That being said we thought it was really interesting how they showed the regions and countries on google maps. 4) What puzzles us about their website? One thing that puzzles us about their website is how you search for a country by ID as opposed to by name. This is also noticed on the URL when navigating through the models. For example, http://sweography.me/countries/18 corresponds to Bangladesh's page.
10. Question & Answers