Part of course:
What it Rapid Prototyping?
- The Rapid Prototyping Process
- What do you need to prototype?
- How much should you include in your prototype?
- Make a scenario
- Iteration Plan
Rapid Prototyping is an iterative process used to quickly visualize what a system (such as a website or an application) will look like in order to get feedback and validation from users, stakeholders, developers and designers.
Prototypes can come in many forms, such as a rough sketch on paper or an interactive simulation that looks like the final product. The key to successful rapid prototyping is to use feedback to quickly revise the prototype using the right method.
Used well, rapid prototyping can improve the quality and speed of your design by improving communication and reducing the risk of missing requirements.
Rapid Prototyping involves a three-step process, repeated as many times as needed:
A prototype will usually start with a very simple mock-up of key areas and become more complex with each iteration as you gather more data from user feedback.
A prototype is not designed to be a fully functional version of a system, but is only meant to help visualize the user experience of the final product. Prototyping is a good method to evaluate:
Focus on the key functions that will be used most often. The point of rapid prototyping is to show how a function will work or what the design will look like without prototyping the entire product.
Instead of going function by function, create a story that will take the user through the areas that you want to prototype. This way, you will get more accurate feedback because your prototype will reflect real life scenarios.
A good rule of thumb when planning iterations is to start broad and then work your way towards a more detailed version of the solution. Using website design as an example, you can start with a mockup of the home page and landing pages, and then move deeper into the other sections of the website.