Test high-fidelity Prototype with Users (Process Notes 5.3.1)


This task tests should ideally be done in parallel with the task of building the prototype. However, if the process of building the prototype involves procedures that are irrelevant to the user (due to the nature of the prototyping product), then it is better to build the prototype before showing it to the user.

The trouble with high-fidelity prototypes is that they are often so convincing that users are convinced that they are real, and think that you can build the whole system in half an hour. Remind the users that this model is a prototype. It's like a stage setit appears to be real until you look behind the facade and discover that it is only simulated functionality.

Demonstrate the prototype to the users and ask questions like these:

  • Does this model behave as you expected?

  • Can you imagine yourself using a product that works like this to do useful work?

  • Does anything about the prototype irritate you?

Review the objective of the prototype, and ask whether the prototype is leading you toward satisfying that objective. Depending on the objective of the prototype, you might decide to leave the prototype with the users for a period of time so that they can experiment with it and give you feedback at a later date. Identify any prototype modifications that are necessary to bring the prototype closer to satisfying this objective.

If you have satisfied the objective of the prototype, then the usage feedback will consist of user comments, new requirements, and requirements changes that emerge as a result of using the prototype.




Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net