StyleShare+Prototype

=High Fidelity Prototype:= Main Prototype

The prototype we created is basically a replica of the Balsamiq profile we created in the previous phase, but the functionality is limited. While most of the pages have links and are fully connected, not everything works perfectly. There were problems integrating AppSketcher files with JavaScript/JQuery functionality. Please reference the final prototype description for an exact breakdown of how the website should work: http://cmsc434-f11.wikispaces.com/Final+Prototype

=Missing Components= Since the high-fidelity prototype is supposed to be a test of our ideas to guide us in the right direction with the remainder of development, we were limited in how much we could implement without having to potentially re-write large portions of the website in future phases. Things we left out:

Database Functionality
The user log in system we planned to implement is basically useless without a database since the main purpose of each account is to track the clothing items and outfits that the user adds to his/her closet. Since we did not want to implement the entire database just yet, we decided not to implement the database or the user log in system. This means that search queries on the 'Browse' pages can't be executed, items can't be rated or recommended, and we will have test users pretend that they can create and save outfits, manipulate their closet, view other's closets, communicate with other users (recommend items and send messages), and rate items using 'hooks'. We realized that these are the main features of our website, but implementing them will take longer than the time we had for this phase and will consequently defeat a major purpose of the 'high-fidelity prototype'. Instead we made static pages that can at least show the user (with some prior knowledge) what the expected behavior of the system is like. We covered as many aspects of the website that we could with static pages.

Modules & Page Features

 * The home page sign up link doesn't go anywhere. In order to reach the page a logged-in user will see, just click Log In.
 * The notifications do not link to their corresponding pages. These would hypothetically link to the 'Edit Outfit' page for the outfit that another user recommended.
 * Drag and drop for editing outfits is not fully debugged.
 * The pictures to the left of the notifications should be profile pictures for various user accounts, that link to their profiles - this is not implemented.
 * The messaging system is not implemented and cannot really be done so without the database. The sample messages are static.
 * Also, the pictures to the left do not link to user accounts.
 * Sample data is static without database functionality. This effects the following:
 * "Friends" and "Users" listed on Browse Users
 * "Your Clothes" and "Clothes You Don't Have" on Browse Clothing
 * "Your Outfits" and "Other's Outfits" on Browse Outfits
 * Clothing & Outfits in My Closet
 * Featured Items & Contents on the Home page
 * All messages under Messages
 * Search criteria is not implemented (and cannot truly be without database functionality). This effects the follow pages:
 * My Closet
 * Browse Clothing
 * Browse Outfits
 * Browse Users
 * There is no log-out button. We plan to put this below settings in the options menu, but App Sketcher didn't work for this purpose.
 * Pop Up Windows
 * There was problems integrating pop up windows with all of the features that we hope to utilize in the window.
 * An AppSketcher implementation of the page can be seen here:
 * Clothing or Outfit Detail
 * Clothing or Outfit Detail (While Editing an Outfit)