Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

6
Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner

Transcript of Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

Page 1: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

Drunk Dial

Brent Foster

Steven Hollar

James Pendleton

Anish Verma

Chris Wagner

Page 2: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

How it Works (Logically)1. User launches application and sees:

a. Search Boxb. Button for listing categories

2. User types in radix search query or clicks category3. User hits ok when ready4. A list of businesses is populated5. Results are returned to the phone6. User is presented with:

a. Business Nameb. Phone Numberc. Button for additional information (if applicable)

Page 3: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

How it Works (Topologically)

Page 4: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

Requirements

• Cell phone user must be able to quickly dial a desired business with no more than 3 button presses (excluding navigation of favorites).

• Businesses must be able to easily update data via web application.

• User must be able to create & modify a list of favorite businesses.

Page 5: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

Potential Problems

• Retrieving phone location.– GPS? Cell Antennas? Triangulation?– Cell phone types (GSM, GPRS, etc.)?– Legal issues

• Size of entire database.– Machine dependant

• Size of user favorites.– More favorites, more complexity.– ~ 10 favorite categories / places

Page 6: Drunk Dial Brent Foster Steven Hollar James Pendleton Anish Verma Chris Wagner.

Tentative Schedule

• By March 2nd (Initial Requirements and Documentation)– Complete Requirements Spec., Flowchart, and any other

initial documentation.

• By April 6th (Coding and Prototype) – Complete coding and have initial prototype for testing/demo.

• By April 27th (Testing and Finalization)– Have project completely tested and ready for full

demonstration.