TBD-Notes
From CS 160 Fall 2008
Contents |
Stepan Grigoryan
Task Measures
* Create Char: 50s/0e * Collecting Data: 25s/0e * Reviewing Data: 84s/0e * Carpooling: 240s/0e * Customizing/Shopping: 140s/0e
Critical Incidents
1. Trouble clicking menu, waiting for user input.
2. Spatially fine with it.
3. Spent a lot of time reading each of the screens
4. Can't tell that it was running on the background - collecting data
5. Prototype issue - not dynamic enough
6. Did not properly end data collection by clicking on it only once, bad design - have to click on it twice -
7. A lot of reading and involvement
8. Unclear - review data - diagram/prototype is unclear, too much text
9. Accel. different font - can see,different colors - speed
10. Name of avatar - correlation between avatar and map is unclear, avatar should have name in screen.
11. Conversion to Iphone - touch screen, click on it once
12. Menu click -confusion - where to buy items
13. In store, there should be more confirmation - feedback, to show that you actually bought it. Put character at top than bottom.
14. Should have a click to buy.
15. In store, liked where the money is located - the position is appropriate
16. Should have a Save Routes button instead of or in addition to Back to Routes button
17. Request Call Confirmation/ CALL - confusion
18. Label map to show that it is actually a map
19. Color should inference ranking - green is good
20. Change You to Me in the maps
Ronald Tong:
Task Measures
* Create Char: 45s/0e * Collecting Data: 20s/0e * Reviewing Data: 140s/1e * Carpooling: 310s/0e * Customizing/Shopping: 210s/0e
Critical Incidents
1. Ronald mentioned that the animal selection that we provided may be too childish for most users.
2. When asked to begin collecting data, he pressed OK to proceed. However, when the screen reverted back to his personal cell phone background, he was confused as to what our application was doing. He mentioned that we needed to make clearer boundaries between the user's personal background and the application message: 'Collecting Data. Press End twice to stop'.
3. When reviewing his data, Ron was slightly slow to understand what was going on. It was not obvious that each point on the map corresponded to a number on the keypad. Also, he did not toggle between the current route and weekly routes.
4. During his shopping session, Ron correctly guessed that the number at the top left of the screen was his current amount of money, but he mentioned that we should make this more clear.
5. While equipping items onto his characters, he could not figure out how to de-equip items.
6. While setting up his carpooling session, he did not realize that there was a ranking associated with the maps of his friend's routes. He was also confused by the 'call/request carpool confirmation screen'. He did not realize that he needed to call his friend first in order to set up a confirmation.
7. Lastly, Ron mentioned that there should be a differentiation between how we collect data for normal driving and how we collect data for carpooling.
Jennifer Chong:
Task Measures
* Create Char: 55s/0e * Collecting Data: 21s/0e * Reviewing Data: 220s/1e * Carpooling: 200s/0e * Customizing/Shopping: 423s/2e
Critical Incidents
1. confused about what the map means on the reviewing data screen
2. confused about the numbers on the map on the reviewing data screen
3. Took some time to read all the text, but did take the time to read it.
4. went to options screen instead of the shop
5. went to "your items" screen instead of the shop
6. said that went to options out of reflex, seen many other applications with options screen
7. used to a back option instead of a menu option
8. went to request confirmation page first, then went to call option.
