Reference no: EM131013366

Creating and Testing a PaperPrototype-

Prototyping is an important step as it allows you to decide on navigation, layout, menu options, application structure and much more, making quick decisions about your apps or site's requirements and ultimate design.

A prototype does not mean screens must be perfect. In fact, it shouldn't be: the majority of time should be spent iterating the design, not making screens beautiful. Prototypes are made to be tested and iterated (and if they fail, thrown away).

1: Choose a Storyboard

Decision time. Set out your storyboards. Study your Personas. Take a deep breath. Spend some time to reflect on the different ideas you've had. Make sure you discuss the strengths and weaknesses of each design, and how well they be useful andfityour personas goal's. Keep in mind how you will improve the efficiency and effectiveness of the business process. And then, decide on one of these ideas to prototype.

2: Create and Test an Interactive Paper Prototype

Make a paper prototypes that implements the improvement ideas you've decided on. A rapid interactive paper prototype concretely shows all the major elements of a user interface, except that it's implemented with pen and paper

Again, paper prototypes helps focus on the concepts, and saves you from wasting hours twiddling. The goal is to be fast, flexible and creative.

The paper prototype you create should be interactive. That means that your user testers should be able to navigate around it and get a feel for how the ‘real thing' would work. The prototype should be complete enough to "run" a new user through a task. You can start making a paper prototype, then change your mind an update it as you learn through letting users interact with it. And your prototype doesn't have to exactly align with your storyboard. Your prototype interface should enable people to navigate, recover from errors, and change their mind etc.

1. Turn in your Paper Prototype.

2. Create One Task to Test with your prototype and fill out a Template Task Sheet (see Below and see PowerPoint for an example )

3. Test your Prototype with at least two users

Prepare responses to the following questions:

• Explain what you learned and how you changed the prototype as a result of user testing?

• What were the main stumbling blocks for the user(s)?

4. Create at least 5 user stories that are supported by your prototype(or that you subsequently need to include in your next prototype).
User stories can help managers discover what really needs to be built without rushing too far forward under and help business sponsors manage their investment in software and get the most out of it. User stories are short, simple description of a requirement told from the perspective of the person who desires the new capability. They follow this simple template:

As a <type of user>, I want <some goal> so that <some reason or benefit>.

User stories can facilitate planning and discussion. As such, they strongly shift the focus from vague ideas to discussing system requirements. In fact, these discussions are more important than whatever text is written.