Difference between revisions of "The Line of Least Resistance"

From ESE205 Wiki
Jump to: navigation, search
(Challenges)
(Budget)
Line 23: Line 23:
  
 
== Budget ==
 
== Budget ==
* iPhone (provided by team members)- $0
+
* Device with iOS (provided by team members)- $0
 
* Coding software (provided by school) - $0
 
* Coding software (provided by school) - $0
  

Revision as of 07:26, 4 October 2016

Project Overview

Research has shown that many of the typical methods for queueing customers are incredibly inefficient [1]. Many businesses choose to use reservation systems, for many reasons, such as space limitations in their waiting areas, preparation for large parties, and because the first-come, first-serve process is proven to be inefficient. We aim to create a mobile app that customers of three sample businesses (a tourist attraction, a small restaurant, and a large restaurant) can download and input their name and party size, and receive a time to arrive in order to be attended to. The goal is to minimize delay time/maximize predictability because restaurants, tourist attractions, etc. are meant to be enjoyable, and being given an accurate wait time contributes towards a pleasant experience.

Team Members

  • Devon Essick
  • Andrew Sweren
  • Kjartan Brownell (TA)

Objectives

  • Create a mobile application (iOS) that a potential customer of a business can download and "make a reservation." The app will be simple with an intuitive user interface for those who might not be tech-savvy, and will only require that the user selects which business they want to make a reservation for, and input their name and group size. Once submitted, this data will be analyzed by preset conditions for a certain situation in the app and the next available time will be displayed on the mobile app.
  • Create multiple "sample" situations for the reservations to be based off of (e.g. for one point in time at a restaurant, there are three 2-person tables and one 6-person tables open, but it is estimated in 30 minutes another six-person table will open up, and each person stays for an average of one hour, etc.)
  • Time permitting: extend the program by creating an outside app which includes changeable inputs (total capacity, hours of operation, etc) which can "talk" with the mobile app, to create a more usable app, rather than one based on sample situations, or outline how this would be done in future projects

Challenges

  • Learning how to create a mobile app
  • Coding the system that determines when a customer should arrive
  • Creating an approachable and intuitive mobile app user interface for people with no experience to use
  • Making sure we take into account important inputs about a given business so that the recommendations are realistic (e.g. understanding even if there are 2 two-person slots available at a given time, a group of four will not split up)
  • Taking into account that even if there is a reservation system in place, people are bound to still show up unannounced, and what the impact on the business could be to turn them away
  • Accounting for changes disrupting the way the business operates (e.g. making the business only accessible by reservations could change the type of customers, or making reservations only accessible via mobile app could exclude an older generation)
  • Taking into account that people may make reservations and not show up, which may disrupt the system
  • Making the app reliable (understanding that introducing the app to a business when it does not give accurate times could mean customers do not return)

Budget

  • Device with iOS (provided by team members)- $0
  • Coding software (provided by school) - $0

Total: $0

Gantt Chart

EssickGantt4.png

Design and Solutions

Results