Group Members
- Stephen Suen ssuen
- Kathy Fang kfang
- Yi Wu wuyi
- Connie Huang connieh
- TA: Katrina Panovich
GR1 - User and Task Analysis
GR2 - Designs
GR3 - Paper Prototyping
GR4 - Computer Prototyping
GR5 - Implementation
GR6 - User Testing
GR2 - Designs
Scenario
Tiffany is a 24-year-old software developer working in San Jose, California. She is engaged to Brian, a nurse who works double shifts to make ends meet.
Because of financial reasons, Tiffany and Brian decide not to hire a wedding planner and opt to organize the event themselves. Tiffany takes the lead in planning the wedding, but is overwhelmed by the number of tasks to accomplish in such a short period of time. She uses Hitched to make a timeline of all the tasks and milestones that lie ahead (Task 1).
Because Brian works long hours, he cannot help with wedding planning, but would still like to keep up with Tiffany’s decisions and offer input. Tiffany’s best friend and maid of honor, BFFany, wants to help in the planning process. Brian’s mother, Lucille, constantly nags Tiffany about her progress and disagrees with many of Tiffany’s choices. Tiffany wants to make sure she can satisfy everyone else involved in the process by getting their input in an organized way (Task 2)
Tiffany synthesizes all the feedback and incorporates it into her timeline. At each stage of the process, she updates the involved parties when decisions are finalized (Task 3).
Individual Sketches
Kathy's Sketches |
Analysis |
|---|---|
|
The user selects the date he/she wants to start planning the wedding, the date of the wedding, and types of events/tasks from a checklist. Then, the user sees a suggested timeline in calendar form, with event/task dates highlighted. The user can click on a month or day to zoom in and see details of a specific event. The user can change the task location, time, and description, and notify guests of these changes. The user can also see guests' comments or send guests a reminder about the event/task. |
|
These sketches show the log-in and home screens of a user's account. Upon logging in, the user sees two types of weddings: those that he/she can edit and those that he/she is tracking, but can't edit. Next to each wedding, the user sees the number of new notifications. When the user clicks on these notifications, he/she is brought to a new screen that displays the notifications in detail (i.e., new comments on events or new changes to event dates). Each wedding has a homepage that can be accessed from the notifications page. From the homepage, a user can view or search the wedding timeline or message the primary host of the wedding. |
|
These sketches show a mobile interface. The user wants to search for an event on a a specific wedding timeline (Allison's wedding in this example). The autocomplete feature increases search efficiency and enables the user to type fewer characters, improving accuracy because typing is often error-prone on a mobile device. The user can then view event details and see some previous comments. Most previous comments are hidden (and revealed upon clicking the load more button) because of limited screen space on a mobile device. Finally, the user can post his/her own comment, after which he/she is taken to a page linked to other relevant actions (i.e., undo comment, search for other events). |
Stephen's Sketches |
Analysis |
|---|---|
|
|
|
|
Connie's Sketches |
Analysis |
|
|
|
|
|
|
Yi's Sketches |
Analysis |
|---|---|
|
This is a design for the sign up page. The top screen is the home page, with a button to sign up at the center. In the right corner is the login button for returning users. When a user clicks on signup button, the popup |
|
|
Team Storyboards
