On the top is the homepage. On the left is the navigation bar which allows you to access all the functions you'll need in one place.
Below that package registration page. Alyssa arrived here by hitting "Package Registration" under "Packages" on the left. When Ben's package arrived, it was dropped off along with a few others. This page allows you to register more than one package at once so that you don't have to enter the info, hit "Update," enter in the info for another package, and then hit update again. This page will have Auto-Complete, and Auto-fill functionality. For instance, if Ben is the only Ben that lives in the dorm, then by entering "ben" his name should come up
in auto-complete, and once enter is hit, his last name will be filled in.
Top) When the Alyssa hits "Update" the Waiting Packages page comes up to demonstrate to Alyssa that the packages were registered.
Bottom) Ben comes to pickup his package a few hours later. Alyssa hit "Package Pickup" under "Packages" on the left navigation bar. She enters Ben's name. Once she hits search, it loads the next screen. If she entered the name of someone who wasn't in the db, or someone who didn't have a package, a message would flash telling her that that is the case.
Top) This screen shows who you are picking up packages for. If he had received more than one packages in different bins, and he was picking up both, then Alyssa could just hit "Select All" and then press "Pickup" to have remove the packages from the waiting packages list.
Bottom) Once all of his packages are picked up, the page says that there are no packages for Ben Biddle.
Analysis
This design was revised according to comments and feedback received in class.
Learnability: The design is learnable because all of the actions can be found on the left. It's also learnable because there are common affordances (querying information by names, text fields with hints in them), and the buttons have meaningful text, indicating the action that would occur.
Efficiency: The design is efficient because it allows for multiple package registration. It's also fast because the actions are consistently on the left.
Safety: Because of auto complete, you'll know if a name isn't in the db. There is a chance of registering a package for someone who doesn't have a package (for instance, if you enter the wrong Ben). You can easily undo this by picking up the package. There are definitely faster ways to take care of that scenario. Because of the step involved in checking out a package (searching for some one by name, and seeing their name on the Pickup package page) it'd be hard to pickup a package for the wrong person.