Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Catastrophic: “Resume” button was intended to show a student’s Résumé but a user could think it means resume back to the search screen. (User 1)

Solution: Change the button to display text “Résumé”.

2. Catastrophic: Searching for multiple “and” and “or” in one clause results in one suggestion repeated several times. (User 2)

Solution: Re-examine parser and suggested terms.

3. Major: When new users register an account, the previously entered information is stored in the text field. (Users 1,2,3)

Solution: Clear the text fields for registering a new account. (User 1,2,3) 

4. Major: If the requirements text field is empty, there is still a popup of Suggested Values. (Users 1,2)

Solution: Do not have the popup or have it say “You didn’t enter anything!” (User 1,2)

5. Major: User didn’t realize the need to select a student and then e-mail. (Users 1,2)

Solution: Consider that with the hide functionality, the “Email Students” button could be clicked to default email all the students that match. Consider changing the “Email X students” button to say “Email X selected students”.

6. Major: Users don’t have an efficient way of emailing all students that match besides selecting them all one by one. (User 1,3)

Solution: Have a “Select All Students” button.

7. Major: User could not find documentation for learnability. (User 3)

Solution: Consider putting together a “Help” section for website capabilities.

8. Minor: User was misled by “Showing 40 matches” when only 6 were visible at a time. (Users 1,3)

Solution: Consider removing “Showing” or changing it to say “Showing 6 of 40 matches”.

9. Minor: Users can get confused with the inconsistency of having to select a student and then perform the Email action whereas the Hide action can be performed with or without selecting a student. (User 1,3)

Solution: None because of the tradeoff in scenarios where users need to hide in the middle of selecting students to email. Users can’t have freedom to change their minds in the middle of selecting students to e-mail.

10. Minor: Users didn’t know what to expectin clicking the gear icon. They understood it was settings of some somrt but didn’t know if it was view settings, search settings, or other miscellaneous settings. (Users 2,3)

Solution: Adding text to say “Filter/Sort Settings”

11. Minor: Search input beginning with “or” or “and” does not add the respective “or” or “and” clause, but always returns as an “and” clause. (User 2)

Solution: Have the parser account for the case of having an “or” clause before classes.

12. Minor: Users are not stopped in their search when the requirements return no results because they missed the feedback in the match results. (User 3)

Solution: Consider preventing users from adding more requirements if current requirements return none until the user updates the requirements to allow for more matches.

13. Cosmetic: User understands “Courses” requirement to mean either Course as in major or Course as in class. (User 3)

Solution: Consider either using “Classes” or “Subjects” or both.

Reflection