[A#10, P1]

(1) Evaluate your test results.

What method(s) did you use to evaluate the results of your usability tests?

We created this based on the System Usability Scale developed by John Brookee at the Digital Equipment Corporation, but had not the time to use it during the tests.

We used the method introduced in Assignment #6 for this evaluation too because we received very good feedback after presenting it to our other fellow students and we believe it fits to the other methods given in this assignment.

How did you evaluate the results?

After filling in the formulas provided we expanded it with our difficulty estimation and with both we created the following table to summarize the results:

TaskNotesTake-Away
Log-inNo option to log-in without google or social media.Add more anonymous way or even without log-in.
Figure out what is the last recipe you cooked
Add ingredientsIngredients doesn’t have unit. This confused the user since it is not consistent with other ingredients.

Additional after adding the users are confused why the home-screen is the next one and not the fill-pot-screen.
No drop-down when no unit.

Test person should stay in FillPotLayout when adding an ingredient.

App bar name should be Fill Pot and not My Pot when searching for ingredients
Access potNo indication that the pot is clickable.Add tutorial.
Not-clickable with grey color could work too.
Get recipeAdd more content
Add recipe to historyTest person literally said that he would never click the „Add to history“ button after cooking.He want to use the smartphone for something different after cooking.We will describe a better way to motivate the click on the „Add history“ button in the next block(see below).

Get recipe with too little ingredientsThe provided explanation text is very helpful when no recipe suggestions available
Log-outMake it more difficult to log-out, because we want to keep users as long as possibleLogout should be just on the home-screen not in every screen and also with a pop-up.

What did you learn from the testing?

We want to improve a general issue which is the size of the fonts which might be a bit too small, especially for seniors. We will now mention one part of our design that was continuously discussed in every single task and we think it is important to go into detail about the ideas we can share after this semester regarding this.

What are your main takeaways?

The main general takeaway from usability testing is the idea that the developer/designer perspective might be very different from the user’s expectation from the app. Concretely, we could improve our prototype through test evaluations. Besides, the tests drew our attention to a serious usability problem. Namely, the last step of the recipe preparation contains a button named „Add to History“ that has to be clicked for the application logic to work. What we noticed during tests is that all test participants tend to think that the goal is achieved when they reach the recipe preparation description which is not the case. The „Add to History“ button is crucial since it doesn’t only add the recipe to history if the user wants to access it later but it updates the ingredients pot by removing the used ingredients. The solution that we came out with is to always pop the confirmation alert dialog whenever the user tries to exit the application or go to the main screen. If the user isn’t cooperative and chooses to forcefully exit the application, notifications should be pushed to remind the user that he has to update his ingredients pot. We also want to mention in the pop-up that we will empty the pot and add to history every looked up recipe because we have „favorites“ as a list controlled just by the user.

(2) Project description

Mouadh Khlifi – Master student on Computer Science at the FU Berlin

Christian Zygmunt Jeschke – Master student on CS Education at the FU Berlin

Take-away or food delivery is convenient, but ordered food mostly comes with too much plastic. Moreover, leftovers have to be thrown away. To protect the environment and save food we want to make it easier to find out which meal you can do with leftovers. From our own experience, we know: Even if we have ingredients, sometimes we decide not to cook because we are just too hungry and want to save time. We designed and implemented the app Hello Fridge to solve this issue. The app allows searching for recipes just by inserting ingredients. We expect that our users will more likely open their fridge (and check with our app if they can create something novel by themselves) before ordering food. We used proto.io for the first iterations and now the Flutter Framework from Google for the development. During the methodology-oriented design process, we made multiple types of user tests. On one hand to conceive a concrete idea of what the end product should look like. On the other hand, to detect and solve usability ambiguities that a user can encounter.

Our most important lesson with the focus on HCI was this design decision since we had to change it a lot

Test the app in you browser here (preferabily on your phone)

Hello Fridge App

Please ask us for access to the source code

Who did what?

We had a strong pair work this week but we can mention that Mouadh was more focused on the administration of the web app while Christian did that for the evaluation.

What have we learned?

We identified that Meta Strategies like the consideration of multiple perspectives is a very important and difficult task. We need to keep this in mind during the whole process because once we forget it we are developing just for ourselves and have no chance to sell to the user.

What went well?

We managed better to find a good timing here.

What do we want to improve?

We need to find out how to work in the future.

[A#9, P1] Preparation of a summative evaluation

(1) Improve your high-fidelity prototype

In the heuristic evaluation we received 4 violations while 1 of them reached the 4th level of severity, two reached the 3rd level and one is on the lowest. Nevertheless, we decided not to pick the highest level available because it was, we believe, not our initial design approach. Since changing this design will make a fundamental change on our problem to solve, we do not want to follow this feedback and rather focus on the other. The problem is described „To look at the preparation you need to press the button on the bottom right corner. To go back to the ingredients, you need to click on the arrow in the upper left corner.“ A bit special is that we received two ideas for „Recommendation:“ where we skip „a) Ingredients + preparation on one page with scrolling“ and going as our solution „b) Divide both parts and store the preparation step (where you were) when you switch to ingredient list. Switching to back to ingredient list should be with the same button as ‘Showing preparation’“. We expect that this will change one of the first interaction problems which is also the most intense one because we discussed on every iteration, namely, how should the user interact with our app after cooking.

We implemented our app here https://mouadhkh.github.io and we followed the desciption above to know the usability issues and features and here is the excact list:

implemented fillPotLayout, fillPotlayout action still missing

implement mainLayout, theme not working, log out button missing,no links for buttons and recipes are not clickable at all

-fixed TabBar and restyled

add recipes suggestions

horizontal slider for recipes

add new recipe layout

add layouts for a single recipe

add preparation implementation for recipe

add alertDialog for confirmation

log out button on all screens

(2) Preparation for a summative evaluation

Even if on the tests at the 6th assignment we had no problems, we want to make some improvements because of the heuristic evaluation where we had to improve our tasks from the #6 assignments. Especially the task amount is higher now because our current prototype allows more and therefore, we have more details here.

In the second attempt the task has been specified by this HCI seminar and it was not necessary to add them like in the #6 assignments. Same as the other group we hoped that the tasks presented are a good starting point to understand the prototype without our own interruption.

Skript

The roles: The observer is taking notes while the facilitator guides the interview. All participants are affected by the solution that HelloFridge offers. Since the target group is living in our area we decided to provide the script in German:

1.Hinweis für den User
Wir testen die App, nicht dich! Fragen bitte gerne stellen, ich kann aber nicht versprechen, alle Fragen direkt zu beantworten! Bitte laut denken

2- Erklärung des Kontexts
Essen bestellen und Fast Food ist bequem und schnell, aber es schadet der Umwelt. Um diese zu schützen erlaubt unsere App HelloFridge mit einer Zutatenliste passende Rezepte zu finden. So können für die Essensreste Zuhause neue Gerichte gefunden werden.

3-Fragebogen
Alter ?
Erfahrung mit dem Umgang mit Smartphones ?
Regelmäßiges Nutzen von Mobile Food Apps ?

4-Szenario
Du hast Hunger. Wie immer, gehst du zum Kühlschrank und schaust ob du etwas kochen kannst vor allem damit du deine Essensreste verkochst. Du hast zwar einige Zutaten, aber ein Rezept fällt dir nicht direkt ein. Deshalb nimmst du dein Smartphone, suchst nach einer Rezepte App und klickst auf das innovative Hello Fridge.

5-Aufgaben
Sollten zu einem Zeitpunkt Verständnisfragen zu den Aufgaben auftreten, bitten wir dich, diese uns gegenüber zu äußern. Wir stehen dir auch gerne zur Seite falls mal etwas schiefgelaufen ist.

Log Dich ein
Was ist das letzte Rezept das gekocht wurde ?
Wir wollen nun dieses Rezept nur mithilfe der Rezeptliste finden.
Füge dazu eine normale Einkaufsportion von Hänchenbrust, Reis, Tomaten Olivenöl und Gewürze hinzu.
Lass dir von der App ein Rezept finden.
Bestätige dass du das vorgeschlagene Rezept gekocht hast.
Finde heraus welche Zutaten du noch hast nachdem du gekocht hast.
Füge noch ein beliebige Zutat zum Hello Fridge Topf hinzu und versuche nach einem Rezept zu suchen. (Du wirst kein Rezpt sehen können)
Log Dich aus

6-Abschließende Fragen
Welche Vor- und Nachteile siehst du grundsätzliche bei der Rezeptesuchen-Funktion der Hello Fridge App ?

7- Abschluss
Hast du weitere Fragen oder Anmerkungen ?

Which standardized questionnaire did you choose and why?

After talking about it with the guests, we used the time for that.

Who did what?

We splited this week the tasks in detail but we have both worked on the programming and writing.

What have we learned?

We learned especially how to finish a project with the SDK Flutter and interaction design.

What went well?

We are very happy with our final result.

What do we want to improve?

We try to work on our time management and to find a balance between programming and Human-Centered Design.

A/B testing

Also known as simple controlled experiment, bucket testing, controlled online experiments or split-run testing. In an experiment like this we have 2 groups and in the simplest version just one variant is different. That`s an user experience research methodology.
In the last years large companies started to use this like LinkedIn, Facebook, Google, Microsoft and Instagram.
Multivariate or multinomial testing is the version where more than 2 versions get tested together in parallel.
Observational, quasi-experimental or other non-experimental situations are unvalid for simple A/B tests.
Two-sample hypothesis tests are appropriate for this.

Each group get’s a different software

[A#8, P1] Heuristic Evaluation

Continue to improve your high-fidelity prototype

We finished our onboarding on Flutter and started to design concrete Screens. We already have reusable Widgets that will accelerate the development process but some Screens are still work in progress. The planning was made before having a concrete idea of how things should be done in Flutter so we will use the time of preparing „Dummy Data“(the plan was to store data in JSON files) to finish the screens since we already created dummy data inside Dart objects.

Conduct the first and second phases of a heuristic evaluation

Phase 1: Preparation

We have exchanged Tasks with Group8. We prepared the tasks we received as starting point for the evaluation

Tasks for the evaluators

-In der echten App fängt der User mit 0 Zutaten an . Zur Testvereinfachung, wurden schon Zutaten hinzugefügt.
-Finde heraus welche Zutaten du schon hast?
-Was ist das letzte Rezept das gekocht wurde ?
-Wie wurdest du einen Rezeptvorschlag bekommen ?
-Wähle das Vorgeschlagene Rezept -Bestätige dass du das vorgeschlagene Rezept gekocht hast
-Was ist das letzte Rezept das du gekocht hast ?
-Welche zutaten hast du übrig nachdem du gekocht hast ?
-Füge 2 Baguette zu HelloFridge Topf

We used the following form template for the evaluation process

https://docs.google.com/forms/d/1CtM835Rphnc312GX8F15cvzG1dIpIFrA3T9vDYXlV7o/edit

Screenshots

Mouadh used Monosnap to easily take screenshots and copy the link. Christian uploaded the images in Google drive and posted the links.

Phase 2: Evaluation

The given resource(https://www.nngroup.com/articles/ten-usability-heuristics/) helped us to have the Nielsen’s heuristics listed in a compact page where we can easily extract the violated heuristics from the prototype.

Summary of our evaluation processes

The tasks that we received presented a good starting point to understand the prototype. We decided to not play with the prototype until we accomplish all the tasks in order to keep the mind of a completely fresh user.
We took one hour to separately evaluate the prototype using the mentioned Google Doc. Concretely, each team member followed the tasks and added the detected violation.
Parallelly, we wrote down some unclarities that we couldn’t clearly associate with heuristics violations. Afterwards, we discussed the extracted violations and discussed the ambiguous ones in order to classify them.

Who did what?

We prepared the tasks together and then met another day to solve the assignment questions. We prepared the evaluation together then evaluated the prototype individually. Afterwards we met again to discuss our evaluation results.

What have we learned?

Nielsen’s Heuristics were eye openers, not only as we evaluated the other group’s prototype but also made us conscious about the violations that our prototype has.

What went well?

Communication was smooth. We are organized since we have fixed times reserved for solving the assignment.

What do we want to improve?

We are happy with our process and results.

[A#7 P1] Starting High Fidelity Prototyping (First Iteration)

What framework or tools are you going to use? Why?

We decided to use Flutter because it offers an intuitive approach to building user interfaces. It provides higher productivity than implementing the application natively and thus saves us time. Moreover, its artefact is cross-platform what means that our codebase will be the same for multiple platforms(Android, ios…).
We hesitated between Flutter and React Native. Since Mouadh had some experience with the latter, we decided to use the Hello Fridge project as an opportunity to learn new promising technologies.

List your functional and non-functional requirements (features) you are planning to include in your High-Fidelity Prototype.

Sorted by priority in descending order.

Functional:

  • User should be able to add ingredients with limited possible ingredients at this stage
  • User should at least get one recipe suggestion from his ingredients
  • Already cooked meals should be automatically saved in the history menu
  • User should be able to manually add meals to favourites
  • User should be able to sign in with social media

Non functional: Database access should be done in reasonable time

We now have 6 weeks left for our projects. Produce a detailed timeline (e.g., a Gantt-chart or similar) of jobs that need to be done and milestones that need to be reached starting from today.

What menu type did you choose and why?

Our menu type is not explicitly in the visible area since we decided that in our design we want to focus the route on the functionality and not the other way around.

Which UI controls are appropriate for your application and why?

In general we are using buttons which describes the functionality in the button’s label. One special case is the pot in the home screen. We used this analogy for our ingredients stack. Even if practically the pot is also just a button we have designed this element as a support for the understanding of our functional requirements. An animation that looks like the pot is opened or closed will help in this mindset.

Which design patterns are suitable for your application and which ones have you implemented or used? Why?

Since it’s important for our app to break down single goals into smaller one we want to use the wizard design pattern. „The task of inputting data into the system is parted into multiple steps. Each step is presented to the user one at a time. The user should be presented with information about the steps that exist, progress through the process and which steps are completed.“ http://ui-patterns.com/patterns/Wizard We will use it especially when the recipe is presented where we have some options like adding this recipe to the favorites or at the ende when the user can click on „Already coocked“. With the design pattern wizard we have a previous and a next Logic and we have that during this preparations steps. It`s also very good to show a step by step process.

Who did what?

In this week we have clarified our approach before the start of the first week and had in both following weeks a very separate to-do list.

What did we learn?

We learned Flutter and CI basics but we talked a lot about our priorities too.

What went well?

Everything.

What do we want to improve?

Despite having a clear idea of what the product should look like, we experienced some uncertainties since we are new to the technology and we are still in the explorative prototyping phase.

[A#6, P1] Paper prototyping and usability testing

In our usability tests, the average time was 20 minutes. We did it in alternation so that each of us can experience the available roles at least once. The roles: The observer is taking notes while the facilitator guides the interview. All participants are affected by the solution that HelloFridge offers. Since the target group is living in our area we decided to provide the script in German:

1-Hinweis für den User

Wir testen die App, nicht dich! Fragen bitte gerne stellen, ich kann aber nicht versprechen, alle Fragen direkt zu beantworten! Bitte laut denken

2- Erklärung des Kontexts

Essen bestellen und Fast Food ist bequem und schnell, aber es schadet der Umwelt. Um diese zu schützen erlaubt unsere App HelloFridge mit einer Zutatenliste passende Rezepte zu finden. So können für die Essensreste Zuhause neue Gerichte gefunden werden.

3-Fragebogen

Alter ?
Erfahrung mit dem Umgang von Smartphones ?
regelmäßiges Nutzen von Mobile Apps ?
Schon mal ein Food-App benutzt ? Welches ? Worum ging es ?

4-Szenario
Stell dir vor du bist zu hause und überlegst ob du etwas kochen sollst oder etwas
bestellen. Du öffnest dein Handy um eine Lieferdienst App zu nutzen, aber plötzlich siehst du das HelloFridge Logo und entscheidest dich der tollen App eine Chance zu geben.

5-Aufgaben

Sollten zu einem Zeitpunkt Verständnisfragen zu den Aufgaben auftreten, bitten wir dich, diese uns gegenüber zu äußern.
Wir stehen dir auch gerne zur Seite falls mal etwas schiefgelaufen ist.

Log dich ein.
Beschreibe was du siehst und deinen ersten Eindruck
Finde heraus welche Zutaten du schon hast.
Du hast bereit Hänchenbrust, Reis, Olivenöl und Gewürze. Du öffnest die App. Unter der Annahme dass diese Zutaten bereit hinzugefügt wurden, wie wurdest du einen Rezeptvorschlag bekommen ?
Was ist die letzte Rezept die du gekocht hast ?
Welche zutaten hast du übrig nachdem du gekocht hast ?
Versuch den Topf mit Zutaten zu füllen

6- Abschließende Fragen

Welche Vor- und Nachteile siehst du grundsätzliche bei der Rezeptesuchen-Funktion der Hello Fridge App ?
Was war für dich nicht intuitiv bzw schwierig zu interpretieren?

7- Abschluss

Hast du weitere Fragen oder Anmerkungen ?

What method did you use to evaluate the results of your usability tests? How did you evaluate the results?

We tried to be as passive as possible during the usability tests to not influence the test persons interaction with the user interface.

While writing the script we tried to have small tasks which can be rated separately. The difficulty of each task will be rated by us according to the performance of the user in order to identify the ambiguous and not intuitive tasks.

Since we provided as little help as necessary to our test user we received rich feedbacks and interesting questions. Those led to greater discussions because we felt that only with additional prompts the thoughts will be verbalized by the users.

What did you learn from the testing? What are your main takeaways?

We noticed that our interpretation of the user interface does not always align with the users interpretation. On various occasions, the user said that „I think the app expects me to …“ which is a clear sign of multiple uncertainties on the users side.

For the reasons stated above we decided to make some changes on our prototype:

It is not possible to design all the possible use cases that`s why we started with an already filled pot (5 ingredients). The user had some confusion with the first step of our app because it was not clear that the empty pot use case is not tested here.
When the pot is empty the Get Recipe button should be disabled. The favourite button was not clear for all our users „He seems to be out of place“. After some discussions, we decided to change the approach and we will create a tabulation for the Favorites next to Already Cooked ones, which we will also change to a tabulation.

One situation that led to a greater discussion was How the user can mark a recipe as Already Cooked? In our prototype when the user is in the recipe preparation screen we have an Already Cooked? button but clicking this button was mentioned as not intuitive since the common approach is to click on the Back button (<-) . The functionality of the Already Cooked button is very important, especially for refreshing the ingredients list in the pot. This functionality was not communicated clearly to the user through the app. Again after some discussions, we decided to adopt a swiping system where the user can swipe through the recipes preparation steps. The last step asks the user to manually confirm Already Cooked? either by a simple button click or by taking a photo of the cooked meal. But the last-mentioned functionality is nice to have.

Some additional points we discovered:

we want to include drag and drop menues when choosing the ingredients

settings for multiple languages

the touch buttons have to be as big as the pictures

in the recipe preparation screen we want to see the name just once

the recipes at Already Cooked? need a star when they are also in the favourites

An open question is how long our UX prototype has to be alive.

Who did what?

The usability test script was written collectively. During the usability test, we alternated between the Moderator and Observer roles.

What did we learn?

The Usability test brought more inputs than we expected. Moreover, we understood the real value of a usability Test. We have learnt that the product looks different from the user perspective. A big usability flaw wasn’t noticed by us as we designed the prototype so it confused our test persons.

What went well?

The usability tests went well.The discussion was rich and fun.We could draw many conclusions and take some important design decisions.
We are happy that we are reserving a whole day for the collaboration.It is a system that we implemented since the beginning but wz started to see the benefits now since it became a habit for us.

What do we want to improve?

We have noticed nothing this week. The tests went well and the assignment itself was rewarding since we have learned and applied new ideas.

[A#5, P1]

Summarize the feedback you received regarding your storyboard.

During our last virtual classroom session, we received a lot of software and especially programming tips from various other students and because of this we have a good idea of our coding challenges in the future of our project.
One of the hints was that the account is most likely the most difficult part since it needs access to our own database in every interaction and besides that, we must take care of all the necessary security that comes with an account.
The general feedback was good, and we heard that the artefacts created had a good quality and that the content suites the initial presentation/pitch.
An improvement can be done with a combination of the sketches with the storyboard.
While all teams accepted our Moodboard as a potential solution for the assignment, we found that it was difficult to explain our project through our Moodboard. That’s why we are interested in more theory behind this presentation method.
One sentence where all feedbacking students gave positive feedback was „Even if HTA provides a better understanding which subtask are included, in our current project state we mostly need a better overall understanding of the system. From the choices given BPMN is the best to achieve this because it delivers a clear visualization of the whole lifecycle.“ and it seems all of them came to a similar conclusion.
We want to include the pot as a metaphor while picking the ingredients.

Develop an interactive paper prototype.

https://share.proto.io/X7US1C/

After a group discussion it was clear that the most efficient way of a Paper Prototype is making it completely in proto.io. We are going for that since we are skilled here and the argument for using pen and paper was just the lower time and effort it takes. Therefore, we do have the opposite opinion: a computer made prototype is more efficient for us. Additionally, an interactivity is required which is also an argument for proto.io because this tool makes this very easy.

The prototyping process was straightforward and productive with some good thoughts regarding how intuitive it is.

The use case and/or model (task analysis from last assignment) this prototype relates to is mostly the BPNM.

With the storyboard created last week we can make a good software that solves the showed situation.

We have a pretty good feeling in the group since all our discussions are constructive. The technology knowledge is on a good level for the challenges.

At this point, we think it is good to mention that we had some confusion regarding the definition of a Paper Prototype since we understood with the lectures definition that the interactivity is just played (while this additional means it is not possible to distinguish it`s to a „Wizard of Oz“ prototype) but we remember from the last session that we need interaction without a playing computer.

https://www.designevo.com/apps/logo/?name=green-chef-cap-and-white-tableware (icon source)

Design rationales

process-oriented gIBIS
structure-oriented general QOS

Who did what?

Mouadh has strong knowledge of the prototype tool so he took the lead. The learning opportunity was used by Christian and since learning is more focused when you write while doing it this was a Win-Win situation. We are again happy afterwards that we did it this way.

What did we learn?

While Christian achieved a basic understanding in the disciplines required Mouadh was concentrated on the requirements implementation. The proto.io tool is very cool, process and structure is an interesting perspective.

What went well?

As mentioned in the second question of this assignment we are happy that we can do a lot of collaboration and this is always oriented for the good of our product. Therefore we have a lot of respect for the other person`s opinion.

What do we want to improve?

We had some struggles this week with the platforms but everything is clear at the end of the tasks. This was mostly because of an initial wrong thought regarding where we can find the correct answer.

[A#4, P1] Ideation and Storyboard

Formulate a problem and hypothesis statement and document it.

Jorg needs a way to easily generate recipes from a set of ingredients because he always has leftovers.

We will know this to be true when we see: that Jorg always get a list of recipe suggestions from his ingredients selection.

We believe that by creating a user friendly interface for ingredients selection and clear visualization of the resulting recipe list for Jorg, we will achieve having less leftovers and ordering 50% less food.

Conceptual models for task analysis

We hesitated between BPMN and HTA, but we decided to go for the task flow with BPNM because we estimate that this choice will help us the most analysing our user`s tasks. Even if HTA provides a better understanding which subtask are included, in our current project state we mostly need a better overall understanding of the system. From the choices given BPMN is the best to achieve this because it delivers a clear visualization of the whole lifecycle.

Find inspirations, analogies, and create a moodboard.

Picture sources from left to right: 3 screenshots, pot, fridgepix, no-fast-food sign, tender, supercook.com

Create individual sketches and share your sketches with your team.

With the made BPNM and the moodboard we are able to get a better insight for the processes. Following this insights we created sketches how our app will look like.

Condense your results from the previous step into a storyboard.

Who did what?

We decided this week that the assignments need a very strong interaction, discussion and collaboration. Therefore, we have not spent time on separation and had a long teamworktime. We are happy afterwards that we did it this way.

What did we learn?

All the methods used besides BPNM are new for us. This means we had a lot of hands-on training this time. We have also discovered that the old tool like Miro can be used in a new way and have functionalities previously unknown for us.

What went well?

The teamwork was taff but we think that our time was really productive and efficient: We have a good communication basis and we have a strong common vocabulary in the domain. It was also easy to establish the meeting appointment.

What do we want to improve?

It is very difficult to have a routine during weeks where you are in distance learning because you need to schedule learn time and additional even plan time. We discovered this habit in this week because we still have no fixed day and that´s not the best but still okay.

[A#3, P1] Requirements

Analyze your (qualitative) data using affinity diagramming

We did the analysis firstly with the interview… (in Miro)
and afterwards added some insights from the application.

Derive a primary persona from your data-gathering insights

The Photo is made with a GAN. The document is made in xtensio with their provided template.

Create scenarios

Scenario 1
Jorg does the groceries each Saturday after he finishes doing the chores. Jorg is used to coming back home from work exhausted and not in the mood to cook especially that he used most of the ingredients he has bought last Saturday. For this exact reason, Jorg had the habit to eat outside or order food on Thursdays and Fridays.
After he installed HelloFridge, Jorg rushes to her kitchen every timeshe arrives home from work, opens his fridge and his kitchen closet, and starts creating an ingredients list in the HelloFridge application. After finalizing the list and clicking the confirmation button, Jorg will see a variety of recipe suggestions that he can choose from.
When
Jorg does the groceries each Saturday after he finishes doing the chores. Jorg is used to coming back home from work exhausted and not in the mood to cook especially that he used most of the ingredients he has bought last Saturday. For this exact reason, Jorg had the habit to eat outside or order food on Thursdays and Fridays.
After he installed HelloFridge, Jorg rushes to his kitchen every time he arrives home from work, opens his fridge and his kitchen closet, and starts creating an ingredients list in the HelloFridge application. After finalizing the list and clicking the confirmation button, Jorg should see a variety of recipe suggestions that he can choose from.
Where
Jorg does the groceries each Saturday after he finishes doing the chores. Jorg is used to coming back home from work exhausted and not in the mood to cook especially that he used most of the ingredients he has bought last Saturday. For this exact reason, Jorg had the habit to eat outside or order food on Thursdays and Fridays.
After he installed HelloFridge, Jorg rushes to her kitchen every time he arrives home from work, opens his fridge and his kitchen closet, and starts creating an ingredients list in the HelloFridge application. After finalizing the list and clicking the confirmation button, Jorg should see a variety of recipe suggestions that he can choose from.

Scenario 2
Jorg does his weekly groceries on Fridays on his way back from work. Directly after arriving, Jorg starts arranging the food products in the fridge and kitchen closet. During this process, Jorg opens HelloFridge to create an ingredient list. After finishing, he should get a list of possible recipes as result. By selecting a recipe, Jorg can add the recipe to favorites or plan it in the calendar.
Each time Jorg confirms a recipe to tell HelloFridge that he has cooked it, the ingredients can be subtracted from the current ingredients list and new suggestions should get generated from the updated ingredients list.
When
Jorg does his weekly groceries on Fridays on his way back from work. Directly after arriving, Jorg starts arranging the food products in the fridge and kitchen closet. During this process, Jorg opens HelloFridge to create an ingredient list. After finishing, he should get a list of possible recipes as result. By selecting a recipe, Jorg can add the recipe to favorites or plan it in the calendar.
Each time Jorg confirms a recipe to tell HelloFridge that he has cooked it, the ingredients can be subtracted from the current ingredients list and new suggestions should get generated from the updated ingredients list.
Where
Jorg does his weekly groceries on Fridays on his way back from work. Directly after arriving, Jorg starts arranging the food products in the fridge and kitchen closet. During this process, Jorg opens HelloFridge to create an ingredient list. After finishing, he should get a list of possible recipes as result. By selecting a recipe, Jorg can add the recipe to favorites or plan it in the calendar.
Each time Jorg confirms a recipe to tell HelloFridge that he has cooked it, the ingredients can be subtracted from the current ingredients list and new suggestions should get generated from the updated ingredients list.

Model two Use Cases with UML

Simple Use-Case of using HelloFridge when having Leftovers
Using HelloFridge directly after buying food products

Who did what?

In this week we worked close together since the tasks required a lot of comunication and discussions. It’s difficult to identify the real difference.

What did we learn?

We discovered the new methods which we had first in the live session. We also practiced the skills which we got introduced during „Software Engineering“.

What went well?

Our communication is very good. We have a good common language regarding all our project tasks and it’s easy to share opinios, even during online learning.

What do we want to improve?

In the next week we will try to keep a better work book since our current Miro workbook is filled with the challenges from all the weeks before and that’s not clear anymore.

[A#2, P1] Data

For our in-depth interview, we created the following questions while the goal was to become aware of the meal ideation process

1- How do you plan your meals?
2- When do you plan your meals?
3- What do you think about fast food?

4- Do you cook regularly?
Yes => Where are your recipes coming from?
No => Name the reasons
5- What do you think about a meal planner?
We are developing an app which is recommending you recipes for food that you do not know how to use. It is new because your only input are the ingredients that you want to use for it; and allergies.
6- On a scale from 0 to 10, how willing are you to download an app which helps you with the cooking?
7- If you had such a mobile application, would you use it for your daily eating habits or occasionally?
8- Which ingredients generally remains when you must go for groceries again?
9- What colour intuitively represents food in your opinion?
10- What form of recipe is appealing to you the most?
A- Text
B- Pictures
C- Video
11- If you think about your social circle, to how many acquaintances would you recommend such an app?
12- How would you like such an application to be called?

In our project, it’s best to analyze existing software

1.Document your method and the type of data you are gathering.

During our research, we become inspired by a good working project that we discovered. Our analysis is done with the following steps: 1. Try out the use case written in the previous blog post in the app 2. Protocol during the process all thoughts and become aware of other (potentially for us interesting) use cases 3. Describe the other use cases.

2.Store your collected data.

Supercook was created by Assaf Rozenblatt an it`s an responsive website, Android and iOS App.

„Supercook wants to make life easier for everyone who cooks at home! Our mission is to enable smarter, quicker decisions about what recipes to make and what ingredients to use using advanced technology and all the recipe content on the web. Based in New York, Supercook has a distinct focus on solving the practical problems of modern home cooks: how to waste less food, how to use up perishable or seasonal ingredients and how to keep track of everything in the kitchen“ supercook.com can be easily found with a search engine, just by typing in the word supercook. You will find it on the the top. Similar in the Appstores.

You can see a tutorial screen with the information „Speak to add ingredients Adding ingredients is easy Open your fridge, tap the mic icon, say what you have“ and also „Every ingredient you add unlocks more recipes“, „vegan lasagna without tomato“ and „Search over 1 million recipes“. You can click on „Skip“ or „Get Started“ while both buttons bring you to the same start screen.

On this screen, you can see pretty clearly that it`s time to add ingredients here. You have 3 possibilities to do that. At the top of the screen, you can write in a search bar, after writing the first character you will see the available ingredients. The second option is in the middle of the site and it is a list of ingredients (sorted in meat, vegetables etc.) while each is clickable because they are buttons. The third one is to use natural language processing. At the centre of the screen is always a microphone, which is also a button. Additional to the important button „See Recipes“ which we will click now, we can see other buttons too which will be explained at the end of this analysis.

The relevant/ingredient-dependent recipes are „hidden“ behind one more button. Following it you will see the wished list of recipes for the ingredients chosen, while the same as before each is at the same time a button. Next to the recipes which can be done with the selected ingredients, we can see underneath some others which require 1 more ingredient. Next to this list, you can see filter like „video only“ or „meal type“ and you can also select more ingredients. With a click on a recipe, it`s clear that the categorization is done with tags because we can see here the tags. You can also see here a rating, the cooking time needed, the necessary amount or weight of the ingredients and nutrition facts. With another click, we will be forwarded to one of a few websites because Supercook does not host the full recipes. You can see here links to similar recipes under „You might also like“ too. If you step back to where we found the „hidden“ button we can also see the more ingredients selection and the filter. Additional: Some recipes are shown in a big horizontal slider with the headline „Featured Recipes“ or in many (>20) smaller slider with categories like „low carbs“, „gluten free“ or „cookies“; always with a picture.

Besides the „See Recipes“ button you can see a menu with the name „My Pantry“ where you can deselect your ingredients, a shoppting list which allows to save ingredients in a seperate list and an acctount mode. „If you sign up for an account, your ingredients, and dietary restrictions, will be saved on Supercooks servers. This means you can sign into your account from any device and everything will be synced up. Having an account also allows you to “favorite” recipes you like so you can easily find them later.“

Who did what?

Christian was writing and Mouadh was leading during the gathering

What did we learn?

To come closer to our goal this week was very helpful because we discovered a working product and it`s flow producing. The interview made us aware of the community of people who want to count calories and we will focus on that niche

What went well?

If we can continue like this week it`s very likely that our product will be great.

What do we want to improve?

All writing was good this week but we had problems with the data formating.