You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Task Analysis
Our website is meant to be accessed in two different settings. On one hand, the Manager needs to update his/her restaurant’s menu information from a web interface, where he/she can easily update the restaurant’s profile. From a different side, users will interact with the mobile-optimized site from their phones and mobile devices.

1. Update Restaurant Profile (Manager)

Why is the task being done?
The site needs to be updated with menu information about the restaurant, so that content can be displayed to users.

What does the user need to know or have before doing the task?
The manager must have information about what items the restaurant will be serving, and a knowledge how he/she wants this information is to be displayed. He/she must also have pictures of the food items to display on the menu.

Where is the task being performed?
The task is performed on a desktop or laptop computer, either in the restaurant or at home.

How often is the task performed?
The task only needs to be performed as many times as the menu information changes or whenever there are new pictures to be uploaded.

What are its time or resource constraints?
There are no time or resource constraints on the user here, especially if he/she is working from home.

How is the task learned?
The task will be structured like a basic webform, which is quite learnable if the user is used to working with websites, but will also be made obvious by the nature of the form.

What can go wrong? (Exceptions, errors, emergencies)
The user can insert improper and/or incorrect information, but the interface will make for easy editing of such errors.

Who else is involved in the task?
No one else needs to be involved in the task, but the manager may ask a chef or photographer to help update the restaurant profile.

2. View/Filter a Menu (Client/Waiter)

Why is the task being done?
The task is being done to see what items are offered at the restaurant that the client is currently eating at, and to see pictures of said items.

What does the user need to know or have before doing the task?
The user doesn’t need to know anything beforehand, but his/her experience might be shaped by a desire to filter the menu by criteria such as dietary constraints or food cravings.

Where is the task being performed?
The task can be performed inside of the restaurant before the client orders or while on the go as a precursor to deciding to visit the restaurant. Anywhere the user can access the internet from his/her mobile phone is a valid location for the task.

How often is the task performed?
This task is performed whenever the user wants to eat or search a menu.

What are its time or resource constraints?
There are no resource constraints but time might be constrained by the client’s hunger or desire to order food.

How is the task learned?
The task is meant to be intuitive and learnable, but waiters are trained in this task in order to help the client learn the task.

What can go wrong? (Exceptions, errors, emergencies)
The task is meant to inform clients of the options available to them in an innovative way, and the client will not be able to provide any feedback to the managers or waiters through the site.

Who else is involved in the task?
No one.

3. Search for Restaurant (Client)

Why is the task being done?
The client may want to search for a particular restaurant to see its menu, or to find restaurants in the area.

What does the user need to know or have before doing the task?
The user can either search by name, in which case he/she should have the name of the restaurant. Otherwise, the mobile app will use location to search for restaurants.

Where is the task being performed?
The task can be performed anywhere, although it has special behavior if performed at the same location as the restaurant.

How often is the task performed?
This task is performed whenever the user wants to eat or search a menu.

What are its time or resource constraints?
There are no resource constraints but time might be constrained by the client’s hunger or desire to order food.

How is the task learned?
The task is meant to be intuitive and learnable, mirroring other interfaces that users will have seen if they are already mobile phone users.

What can go wrong? (Exceptions, errors, emergencies)
The task is meant to inform clients of the restaurants available to them in an innovative way, and the client will not be able to provide any feedback through the site.

Who else is involved in the task?
No one.

  • No labels