Bureaucrats, emailconfirmed
1,221
edits
No edit summary |
(prototyping) |
||
Line 222: | Line 222: | ||
==Choosing a task== | ==Choosing a task== | ||
So what shall your | So what shall your testers do with the Prototype? You need to give them some tasks they are going to do. So you should follow some simple steps: | ||
* Write down typical tasks one can resolve using your product. This is a little brainstorming. | * Write down typical tasks one can resolve using your product. This is a little brainstorming. | ||
* Out of the tasks you wrote down you choose the ones that you feel are typical for your software and crucial for using it. | * Out of the tasks you wrote down you choose the ones that you feel are typical for your software and crucial for using it. | ||
Line 232: | Line 232: | ||
==Build a Prototype== | ==Build a Prototype== | ||
Now as you know what you are going to test you can build your prototype. | Now as you know what you are going to test you can build your prototype. It needs to simulate the situations that can occur when the participants do the task you gave them. So at least you need to cover the possibilities to resolve the task and some sideways that don't lead to the task's solution. Otherwise the Participant will try to interact and your prototype will not be up to responding and "crashes". I will show two possibilities: Paper-Prototyping and coded prototyping. | ||
===Paper Prototyping=== | |||
===Coded Prototyping=== | |||
==Do the test== | ==Do the test== | ||
==Formulate your findings== | ==Formulate your findings== |