# [CSE 340](/courses/cse340/22wi/schedule.html) Lab 10 Winter 2022 ## Week 10: SUS Testing --- # HW Timeline - Last section of this quarter, you can do this! :) - **Final Project** - **Code** is Out: F 25-Feb, Due: Sa 12-Mar, Lock: Su 13-Mar - **Video and Reflection** are due Due: F 17-Mar --- # Section 10 Objectives - [System Usability Scale testing](#5) - [Section Exercise](#9): SUS testing on a sample app - [Kahoot](#11) - Extra Office Hours! --- # Testing for AS6 - Final Project - Remember to have your testers fill out [this](https://forms.gle/WeCaHTPA6BUZDyTJA) form for AS6 --- # SUS Testing: Pros and Cons ![:youtube How Useful Is the System Usability Scale (SUS) in UX Projects with Jakob Nielsen ,6b2YFgRCVDE] ??? Pros: - Used for a long time (many decades, many data), is a standard Cons: - SUS testing can be misleading… testing gathers very elaborate profiles (10 different questions) - The focus is supposed to be on user behavior - Why ask so many questions? The number values can be taken out of context - Better method: Observe user behavior, not just asking them. Just ask people 1 satisfaction question if you want a number - Have people free-form write and say their responses (essays). - WHY is this design boring or unlikeable? - Puts their thoughts into context --- # Reminder: SUS Questions 1. I think that I would like to use this [project] frequently. 2. I found the [project] unnecessarily complex. 3. I thought the [project] was easy to use. 4. I think that I would need the support of a technical person to be able to use this [project]. 5. I found the various functions in this [project] were well integrated. 6. I thought there was too much inconsistency in this [project]. 7. I imagine that most people would learn to use this [project] very quickly. 8. I found the [project] very cumbersome to use. 9. I felt very confident using the [project]. 10. I needed to learn a lot of things before I could get going with this [project]. --- # System Usability Score Scoring Each question is rated 5-point Likert Scale from strongly disagree to strongly agree Scoring for each question is done based using the following scale: * **Strongly Disagree**: 1 point * **Disagree**: 2 points * **Neutral**: 3 points * **Agree**: 4 points * **Strongly Agree**: 5 points --- # Calculating a System Usability Score 1. Add up the total score for all odd-numbered questions, then subtract 5 from the total to get (X). 2. Add up the total score for all even-numbered questions, then subtract that total from 25 to get (Y). 3. Add up the total score of the new values (X+Y) and multiply by 2.5. Example scoring: Odd = (4+5+3+4+3) = 19 X = 19 – 5 = 14 <br> Even = (2+1+3+1+1) = 8 Y = 25 – 8 = 17 SUS Score: (14+17) x 2.5 = 77.5 - Note: The average SUS score is 68 --- # Section Exercise: Evaluate Apps with SUS - You will evaluate 1 of 3 sample applications with SUS testing and submit with [this](https://forms.gle/WeCaHTPA6BUZDyTJA) form. - Please choose 1 of the following to evaluate: - https://henry-heino.web.app/Misc/Metronome2.html → hheino - https://xournal.online/#/ → tdokka - https://www.accessmap.io/ → jial8 - While filling out the form, please indicate the 'App Author' as the above listed UW NetIDs. (This is just for comparing results) --- # Section Exercise: Compare Results - Calculate your SUS score to share out in class (This [site](https://uiuxtrend.com/sus-calculator/) can help with the calculation) - Compare your SUS score with others who chose the same app. --- # Kahoot! --- # Extra Office Hours - Use this opportunity to seek help from students using similar sensors or app ideas!
