Bureaucrats, emailconfirmed
1,221
edits
no edit summary
No edit summary |
No edit summary |
||
| Line 206: | Line 206: | ||
==Modeless Design== | ==Modeless Design== | ||
=Get to know if your ideas work!= | =Get to know if your ideas work!= | ||
After we developed ideas it is again time to check with reality! This is known as prototyping and testing. | |||
First you look what you need to test, like ''"does or Web-Page navigation work?", "Do people find the preference dialog?", "do people get along with a totally direct Manipulation approach or are we better of implementing it point-and-click?"'' | |||
For answering your questions you will need to build a prototype. (You can and should test finished products too, but I assume you design) Prototyping is creating a "model" of your software that enables you to try out certain things. Think of building a model aircraft: It will be sufficient to show if an engineers idea will be work in general. | |||
Prototypes are easy to make (especially compared to the final product) and don't waste resources if an idea does not work. Ideas that don't work get sorted out and you can try something new. Because it does not hurt to be wrong you can be creative and find new ways of doing things. | |||
==Getting people top do the testing== | ==Getting people top do the testing== | ||
==Choosing a task== | ==Choosing a task== | ||
==Writing a scenario== | ==Writing a scenario== | ||
== | ==Build a Prototype== | ||
Prototypes can be implemented in different ways: in script-code, various office programs and in paper and sketches. Which way you choose depend on what is the easiest for you to build and what the prototype needs to do. The latter sections will provide insight in how code and paper prototypes differ | |||
==Do the test== | ==Do the test== | ||
==Formulate your findings== | ==Formulate your findings== | ||