#4: Final Milestone

#4: Final Milestone

Milestone Date

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

Objectives

As this is the final milestone, main objective was to finalize the project and deliver all requested deliverables and code with all promised functionality and features. In general, we are expected to create a product which enables users to create foods, to create restaurants which contains foods, to rate and comment on foods and restaurants, and to ‘taste’ foods. Also, our focus was on the personal assistance functionality for food consumption of our users. Thus, a detailed and examinable consumption history and recommendation based on history and preferences were also included in the product.

Work and Deliverables

• Repository
  • Wiki pages
  • Requirements
  • Design documents
  • User scenarios and mockups
  • User test Cases and Testing results
  • Issues
  • All Code (documented, and with unit tests)
    • Database Dump and script for restoring it on a mysql database.
  • Manuals (user, system)
• Delivery Package
  • Software:
    • Final version of code
    • packaged django app
    • .apk file containing the android solution
    • database dump & configuration file used by code to obtain database path / username / password
  • Generated real or realistic content to jumpstart crowdsourcing beta & recommendation system
    • At least 30 Recipes and related contributions
  • Requirements
  • All Design documents
  • Manuals
  • Software documentation
  • Unit tests
  • User test Cases and Testing results
  • Final presentation (pptx, pdf)
  • Project video
  • Project Plan
  • Meeting notes
  • Milestone reports
  • Final project assessment

Assessment

• In general, most of the main requirements are successfully added to our product on both web and mobile versions. We developed functional and interrelated parts and connected them as requested, and therefore we produced a product with meaningful and complementary functions.
• Although main requirements are met, we could have spend some more time to improve developed functionalities. For instance, we have commenting functionality but comments are not votable.
• We realized with this project that other teams are heavily dependent on backend team and generated API. Therefore, implementation of backend could be prioritised in order to complete it earlier. Also, we could discuss about the design of API calls and decide on the inputs and outputs beforehand and then frontend and mobile team could have implement their parts using that information.
• In general, our final presentation was okay. We showed most of the functionalities we have. Yet, we could fill in between screens instead of a moment of silence. Also, for web presentation there could be another member for controlling the computer instead of speaker himself.
• Our project video really took attention. We were the only group that uses real life scenario and creates real life video. We offer our thanks to Prof. Tunga Güngör for his contribution in the video.
• After taking two courses on software development, we can easily say that software development is not solely writing code. Planning, designing, communication and all other matters are important until completion of the project. In fact, completion of the project is not the end since we would need to maintain our code in a real world project.

Web

• For web part, we used React framework of Javascript. For visual parts, elements from Semantic-UI are used. In general, we followed the good practices about React. Components are used in a hierarchical manner with one-way data flow.
• As one would expect, we have not done many calculations in frontend. Data is get from backend whenever needed. There is just one exception with recommendation section where we use information from one API call to make another API call.
• All pages functions properly without any error or unexpected behaviours. Based on functionality, there is no downsides.
• Create Food page, food page with commenting and rating sections, create restaurant page, restaurant page with commenting and rating, ingredient page, basic search, advanced search, create diet page, diet page, consumption history section, my diets section with adding and removing functionalities, and recommendation section is present in web version.
• Design is kept simple but useful. For instance, multi select search dropdowns were a good addition to the website. We did not use too much color.
• Profile page offers a good range of charts for consumption history of users. While first row is for total consumption data, next rows includes daily comparisons.
• Recommendation system is works based on semantic tags on - at most - 5 most recently consumed food.
• We provide basic search, advanced search, and relatively automated search when diets are used. Search results includes ingredients, foods, and restaurants.
• As we tried to implement all needed requirements, we could not spent enough time to add details, work on animations or to find fancy visual elements. It would not take one’s time to add another field for images to post comment section and display added images or making semantic tags clickable so that it can navigate user to a search result with the given semantic tag. If we could finish requirements one week earlier, we could have look for these simple but effective improvements.
• Although the system does not allow users to create new ingredients as it is not listed in requirements, one can add an ingredient to her consumption history. For instance, if you eat a banana for breakfast, you can directly add it.

Android

• Network state controlling would be better.
• We could take user experience design into consideration more.
• We could have more intuitive page design while tagging food for the user.
• Navigations may be enhanced.
• Our application meets the requirements and is parallel with web except the main focus of the mobile is the regular user not server because aim of the mobile version is to be a personal eating assistant.
• A regular user can add food which is a vital need for an assistant app.
• Semantic tag is used successfully while adding a food and searching a food.
• Our charts are really satisfying because we have charts based on not only macronutrients but also micronutrients. Also, charts shows daily consumption in terms of macro and micronutrients and general consumption in terms of macro and micronutrients in daily manner.
• We offer wide range of micronutrients.
• Calorie calculation via ingredients works good. It takes both macro and micronutrients into consideration. Also, ingredients and their calories are shown for each food.
• Search food is comprehensive. Searching may be done according to semantic tag, allergic or unwanted ingredients, total calories, carbohydrate, protein and fat quantity.
• Search results may be sorted according to ranking and name.
• Recommendation system works successfully and uses semantic tags of eaten foods which are in the consumption history.
• Commenting and rating both server and food is working.
• We are using different units while adding food which is an important point.
• Also, our graphs are user-friendly.