#3: Customer Milestone 3

#3: Customer Milestone 3

Milestone Date

24.11.2016

Attendees

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

Kağan Sarı was absent

Objectives

For this milestone, the main objectives were to demonstrate communication between backend and mobile/frontend with the implementation of food page, food add page, and searching/fetching and to start implementation of user oriented features from consumption history part. Updating test plan was also part of the objectives.

Work and Deliverables

We make our demonstration with Android app and web site. Our master branch includes the latest version as of Nov 24. We did not deploy the latest version due to a small issue. Therefore, the demonstration is made on local for frontend. Also, Android demonstration lacked some of the recently added features of backend.

Assessment

• We could not match all required features of this milestone. For web, all required pages were present, but ‘tasted it’ feature and consumption history could not be implemented due to API problems. For mobile, add food page and add food functionality were missing. There was an extra filtering functionality for allergens. We also could not complete the implementation of unit tests, we will implement all necessary unit tests.

• We had a small problem with deploying latest state of the backend, and since android team communicates with API through our deployed url, latest additions to backend could not be used by Android team. For instance, image url field is added for food and ingredient models, yet this field were not available for android.

• There was a small misunderstanding about the development process. The features we should implement is determined by the milestone, yet there were some missing features and as well as some extra features. (Extra features is not unwanted but priority is on the missing features). For instance, add food was missing on mobile, yet we were able to filter allergens which is not required by this milestone. We should demonstrate same features for both web and mobile.

• The milestone presentation was unsuccessful as obviously realized by the audience. Yet, this situation should not cloud our progress in development. We are not behind the plan too much. Still, we need to make a better preparation with a good scenario to sell our product to the customer and the audience.

• We still have not been able to finish creating our database for ingredients. The database which is reached through deployed website should include a large set of ingredients statically. Additionally, we need to add unit conversion for nutritional values.

Actions

• Populate ingredients table in the database. Add unit conversion.
• All endpoints for the API must be implemented. Retrofit implementation should be done as well.
• Complete the pages which are implemented until now. We need to work on the design of the pages as well for the rest of the project.
• All necessary fields for data models should be added, e.g. allergens of a food.
• Need to implement recommendation system according to habits of users.

Next Milestone

Milestone 4

15.12.2016

• Implementation of the project should be completed
• Requirements should be updated according the latest version of the project
• User tests should be done. Test plan should be updated. Unit tests should be done.
• System and user documentations should be done.