...

Third, we implemented user accounts. We used these accounts to store user-specific wardrobes, requests, and responses in our database. Our project hinged heavily on each user being able to create their own personal wardrobe for others to work with; the need for user-specific accounts was clear from the start. We built our interface around this design, in part, and it was largely unobtrusive. It does require additional steps from our users, but the start-up time for completing this process was not a burden (as our user testing below discovered). As a consequence of the user testing, however, we did discover a conflict in trying to verify accounts on our site when using a mobile device.

Fourth, and finally, we opted to not implement updating or deletion of content from most elements of our site. Submitted requests at present cannot be updated, closed, or deleted; uploaded outfits cannot be moved to new clothing categories, and they cannot be removed from the user's wardrobe. These limitations are certainly worth addressing, as they dramatically limit the user's freedom to manage the content of the site. At the same time, these limitations do not restrict the kind of content that our users can produce - every outfit combination and request can still be created.These features were thus deemed to be optional elements, and were left by the wayside in favor of the more critical elements of our design.

Evaluation

Describe how you conducted your user test. Describe how you found your users and how representative they are of your target user population (but don't identify your users by name). Describe how the users were briefed and what tasks they performed; if you did a demo for them as part of your briefing, justify that decision. List the usability problems you found, and discuss how you might solve them.

...