1 / 18

Foodie – Iteration 1

Foodie – Iteration 1. Team 3 Adeeb, 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.

kelly-barnett
Download Presentation

Foodie – Iteration 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Foodie – Iteration 1 Team 3 Adeeb, Arjun, Ayswarya, Karun, and Manisha

  2. 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

  3. 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

  4. ER Diagram

  5. 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 Algorithm

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

  7. 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

  8. …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!

  9. Sneak Peek

  10. Home Screen

  11. Manage Inventory

  12. Add/Delete Items… • Text icons will be changed to pictures. Look out for some attractive icons in the second iteration!

  13. …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

  14. 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

  15. …Continued • Client • Implement recipe search • Connect client to server, read results and show recipes • Implement shopping list • Settings screen

  16. Questions?

More Related