...
Iteration 1 observations
User test 1:
Search page
- user selected a few departments, reasoning was “I like course 6”, which doesn't really make sense because these are hass classes and there is probably at most one course 6 hass class. He didn't understand what all of the departments were there (was probably confused by the three letter ones like “STS” and such that are not described). He was puzzled why some of the department numbers were underlined and others weren't.
- he user next goes over to the categories but has no idea what they are (they are basically listed as 1, 2, 3, 4, 5, Language, and Elective).
- He's user is confused about selecting a schedule
- He's user is confused about how to actually search. The search button was very large, but he instead clicked the “Browse” button on the top navigation bar. The button he clicked brings him to the search results, but he was very unsure of whether it would or not.
...
- user wants to know more about 21H.467, like the name. Once the user clicked on it, the name and info popped up, but it's a history class and she was not interested in taking a history class at all. She mentioned that it would be useful to see the name before clicking on it, because she never would have clicked on it if she saw the name of the class ahead of time.
- when she noticed that there was a message saying you could drag and drop classes to the right sidebar, she remarked “oh!”
- user guesses that any classes dragged to these boxes will stay there (will be persistent) – user is correct
- user wants to look at the description again when it's in the box – this operation is allowed
- “what does finalize mean?” - at the time, the “my classes” page was called “finalize” - this was very confusing to people
User test 3:
TBA...
Iteration 2
User test 1:
User test 2:
User test 3:
Prototype iteration
Changes from iteration 1 to 2:
...