The Naughty List

Transcript

1. Group 11 The Naughty List Ralph(Yu-Huan), Chang Paul Clukey Evan Plunkett Michael Sams
2. Demonstration
3. Database Design • API switch led to redesign • Relationships: ◦ CLUB 1:N PLAYER ◦ CLUB N:M GAME ◦ PLAYER N:M GAME • Note: a = away, h = home
4. Database Design (cont.)
5. Repository Stats Ralph Paul Evan Michael Total Issues Opened 5 30 6 13 51 Resolved 5 30 6 13 51 Unresolved 0 0 0 0 0 Unit Tests 0 44 (Postman) 0 9 (Models) 53 Commits 53 77 19 48 195
6. Critique of our website • What did we do well? Searching and sorting is quite extensive. All pillar elements are clickable with relations to other pillars. Carousel on home page. • What did we learn? Gained experience with website design, API scraping, API implementation, website hosting, database design, working in teams.
7. Critique of our website • What can we do better? Integrate Postman tests into GitLab CI/CD. Expand quantity of data and visualization (difficult with API used). • What puzzles us? Containerization especially in terms of GitLab CI/CD and GCP App Engine deployment.
8. Critique of Project 12 • What did they do well? Nice home page, about us page, Bootstrap implementation very nice. API well documented on Postman. Active search feature. • What did we learn from their website? Bootstrap can be very powerful when used correctly (Home and About pages).
9. Critique of Project 12 • What can they do better? Individual instance pages seem a little sparse, could use more design elements, pictures of the sites, etc. No links from an individual instance page to other sections of the website. • What puzzles us about their website? No way to select which column to search. Three pillars were just different aspects of the same elements.
10. Unit Tests
11. Postman Tests