Kayla’s Status Report for 10/20

What did you personally accomplish this week on the project?

Last week I implemented web scraping by parsing HTML files retrieved from Allrecipes.com, and I worked on the design report with my team.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

The progress is on schedule.

What deliverables do you hope to complete in the next week?

Next week, I aim to set up the database and begin storing the web scraped recipes in the database.

Kayla’s Status Report for 10/5

This week I began implementing the web scraping and continued researching and planning the web app implementation as a whole. The progress is on schedule so far, and next week I will work more on the design report and continue the web scraping implementation.

Here is the repo for the web app code

Team Status Report for 9/28

What are the most significant risks that could jeopardize the success of theproject? How are these risks being managed? What contingency plans are ready?

Latency is a main concern for the project, as latency significantly affects user experience, which is a priority for the project’s success. We are mitigating this risk by hosting the web app on a Raspberry Pi which will communicate with the Raspberry Pi Pico W on the glasses via local network, which is lower latency than communication over the Internet if we were to host in AWS. We are also prototyping with the voice commands and believe they will be within expected latency bounds. Contingency plans are the same in that we will look into larger, more powerful hardware for the glasses.

Were any changes made to the existing design of the system (requirements,block diagram, system spec, etc)? Why was this change necessary, what costsdoes the change incur, and how will these costs be mitigated going forward?

No design changes and no changes to the schedule.

 

Part A (written by Kayla)

As a hands-free cooking assistant, our project is designed to ease the cooking process as well as improve cleanliness in users’ kitchens. By helping to make recipes more readily accessible with clear step-by-step guidance, our project can enable and encourage more people to cook for themselves and their families, which can lead to people having healthier meals, saving money by eating out less, and living a more sustainable and fulfilling lifestyle overall. Additionally, the hands-free nature of the product helps to reduce contamination between foods, handheld devices, and potentially other surfaces maintaining a cleaner workspace and cooking environment. Because the product is targeted mainly toward home or amateur cooks, these areas are often peoples’ own kitchens in their everyday living spaces, so improved cleanliness in these areas can also be beneficial for peoples’ overall health.

Part B: (written by Alena)

“Hey CHEF!” addresses a growing societal trend of convenience, multitasking, and technological integration in daily life. As we increasingly adopt busy lifestyles, the ability to prepare meals efficiently while minimizing the need for manual interaction with devices can enhance time management and also reduce chaos in the kitchen. Additionally, the product can cater to a range of cultural cuisines and dietary preferences, encouraging inclusivity by allowing users from various backgrounds to explore different recipes and share them socially. By recommending recipes based on what users already have, it encourages resourcefulness and economic mindfulness, while also exposing users to new recipes that they may not have heard of.

Part C: (written by Michelle)

We believe that “Hey CHEF!” will be a product desired by consumers around the world. For as long as the need for food exists, cooking will too. Hence, tools that facilitate cook/prep time will always be in demand. “Hey CHEF!” aims to utilize the desire to cook with the desire to make it an easier, simplified process. To make a product that has economic potential, we aim to make the glasses lightweight, cost-friendly, and modular, making production on a larger scale simple. The glasses will reach a large audience by eventually allowing for recipe addition, and the easy-to-use interface will allow a variety of people of different skill levels to use our product.

Team Status Report for 9/21

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

  • The biggest risk that could jeopardize the success of our project is the unknown latency we may experience between sub-modules of our design. We will mitigate these risks by researching multiple options for the best way to communicate from our Raspberry Pi Pico W to our web server, and the best ways to communicate within the web server. In the event that we cannot find a suitable solution, we may look into better hardware while sacrificing some size/weight constraints.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

  • There were no changes made to the existing design of the system.

Kayla’s Status Report for 9/21

This week I created mockups for the web app UI using the Figma design tool as well as researched implementation options and their details for the different components of the web app, including the database, hosting, and web scraping. My progress is on schedule with the tasks laid out in the Gantt chart, and next week I will work on replicating the UI mockups and setting up AWS hosting infrastructure for the web app, with frontend code as a deliverable.

UI mockups

Web app research notes