Slide 1

Slide 1 text

TRIPTREKKER Presented by: IDB Group #2

Slide 2

Slide 2 text

TOPIC OUTLINE INTRODUCTION CITIES ATTRACTIONS REVIEWS SELF CRITIQUE DIET RIOT CRITIQUE

Slide 3

Slide 3 text

INTRODUCTION

Slide 4

Slide 4 text

INTRODUCTION We provided a list of different cities, attractions, and reviews to help you decide which places you could possibly visit, which attractions interest you the most and reviews to help in choosing good restaurants. Our website lets you plan your next trip in the United States

Slide 5

Slide 5 text

CITIES

Slide 6

Slide 6 text

CITIES Add pagination to show cities Sort filters based on Name, Population, Latitude, and Longitude

Slide 7

Slide 7 text

ATTRACTIONS

Slide 8

Slide 8 text

ATTRACTIONS Pagination to show list of attractions Sort by rating or city name

Slide 9

Slide 9 text

REVIEWS

Slide 10

Slide 10 text

REVIEWS Add pagination to show reviews Search by name and filters based on Name, Population, Latitude, and Longitude

Slide 11

Slide 11 text

THE TEAM

Slide 12

Slide 12 text

ADARSH Phase 1: Creating the static pages and intuitive website navigation + used Bootstrap as a CSS framework Phase 2: Connecting the data from the backend to show in the front end, helped document the APIs in Postman Phase 3: Recreated database in GCP, created a base framework for API in Flask, engineered front-end to implement filtering, searching, and sorting Responsibilities

Slide 13

Slide 13 text

ALARIC Phase 1: Setting up the GitLab Wiki, writing documentation, writing up the technical report Phase 2: Editing the About Page, making the UML class diagram, further contributing to the technical report Phase 3: Editing the presentation, GitLab Wiki, contributing to the front- end Responsibilities

Slide 14

Slide 14 text

AUSTIN Phase 1: Delegating tasks, creating and managing Gitlab repository, accepting merge requests, configuring AWS and NameCheap, deploying front-end code using Amplify Phase 2: Managing Gitlab repository, configuring AWS for backend with CLI, further formatting WIKI Phase 3: Code for connecting Attractions API to Reviews API, managing Gitlab repository, adding documentation and formatting WIKI Responsibilities

Slide 15

Slide 15 text

SHRUTI Phase 1: Designing models and creating data instances using a RESTful API, designing a RESTful API using Postman, technical report Phase 2: web-scraping using RESTful API, designing the DB using MySQL, Flask, Deploying on GCP, unit testing in Python, yUML diagram Phase 3: Code for filtering, searching, sorting, D3 visualizations Responsibilities

Slide 16

Slide 16 text

SULE Phase 1: Creating the static pages and intuitive website navigation + used Bootstrap as a CSS framework Phase 2: Connecting the data from the backend to show in the front end, beautifying the website, and pagination Phase 3: Adding filtering, sorting, and searching bars + creating visualizations of another group's site using D3 Responsibilities

Slide 17

Slide 17 text

WEBSITE DEMO

Slide 18

Slide 18 text

POSTMAN API DEMO

Slide 19

Slide 19 text

GITLAB WIKI

Slide 20

Slide 20 text

Self Critique What did we do well? Able to meet the deliverable deadlines Communicated well asynchronously using Discord What did we learn? Full-Stack web development using front-end and back-end technologies Deploying a website app from scratch Troubleshooting as a team

Slide 21

Slide 21 text

Self Critique (2) What can we do better? Time Management Everyone could have learned both front-end and back-end instead of focusing on the one we knew better What puzzles us? AWS Cloud Deployment Linking pages using React

Slide 22

Slide 22 text

VISUALIZATIONS FROM DIETRIOT

Slide 23

Slide 23 text

Visualizations from DietRiot (1) What did they do well? Relevant / helpful objective Colorful/Attractive UI/UX design Rich, extensive DB What did we learn from their website? The use of technologies such as Material UI / Marshmallow Schemas Easy of Navigation

Slide 24

Slide 24 text

Percentage of Different Diet Types in DB

Slide 25

Slide 25 text

Percentages of the Diet Types Present in Group 1's Data

Slide 26

Slide 26 text

cheap vs. veryHealthy Present in each JSON Recipe file

Slide 27

Slide 27 text

Critique of DietRiot (1) What did they do well? Relevant / helpful objective Colorful/Attractive UI/UX design Rich, extensive DB What did we learn from their website? The use of technologies such as Material UI / Marshmallow Schemas Ease of Navigation between the pages

Slide 28

Slide 28 text

Critique of DietRiot (2) What can they do better? Bidirectional sorting Missing values in database entries What puzzles us about their website? Searching UI - non-intuitive Sorting options are limited