Week 6

Our lecture this week was on low fidelity prototype: paper prototype and evaluation.

Prototype and Evaluation
This is the process of paper prototype development and evaluation.

What is a paper prototype?
Paper prototyping is the first time in the user-centred design process that you put together the elements of your new interface design, in a way that approximates what users would see on screen. Although it might seem like it is taking a long time to get to the point, all of the previous steps have been designed to ensure that your paper prototype is as close as possible to the interface that your users will want to work with. Paper prototyping involves creating a minimal version of your interface using easily movable and replaceable interface elements, created from pieces of paper.

This process has two essential steps
1. Development process: Developing ground work and prototype.
2. Evaluation process: Methods of testing and evaluation.

The development process looks a little like this;

System requirements -----------> Information structure ----------> Wireframes ----------> Use scenarios

System requirements is the stage where you have to list all the tasks and goals that your application will be helping with.

Information structure is the stage where you describe how the users can complete different tasks to achieve their goals.

Wireframes is the stage where you sketches what the app will look like.

Use scenario is the last stage and this is where you state the different situations under which your system will be used.

The evaluation process is formative in nature.
But what are we evaluating?
There are 5 principles of usability an they are;

• Effectiveness
• Efficiency 
• Satisfaction
• Learnability
• Memorability

What is the point of evaluation process?

The evaluation process helps the users pick up the problems, and the difficulties they are having with it. It is to help suss out all the problems the app has so we can than change it to make it better. 

In saying this in the evaluation process their is two methods and they are;

1. Inspection method: does not require users. The process is conducted by usability experts.

2. Testing method: products evaluated by testing with real users. 

In the inspection method, their is another 2 methods used and they are;

1. Cognitive walk through

2. Heuristic evaluation

In the testing method, their is also another 2 methods used and they are;

1. Co-discovery

2. Wizard of oz

The lecture was finished with our homework for the week. Our homework for this week was we had to finalise requirements of the solution in terms of tasks and workflow. We also had to prepare information structure to show how our users accomplish their intended goals. We had to prepare wireframes of our solution.

This week I really struggled with the homework. I was not sure what I had to do, so I waited for class on Wednesday so I could tale to me teacher. 

In class, their were quite a few people that struggled with this weeks homework. The teacher sat us down and explained in more detail as to what he wanted than he gave us time in class to than do this. All he wanted was a simple mind map of the tasks that the application would help with and sketches of our app which are called wireframes. This week meant I was a little behind in my assignment but overall I am feeling confident that I can do well. After class I will sit down and do my wireframes and do my mind map. 

References

Gudur, Raghavendra. (2015). 9291 User Interface and experience. Lecture 5, week 6: Paper prototyping and evaluation. [powerpoint slides]. 

Nodder, C. (2014). UX design techniques: Paper prototyping. Retrieved from http://www.lynda.com/Web-Prototyping-tutorials/UX-Design-Techniques-Paper-Prototyping/161093-2.html 

Usability first. (2002). Low fidelity prototype. Retrieved from http://www.usabilityfirst.com/glossary/low-fidelity-prototype/