1 / 65

Creating UIs

Creating UIs. Usability Testing. How to create a UI?. Plan. Test. Design. How to create a UI?. Step 3. Step 2. Step 1. Design. Test. Plan. How to create a UI?. Step 3. Step 2. Step 1. Design. Test. Plan. Testing Outline. What is usability? Usability Factors

taurus
Download Presentation

Creating UIs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creating UIs Usability Testing

  2. How to create a UI? Plan Test Design

  3. How to create a UI? Step 3 Step 2 Step 1 Design Test Plan

  4. How to create a UI? Step 3 Step 2 Step 1 Design Test Plan

  5. Testing Outline • What is usability? • Usability Factors • Usability Problems • Planning for a test • Carrying out the test • Usability Report

  6. What is usability? In general, usability refers to how well users can learn and use a product to achieve their goals and how satisfied they are with that process.

  7. A product is usable if… • Quick to use and relatively error free • Does what the user wants • Easy to use

  8. Why test for usability? • Find program bugs • Prove that the system is easy to use • Find problems • Correct problems • Experience the users of the application

  9. When should usability tests happen? • During design? • Once a functional prototype is made? • When the application is complete and ready to ship?

  10. Run usability tests early during design • Preferably before a lot of programming has been done. • The point of testing is to correct problems. If we wait until the app is finished, there is no time to fix the problems. • Allows developers more time to interact and gain experience with the users.

  11. Experiencing the user • An important side effect of early usability testing is that developers can experience the users and learn new things about them. • Developers learn from the users: • Their domain knowledge and attitudes • Their IT knowledge and attitudes • More about their domain tasks

  12. Experiencing the user When developers take the time to experience their users, they can strongly improve their intuition when designing the user interface.

  13. Testing Outline • What is usability? • Usability Factors • Usability Problems • Planning for a test • Carrying out the test • Usability Report

  14. 6 factors for usability • Fit for use. The system can support the tasks that the user has in real life. • Ease of learning. How easy is the system to learn for various groups of users? • Task efficiency.How efficient is it for the frequent user?

  15. 6 factors for usability • Ease of remembering. How easy is it to remember for the occasional user? • Subjective satisfaction. How satisfied is the user with the system. • Understandability. How easy is it to understand what the system does?

  16. 6 factors for usability • It is impossible to score high in all 6 factors; therefore, it is necessary to specify the level needed for each factor. • Each application has different types of goals and should place emphasis on different types of usability factors.

  17. Testing Outline • What is usability? • Usability Factors • Usability Problems • Planning for a test • Carrying out the test • Usability Report

  18. Identifying Usability Problems • A usability problem is anything that hampers the user. • It is important to find usability problems in order to correct them and make the application more usable.

  19. Classifying Usability Problems • One method of classifying problems is by their severity. • By classifying problems, we can identify which problems need to be fixed sooner than others.

  20. Problem severity • Missing functionality or bug – The system cannot support the user’s task. • Task failure – The user cannot complete the task on his own or they erroneously believed they completed it.

  21. Problem severity • Annoying – The user complains that the system is annoying or cumbersome; or the designer observes that the user doesn’t work in the optimal way. • Medium problem – The user finds the solution after lengthy attempts. • Minor problem – The user finds the solution after a few short attempts

  22. A problem can have multiple severities After leaving a webpage, it doesn’t remember who I am so I have to re-enter my user name the next time I visit it. • The webpage is missing functionality to remember users between visits and that is annoyingto the user. • Multiple severities for one problem, might make it more important to fix.

  23. Benefits of classifying problems • Designers, developers, managers, etc. can identify which problems need to be fixed sooner than others.

  24. Usability Problem Examples • The user cannot figure out how to start the search. The screen says that they should use F10, but for some reason they don’t see it until they try several other ways. • The user believes that they have completed the task and that the result is saved, but actually they should have pressed Update before closing the window. Classify by Severity: Missing Functionality, Task Failure, Annoying, Medium, or Minor

  25. Usability Problem Examples • The user cannot figure out which discount code to give the customer, although they know which field to use. • The user says that it is completely crazy having to go through six screens in order to fill in ten fields. • The user wants to print out a list of discount codes. After many failed attempt, they email support and figure out that they system cannot do that. Classify by Severity: Missing Functionality, Task Failure, Annoying, Medium, or Minor

  26. Testing Outline • What is usability? • Usability Factors • Usability Problems • Planning for a test • Carrying out the test • Usability Report

  27. Planning the test • Picking a type of usability test • Deciding how many users we need to test • Deciding which users to test • Finding test tasks • Choosing roles for the test team • Deciding how to measure task efficiency

  28. Types of Usability Testing • Observe only • Think aloud • Cooperation • Hallway Testing • Opinion Poll • Heuristic Evaluations

  29. Observe Only • Let the user work on their own while we observe what they are doing.

  30. Think aloud • Ask the user to think aloud and explain what they are doing and why. • Have users explain situations when they get stuck. • Question the user’s intent in situations where you have become confused with what they are doing.

  31. Cooperation • Ask two test users to work together on a task. Encourage them to discuss what they are doing and how they might complete the task at hand.

  32. Hallway Testing • Grab the next person that passes you in the hallway and force them to test the new code/prototype that you made. • The basic idea is to show simple screens of your proposed design to anyone other than designers or engineers working on the product.

  33. Hallway Testing • Particularly effective in early stages of a new design when designers are looking for “brick walls.” • Very cheap to do

  34. Opinion Polls • Ask a number of users to complete a questionnaire. • Typically uses a Likert scale • Strongly disagree, disagree, neutral, agree, strongly agree

  35. Opinion Polls • Some specialists consider opinion polls the best measure of usability • Give consistent results from user to user • Hard to perform test during development. Often get better results after application is finished.

  36. Heuristic Evaluation • Hire a usability specialist to look at your design/prototype/system and point out problems. • Expensive to perform • Helpful for finding missing functionality • Still require usability testing to determine ease of use

  37. Planning the test • Picking a type of usability test • Deciding how many users we need to test • Deciding which users to test • Finding test tasks • Choosing roles for the test team • Deciding how to measure task efficiency

  38. How many users do we need? • Ideally you want 5 users • If you can’t find/afford 5 users, 3 will work • Whatever you do, don’t settle for ZERO!

  39. How many users do we need? • Don’t spend all your resources on one testing session with 15 users to discover all possible usability problems. • Instead, have 3 different sets of tests that each have 5 users.

  40. Planning the test • Picking a type of usability test • Deciding how many users we need to test • Deciding which users to test • Finding test tasks • Choosing roles for the test team • Deciding how to measure task efficiency

  41. Which users should we pick? • Don’t use colleagues or people working on your project. • Look for users that are in the weaker end of their user group. • Avoid strong users or IT geeks that might be able to guess their way around problems based off prior experience.

  42. Planning the test • Picking a type of usability test • Deciding how many users we need to test • Deciding which users to test • Finding test tasks • Choosing roles for the test team • Deciding how to measure task efficiency

  43. Finding test tasks • It is important to find good test tasks in order to find all usability problems. • Different kinds of applications will have different test tasks

  44. Test tasks for professional use • Most professional apps are developed to help users do their tasks better. • Study the apps supported tasks to create a list of tasks to test.

  45. Test tasks for web sites • Websites can be used to attract customers and inform them about the website’s company. • In addition to this, some websites support actual tasks (buying products, reviewing bills).

  46. Test tasks for web sites Here are some sources for identifying web site test tasks: • Expectation oriented– Given a small product description, what would a user expect to see when visiting the product’s website.

  47. Expectation Oriented Questions to ask before showing the website • What type of information does a user expect to find? • What services should be offered? Questions to ask after showing the website • Did the user find all necessary information and services? • Was you expectation met? • What is your impression of the company after seeing the website?

  48. Test tasks for web sites • Business-oriented -What is the company’s goal with the web site? What do they expect that the customer/user would do? • What are the prices for the services? • Where is the closest shop? • How to call them on the phone?

  49. Test tasks for web sites • Label oriented - Do users understand the terminology/labels your website is using? • The site has a link labeled ‘staff.’ Where do you think that would take you?

  50. Test tasks for web sites • Structure-oriented– Do users have a clear sense of where they are in the website / service process? • How many screens do you think are left before you have completed what you do? • Where will the system take you afterwards? • How could you cancel what you are doing?

More Related