Prototype Testing - Mockup

The link below lets you download the mockup of the input device interface that will be used for carrying out walkthroughs:

http://rapidshare.com/files/22907346/Mockup.ppt.html

The mockup has been created based on the menu designs and the scenarios outlined. It was created using Powerpoint, with hyperlinks providing button functionality. Some limitations to the mockup are:

• It cannot provide contextual navigation (e.g. if there are two ways to access a page, if you press a back button it will only go back to a default, not the actual last page you visited).
• The handwriting recognition sections cannot be implemented. The plan is to have a pen and paper ready during the walkthroughs and record what users write in this way.
• The mockup functionality is limited to the scenarios, which cover all main aspects but not the whole system (e.g. there aren't delete or edit buttons for every single piece of information as it would take too long to make). However, this should be sufficient enough for testing purposes.

Prototype Testing - Scenarios

Below are the key scenarios to be used for the testing of the touch screen interface and the watch, written in the use case style used in earlier stages. These scenarios will be combined with a mockup of the system.

Ideas for Testing/Evaluation?

We didn't get time to cover this today, so I'm posting here. If anyone has any ideas of how we should test our prototype, add them to the comments. Here's a few, let me know what you think:

• Create a HTML/Powerpoint mockup of the interface, and perform either a cooperative or heuristic evaluation using the personas and/or real people.
• In terms of the mockup, we could either ask them to play with it or give them tasks based on scenarios we have come up with.
• Use my inferior eyesight skills to play a user who has difficulty seeing the interface, and perform a cooperative/heuristic evalution of the interface.
• For the voice recognition part, ask the personas/real people to come up with what they would say if we asked them to tell the device to do something, and compare the results.
• Ask someone from another team to pose as a HCI expert and evaluate our design.
• Perform more questionnaires concentrating on aspects such as the aesthetics of the product.
• Evaluate parts of the system ourselves according to literature and/or design principles already out there.