...

All code we wrote is public on GitHub: https://github.com/benweissmann/vegitude.

Evaluation

We conducted our user tests on three people, each from a different segment of the targeted population. Categories in our target user group are vegans, vegetarians, and non-restricted persons who cook for friends with restrictive dietary needs. We briefed each individual with a general description of the problem that Vegitude is trying to solve and the manner in which it solves it. Following that, we gave each individual three or four tasks based on a scenario centered around the segment of the user population that they are in. Each task touched on a different capability of the website, making sure that each user could successfully learn how to utilize all of Vegitude’s capabilities naturally, without being told or shown how to do so. Here is the link to the user briefing and tasks.

...

Reflecting on the past project, I think that our organization during this project went was pretty well. swell; We all contributed very heavily to the project and came out with a very nicely designed product that both has a reasonable use, as well as an easy-to-learn interface.

We learned a lot throughout this project, from using Bootstrap to create appealing layouts, to creating a database to store structured recipe data, to using python to crawl recipe websites and extract structured data from free-form text.

We used our prototyping stages effectively. While the overall design is similar to the original paper prototype, we fine-tuned colors and sizes and added additional features (such as the mini-search on the results page) based on the feedback we received from our heuristic evaluations.

If we were to do anything differently, it would have probably been early but consistently-updated documentation in order to make it more easy to do group work separate from the groupto create documentation at an earlier stage, and to update this documentation so we could use it as a tool for collaboration and coordination.