Scenario:
I could have sworn I already wrote this.
Individual Design Sketches:
- Katherine
- design 1 - This design is intended for illiterate users. There are pictures illustrating the different options available to the user. Unfortunately, the system must require some amount of literacy to look up resident names and items names or the user would spend an unreasonable amount of time searching through a database of pictures. This design mimics Google Chrome's applications screen and many smartphone screens in that it displays options as different "apps" each with their own icon that the user can open.
- design 2 - This design is intended to mimic the tab system used in many popular web browsers. Learnability is key here. By using a design users are familiar with they won't mind trying out deskdash because it won't ne complicated or take a long time to learn.
- design 3 - This design employs the menu approach to options. Users will always have the same menu of options to choose from on every page to which they navigate. Users can always find what they're looking for because it's always there and always in the same place.
- Jimmy
- design 1 (mobile nightime) - This design is intended for night time workers using a tiny interface. They have to verifiy whether someone with or without an id can enter the building
- design 2 (HomePage and Package Registration Page Possible Output after packages registered) - This design is intended for daytime workers registering packages. It allows a user to register multiple packages at once, increasing the efficiency of the of the process. The second image is still a design choice yet to be made. It w
- design 3 (Package Pickup Page) - This design shows the process for picking up a package. Feedback is given instantly on whether or not a user entered is in the db, or has a package. If they have multiple packages that are all being checked out, there is a select all feature to make sure the process is efficient.
- Chris
Designs and Storyboards
Analysis of Storyboards
more blah