...
Still had some learnability issues and confusion as to how to enter a requirement with an or (Java or C++ and Matlab). He was till unsure even after looking at the example we included. He was successfully able to hide 3 students and then restore one of them. When trying to email students, he didn't see the "email students" button so he tried clicking on their profile card but couldn't find the email button.
User B:
| Wiki Markup |
|---|
\[blank\] |
User C:
| Wiki Markup |
|---|
\[blank\] |
Overall Takeaways:
Understood what we meant by Java or (C++ and Matlab) but accidentally entered in Java or C++ by mistake after looking at the example. After he hid a student and wanted to reshow them he successfully hit undo and showed the student, but he wondered what would happen if he had wanted to undo multiple "hide student actions", and he didn't really understand the "view hidden students". He also didn't understand that you could email multiple students at a time; he selected each student individually and then hit email right away to email them and had to unselect them afterwards to email new students.
User C:
First successful user to enter in composite boolean logic requirements. When clicking through multiple pages of students he forgot which students were selected on previous pages so he had to scroll through pages unnecessarily. Went to get a drink of water in the middle of emailing students and mentioned that a save button for your emails would be useful.
Overall Takeaways:
It seems that although its getting easier for users to do composite boolean logic there is still some confusion. Perhaps we would benefit from a tutorial at the beginning on how to enter in requirements, or a recommended menu of things you can do (w/ composite boolean logic in the menu). Users seem to prefer personal touches to email, so perhaps have a sort of template that will enter in each students name individually so that the email can appear personal even though you only have to write it once. It might be userful to have some sort of tabs system that shows search results in one tab, hidden students in another tab, and selected students in another tab since if there are many search results on many pages it can be difficult to remember which ones are hidden and selected. We should also have some sort of count displayed for hidden students and selected students since users might not want to go over a certain limit.Wiki Markup
Prototype iteration
We made several changes when creating our second prototype in response to the user feedback we got for the first prototype. On the results section which displays the mini student cards, users didn’t understand that the x in the top right corner was so you could get rid of the student card or they didn’t even see it, so we decided to make a hide button that was very visible on the bottom left. Users had the option of starting a search over, and we had a popup that asked them if they were sure they wanted to start over with the default value set to yes. We decided to change this for safety reasons to having the default value set to no so that users wouldn’t accidentally press enter and clear the results of their search. Previously we had a “start new search” button that always appeared, but we decided to make that button invisible until the user actually did at least one search since we didn’t want our users to accidentally click that button while entering in their search parameters and have to start over.
...