#2: Customer Milestone 2

#2: Customer Milestone 2

Milestone Date

10.11.2016

Attendees

• Enes Özipek
• Gözde Berk
• Yiğit Özgümüş
• Kağan Sarı
• Erkam Uyanık
• Arda Yörük
• Murat Sinan Açlan

Berke Can Gürer was absent

Objectives

The main objective of this milestone was to make a demo on web and (not necessarily) mobile with basic user functionalities, searching (and fetching) foods and ingredients, add Food page, and food page. The aim was to demonstrate that we are able to connect our database and backend with frontend and mobile.

Work and Deliverables

We make our demonstration with functional frontend pages. Our master branch includes the latest version as of Nov 10. Also, we deployed current version on http://52.208.59.70/

There is a little exception with add food functionality being on frontend branch. We showed that functionality on localhost.

Assessment

• Structure of the project and current infrastructure with REST API is appreciated by the customer. Having a deployed version was also a good aspect.

• In our demo, we were able to demonstrate the functionality and connection with API. The main aim was this. Yet, food page was not present, and other pages were not completely done. We need to complete these until the next milestone.

• We mentioned that we will have local data for ingredients and user can select ingredients from that list. Currently the source we will use does not include any conversion table, e.g. user cannot select 1 teaspoon of olive oil. We are asked to add such a property in oncoming days (not necessarily on the next milestone).

• Although for this milestone we are not strictly asked to make a demonstration both on website and mobile, mobile version shall be present for next milestone.

• Continuous updating is a good practice for software development. We need to track our progress all the time and current progress should be easily noticeable. For this, issue tracking is very crucial. We need to actively use issue tracking system continuously.

Actions

• Populate ingredients data.
• Implement food page.
• Complete search food page. Listed items should be clickable and should navigate user to the selected food page.
• Complete add food page.

Next Milestone

Milestone 3

24.11.2016

• Every page should be on both website and mobile version
• Add food functionality should be done with added design.
• There should be profile section with consumption history. Consumption history should include a simple list of previously consumed foods.
• User shall be able to navigate to food pages from search results.
• Test plan should be updated. We are expected to implement unit tests for necessary parts.