Foodie – Iteration 1

Team 3Adeeb, Arjun, Ayswarya, Karun, and Manisha

What we had planned

• Design server database• Design the querying algorithm• Setup a basic server that returns static data• Connect client to database (high risk)• Implement the high risk screens

Connect client to database

• Created a simple database• Made a connection to the database and read

values• Tried inserting values and creating new tables

as well• Works!• Thanks to - http://developer.android.com/guide/topics/data/data-

storage.html#db

ER Diagram

Category Name (Vegetables)

Ing. ID Ing Name Cuisine 1 (American)Recipe ID

Cuisine 2(Spanish)Recipe ID

1 Carrot X,X,X,X,X,X,X Y,Y,Y,Y,Y,Y,Y

2 Broccoli Z,Z,Z,Z,Z,Z,Z

3 Lettuce

4 Potato

Cuisine 1 (American)

Recipe ID Recipe Details

X,X,X,X,X,X,X ---------------------------------------------------------------------------------

Z,Z,Z,Z,Z,Z,Z ---------------------------------------------------------------------------------

Searching Algorithm

Step 1: Select the ingredients and query (happens from the client) Step 2: Categorize the ingredients ( i.e. veggies, fruits, dairy etc.)Step 3: For each category get the cuisine ids based on the ingredients.Step 4: Repeat Step 3 until ingredients of all selected categories have been queried.

Searching AlgorithmStep 5: Prioritize the recipe ids based on the commonality of ingredients.Step 6: Build and return the recipe list XML

Server

• The basic server has been implemented• It accepts queries and returns static XMLs• To be done:– Connect to the server database and generate the

XMLs • High Risk:– Since the server database will have a decently

large amount of recipes, we have to automate the insertion process

…Continued

– The plan is to write a parser that can do the job for us

– The recipes that we have found are in text files (with a common format). Parser should work!

Sneak Peek

Home Screen

Manage Inventory

Add/Delete Items…

• Text icons will be changed to pictures. Look out for some attractive icons in the second iteration!

…is high risk!

• We figured out that checkboxes work well for selection. As per our design, we have + and – icons instead of checks!

• Found out the way to customize the checkboxes. Will be implemented by second iteration since it needs some custom images

Roadmap for second iteration

• Server– Implement database and querying algorithm

– Write parser – High Risk

– Populate database – Depends on parser. High risk

– Generate XMLs using data from the database

…Continued

• Client– Implement recipe search

– Connect client to server, read results and show recipes

– Implement shopping list

– Settings screen

Questions?