RESTAURANT CHOOSING APPLICATION DESIGN …cpi/old/410/orangf18/images/Quick Eats De… · Work...

Post on 13-Dec-2020

1 views 0 download

Transcript of RESTAURANT CHOOSING APPLICATION DESIGN …cpi/old/410/orangf18/images/Quick Eats De… · Work...

This presentation uses a free template provided by FPPT.comwww.free-power-point-templates.com

QUICK EATSRESTAURANT CHOOSING APPLICATION DESIGN PRESENTATION

CS 410 - Team Orange

November 28th 2018

TABLE OF CONTENTS1. Team Biography

2. Problem Statement

2.1. Dining facts

2.2. Current Process

3. Solution

3.1. Solution Process

3.2. Algorithm

4. Competition

4.1. Matrices

5. Project development

5.1. Major Functional Components

5.2. Work Breakdown Structure5.3. Site map5.4. Database5.5. Algorithm5.6. Risks

• Technical• Customer

6. Prototype

7. Summary

8. References

2CS 410 TEAM ORANGE – November 28th, 2018

TEAM BIOGRAPHY

CS 410 TEAM ORANGE - OCTOBER 7TH, 2018 3

Erick Cordero

Zachery Miller Tavi Sigas

Jacob OglesbyRyan Ha Mariah Archer

Logan Swartz

CS 410 TEAM ORANGE – November 28th, 2018

Work Breakdown Structure

4CS 410 TEAM ORANGE – November 28th, 2018

User Roles● General User - has ownership of profile to participate in

group choosing a restaurant ● Restaurant User - has ownership of restaurant profile and is

allowed to modify restaurant characteristics● Administrator - can view feedback from other users and

assign ownership of a restaurant profile to a restaurant user● Tester - has access to all components of application to

ensure quality testing

5

Site Map

6CS 410 TEAM ORANGE – November 28th, 2018

Restaurant UI

7CS 410 TEAM ORANGE – November 28th, 2018

Customer UI

8CS 410 TEAM ORANGE – November 28th, 2018

Admin UI

9CS 410 TEAM ORANGE – November 28th, 2018

Database Schema

10CS 410 TEAM ORANGE – November 28th, 2018

Database Schema

User Profile•Name

•Id•Date of Birth

•Friend

Restaurant Profile•Name

•Id•Cuisine

•Price

•Attire

•Location

•Overall Rating

•Reservation

•Delivery

•Alcohol

•Outdoor Seating11CS 410 TEAM ORANGE – November 28th, 2018

Algorithm

❑ Account Creation

❑ Authentication

❑ Login

❑ Data Analysis

❑ Notification

❑ Result Matching

12CS 410 TEAM ORANGE – November 28th, 2018

Account Creation

13CS 410 TEAM ORANGE – November 28th, 2018

Authentication

14CS 410 TEAM ORANGE – November 28th, 2018

Login

15CS 410 TEAM ORANGE – November 28th, 2018

Result Matching

16CS 410 TEAM ORANGE – November 28th, 2018

Notification

17CS 410 TEAM ORANGE – November 28th, 2018

Data Analysis

18

Risk Matrix

19CS 410 TEAM ORANGE – November 28th, 2018

T1: Large Scale Software Bugs

20

Description: Software bugs resulting from large scale software development

Mitigation: Support of a technical issue reporting feature.

CS 410 TEAM ORANGE – November 28th, 2018

T2: System Security

21

Description: Sensitive password and geographic information at risk

Mitigation: Require strong passwords. Use best authentication strategies

CS 410 TEAM ORANGE – November 28th, 2018

T3: Disfunction API

22

Description: Changes to geographic API causes dysfunction

Mitigation: Continual testing to keep app up to date

CS 410 TEAM ORANGE – November 28th, 2018

C1: Customer dissatisfaction

Description: Customer not impressed with recommendations

Mitigation: Support of rating system that will prevent the app from recommending restaurant again

23

C2: Incorrect information

24

Description: Restaurant information not being current

Mitigation: Supports features to allow restaurants to manually update information and for customers to report data inconsistencies

CS 410 TEAM ORANGE – November 28th, 2018

C3: Marketability

25

Description: Group dining not a regular occurrence for everyone so there would be a limited appeal to use app

Mitigation: Support a new restaurant recommendation algorithm that can appeal to a wider audience

CS 410 TEAM ORANGE – November 28th, 2018

Prototype

https://xd.adobe.com/view/34fec80f-2f71-4e28-7fdd-f790679363f5-42cf/?fullscreen

26CS 410 TEAM ORANGE – November 28th, 2018

PRESENTATION SUMMARY

❑ Quick Eats provides a fast and efficient way for groups to determine an optimal restaurant

❑ Quicks Eats, with its well defined parameters required along with a solution process, is a feasible project

CS 410 TEAM ORANGE – November 28th, 2018 27

REFERENCES

• [1]:https://www.statista.com/statistics/650054/frequency-of-dining-out-at-fsr-restaurants-us-by-age/• [2]:https://www.7shifts.com/blog/15-restaurant-stats-for-2018/• [3]:https://www.thebalancesmb.com/millennial-restaurant-dining-trends-2888291• [4]:https://www.bls.gov/charts/american-time-use/emp-by-ftpt-job-edu-h.htm• [5]:https://project.wnyc.org/commute-times-us/embed.htm• [6]:https://blogs.voanews.com/all-about-america/2015/05/18/top-10-most-popular-ethnic-cuisines-in-

us/• [7]:http://www.businessmanagementideas.com/management/organisation-management/3-main-factor

s-affecting-group-functions/4889• [8]:https://mlsdev.com/blog/62-the-benefits-of-mobile-apps-for-restaurants

28CS 410 TEAM ORANGE – November 28th, 2018