Process for User-centered Development
From Computing and Software Wiki
(→Iterative Design) |
(→Empirical Testing) |
||
| Line 6: | Line 6: | ||
== Empirical Testing == | == Empirical Testing == | ||
| - | + | === User-based Tests === | |
| - | + | ||
| + | ==== User Survey ==== | ||
| + | |||
| + | ==== Performance-based ==== | ||
| + | |||
| + | ==== Think-aloud protocol ==== | ||
| + | |||
| + | ==== Co-discovery ==== | ||
== Iterative Design == | == Iterative Design == | ||
Revision as of 01:32, 23 November 2009
Write introduction here.
Contents |
Early Focus on Users
Empirical Testing
User-based Tests
User Survey
Performance-based
Think-aloud protocol
Co-discovery
Iterative Design
The iterative design method is applied in the development of a new product (typically a software). It consists of developing by a succession of iterations. Five steps compose this method:
- Prepare a prototype design of the product
- Present this design to a set of potential users
- Collect problems noticed by users
- Refine design based on users point of view
- Repeat steps 2 to 4 until you get a desired result
This method puts quality at the centre of the development path. Indeed, by refining step by step the design, you obtain a product approved by its future users. That's the main reason why it fits totally with User Interface development. As it's hard for a User Interface designer to get a perfect understanding of user's needs and behaviour, it allows him to base his work on user's feedback and improve his product based on their point of view.
Websites use this method a lot: Web masters generally propose an interface and collect user's feedback by email or with a dedicated topic on the website forum and correct mistakes. For software development, it is different as it's impossible to propose an unfinished product to the customer. The iterative design method is used to perfect the design before the software release.
