Problem Statement

People have a lot of clothes in their wardrobe, but run out of ideas for outfits very quickly, which means that they have to go out and buy more clothes. What if other people could suggest new outfit ideas using existing items in the wardrobe? The goal of PK3k is to make uploading wardrobe items simple for the wardrobe owner and to make designing outfits easy for the outfit designers. 

Challenges

Possible challenges include:

1. Implementation of the interface for outfit designers (Should be intuitive; how do we make the wardrobe items easily searchable and how do we group them?)
2. Implementation of the wardrobe uploading system (if from online sources, how do we create a good interface for users to find their specific article of clothing? If from a camera, how do we try to ensure the quality of these images and make the interface intuitive?)

User Analysis

We have determined that there are two groups of users. This analysis is based on two sets of interviews with 3 people (3 people per group).

Group 1: The Wardrobe Owners

Age: 13 - 35

Gender: N/A

Education: English literate

Abilities: Computer literate, Access to internet

Motivations: Warrobe owners have a lot of items of clothing in their wardrobe, but have run out of ideas for outfit combinations and want suggestions for possible outfits.

Existing Approaches: 

Bulleted Conclusions from interviews

1. They like to eat chocolate

1. • Om nom nom.
   • Delicious
2. They really like chocolate
   • Om nom nom

Group 2: The Outfit Designers

Age: 13 - 35

Gender: N/A

Education: English literate

Abilities: Computer literate, Access to internet

Motivations: 

Existing Approaches: 

Bulleted Conclusions from Interviews

1. They want to know the occasion

1. • "One of the first things I do is ask what occasion the outfit is for"
   • Even for the same person, different occasions call for completely different outfits (e.g. outfits for a beach vs. dance party)
2. They want to know the build of the person

   • "It \[designing outfits\] is totally different depending on the person's build. For example, a 5' 2" woman that wears a size 12 is going to look better in a flowy outfit, while a 5' 11" woman that wears the same size will be wearing more proportional outfits"

   • "Designing an outfit for a 6' 5" model that wears size 0 is going to be different than designing an outfit for your every day person"
3. They don't need to see the person's face (but hair color and eye colors are important)
   • "I don't need to see their face"
   • "The person's hair and eye colors determine what colors will look good on them."
4. Personality of the person is important
   • "It's all about the attitude, whether they can pull an outfit off"
   • "People are all associated with a season and they tend to wear clothes that match their season"

Task Analysis

These are the tasks that represent wanted functionalities from the point of view of the user. 

Major Tasks

1. Upload user's wardrobe
   • Goal: User would like to upload the clothing in their wardrobe in order to allow others to view the user's wardrobe and allow others to design new outfits.
   • Precondition: User must have clothing. 
   • Subtasks:
     1. Describe the two items using a name and/or image and/or description
     2. Describe the context in which the decision is being made. (User is trying to save money, user wants people to vote based on overall traits, etc)
     3. Set a time limit on when voting ends
     4. Finish creating poll
2. Create a new outfit
   • Goal: User wants to take articles of clothing from another user's wardrobe and match them together into an outfit.
   • Precondition: User has created a poll that has finished, or has an existing poll they would like to close.
   • Subtasks:
     1. Be able to view voting results for this newly-created poll as the poll goes on
     2. Optional: Close the poll early
     3. Receive a notification when the poll ends, with a summary of results
     4. After the decision has been made in real life, user selects which option they ultimately decided on to give feedback to the voters
3. Browse outfits that have been created for a user
   • Goal: User wants to vote on a poll that has been created so that the user can be a part of other users' decisions (or so that the user can procrastinate and put off doing his or her pset).
   • Precondition: User is bored and/or feeling helpful and is near a computer or a smartphone with internet. User must be logged in for this.
   • Subtasks: 
     1. Find a poll to vote on, either through a search (on poll traits such as item names, time remaining, number of votes so far) or randomized listing
     2. Select one of the two items in the poll
     3. Optional: Add a comment to go along with the vote
     4. Submit the vote
     5. View a summary of how the votes have been cast thus far
4. Search and browse polls
   • Goal: User wants to search and browse through completed polls so that the user can make a decision about items in an existing previous poll without having to remake a new poll. Also, the user would like to search and browse polls to see what people are comparing. For instance, if the user is trying to find movies similar to Lord of the Rings (LotR), the user can search for polls with LotR to see what it is being compared to.
   • Precondition: User is near a computer with internet and is curious about a specific item or topic, whether because they are trying to make a decision or because they are trying to find similar items. User does not need to be logged in for this.
   • Subtasks:
     1. Enter search queries, which may include a search on the name/description of the items, total number of votes, etc.
     2. View results listing the items in the poll along with a summary of results
     3. View the comments for a given side of a poll
     4. View statistics about a particular item (For instance, how often items with names matching "iPhone" have been voted for and against, how many polls have been created with that item name, a list of other items that have been popular contenders, etc)

1. #*