Scenario:



Team 5

Mitch Dempsey MDEMPSEY@UCI.EDU

Allen Huang AEHUANG@UCI.EDU

Arthur Huang ACHIU1@UCI.EDU

Matthew Kwow MWKWOK@UCI.EDU

To Register for an account, please visit:



After you have confirmed your email address, please visit the URL below and login.



Or



Photo sharing has changed the way pictures distributed among friends,and family. Before the rise of photo sharing, distributing digital photos required uploading each photo to an email attachment sent to an individual or group of individuals. With photo sharing it allows a person to upload to one site and distribute the site to anyone who he or she wishes. This distribution creates a simple way for many people to view the photographs at once, as well as share the photographs with others who may or may not have been included in the original invintation.

Currently, the photo hosting system provided by Facebook does not allow for users to upload their pictures at full quality. All pictures are converted to a 604x604 pixel thumbnail (Which is terribly small, especially when cheap modern cameras take pictures with dimensions greater than 2800 pixels). Our aim is to allow users to be able to safely and securely store all their pictures. However, by serving as a replacement to Facebook photos, the application will need to seamlessly replicate the functionality of Facebook's Photos.

The goal of this project is to allow users on Picmember and Facebook to seamlessly mix with each other. It will allow Picmember users to publish their pictures onto Facebook, so that their friends can view them easier. It will also allow users on Facebook to easily transition over to Picmember services. The system should also allow groups to collaborate and act as a single point of collaboration for all members to post pictures and learn about upcoming events.

The goal of Picmember is to provide full-quality hosting alternative to Facebook. Photos are also sorted based on event, which allows for a much more logical viewing path.

|Task |Description |Actions Required |Interface Response to Actions |Required Knowledge |

|Create an album. |User creates an album. |User clicks “Create Album” button on |Album is created. |Basic mouse and keyboard knowledge. |

| | |main page. | | |

| | |User fills in required fields. |User is redirected to the upload | |

| | | |pictures page. | |

|View an album. |User views an album. |User places mouse over the “Pictures” |Album is displayed to the user. |Basic mouse and keyboard knowledge. |

| | |option and waits for the drop down menu | | |

| | |to appear. | | |

| | |User selects “Browse Albums” from the | | |

| | |drop down menu. | | |

| | |User selects the album he or she wishes | | |

| | |to view. | | |

|Create an event. |User creates an event. |User places mouse over the “Events” | |Basic mouse and keyboard knowledge. |

| | |option and waits for the drop down menu |User is redirected to the event page. | |

| | |to appear. | | |

| | |User selects “Create Event” button. | | |

| | |User fills in the necessary information.| | |

|View an event. |User views an event. |User places mouse over the “Events” |Event is displayed to the user. |Basic mouse and keyboard knowledge. |

| | |option and waits for the drop down menu | | |

| | |to appear. | | |

| | |User selects “Browse Events” | | |

| | |User selects the event he or she wishes | | |

| | |to view. | | |

|Add an existing album to an event. |User adds an existing album to an event.|User clicks the “Events” Button. |Albums are saved to the event. |Basic mouse and keyboard knowledge. |

| | |User clicks the event that he or she | | |

| | |wishes to add an album to. |User will be alerted that the albums | |

| | |User clicks the “Add Album” button. |have been saved. | |

| | |User checks off which albums he or she | | |

| | |wishes to add. | | |

| | |User clicks the “Save Albums to event” | | |

| | |button. | | |

|Delete and event. |User deletes an event he or she created.|User clicks the “Events” button. |Event is deleted. |Basic mouse and keyboard knowledge. |

| | |User clicks the event that he or she | | |

| | |wishes to delete. | | |

| | |User clicks the “Edit Event” link. | | |

| | |User clicks the “Delete Event >>” link. | | |

| | |User confirms it is okay to delete the | | |

| | |event. | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download