...
Image 1 was redrawn so that only the important buttons are present. Students in recitation criticized the original design's number of buttons and the fact that they were all equally sized although only a fixed set of buttons will be used 90% of the time. In this design only the critical features appear on the home page.
Image 2/3 were redrawn to include a "location" column instead of a "bin" column because not every dorm uses bins to sort packages--some do not sort them at all.
Students in class suggested adding ", etc" to the list of search suggestions to be displayed in the search bar before a user types anything. This will make it clearer that the text in the search bar is a suggestion--not a requirement.
Learnability: This design is very learnable because design is very learnable because it's very explicit. It's obvious that if you want to do anything involving packages, you should click on "packages" in image 1. The button icons also make the button functionalities explicit. In addition, users can type anything into the search bar, so if a user doen't know where to look for "pool sticks", they can type it into the search bar and the database entry for "pool sticks" will pop up.
Image 2/3 were redrawn to include a "location" column instead of a "bin" column because not every dorm uses bins to sort packages--some do not sort them at all.
Students in class suggested adding ", etc" to the list of search suggestions to be displayed in the search bar before a user types anything. This will make it clearer that the text in the search bar is a suggestion--not a requirement.
Efficiency: This design is not as efficient as it could be because it requires a lot of clicks to get where you want to go. Having a homepage means the user will have to click an extra time to get from the homepage to whatever page they want to be on. Once on the packages page, users must use move their hands to the keyboard, type in package information, and then go back to the mouse to click the "check out" button, which isn't very efficient. It would be better if, after typing in enough information to the search bar so as to return only one search result, users could press "enter" or some shortcut command to check out a package.
Safety: This design has safety built into it in the form of the search bar. If users cannot find what they're looking for they can search for it. Also, the "undo" button allows users to revert packages they did not mean to checkout. However, the undo option will only work for one package (so we won't have to store mass amounts of data), so if users accidentally check out the wrong package and then the right package, they won't be able to undo checking out the wrong package. Users can find the information for the accidentally checked out package by clicking on the "history" button on the homepage. They can then re-enter that information to re-register the package they accidentally checked out.This design is