Requirements List, User Experience Goals, & Usability Goals
Usability Goals
- minimize number of clicks to reach a desired recipe
- minimize visible layout elements (easy to remember, easy to learn)
- provide advanced functionality as alternate interface
- easy to extract data (example: printing stylesheets rather than separate pages)
User Experience Goals
- users should be confident that recipes will work
- users should have access to data in a convenient form
- users can share data and provide feedback to the system (community building)
- users should have access to supplementary data, i.e. recipe variations, similar recipes, and technique documentation (helpful, motivating design)
Requirements
These requirements are illustrated in the Usage Scenarios and Hierarchical Task Analyses.
Functional
- provide recipes based on users' available and unavailable ingredients
- search results should be refinable
- provide recipe methods with measurements in various standard units
- make extra information available, such as how to dice ingredients
- provide with ability to browse via other methods or criteria
- have a base set of recipes on launch (possibly from a company)
- provide an avenue for submitting recipes via a community
- encourage recipe submission
- recipes should be moderated before they become public
- simple use should not require login
- must be able to print to a variety of devices
Non-functional
- must run on most pc platforms with little to no difficulty in setup
- some functionality of the system should be extended to portable devices