1. Identification Summary
Title: View Top Presentations
Summary: This use case describes the steps to be followed to view the top presentations of the
day.
Actors:
1. User – the one who uploads presentations.
2. Slideshare system – the one that make presentations viewable online.
Creation Date: July 8, 2013 Date of update: July 8, 2013
Version: v1.0 Person in Charge: Richmond Roy R. Roldan
Flow of Events
Preconditions:
1. User and Slideshare have already undergone Login use-case.
Main Success Scenario:
1. Slideshare refreshes its page and will display the user’s newsfeed.
2. User presses Slideshare home button.
3. Slideshare refreshes and will display the top presentations of the day, featured, hot on
Facebook, twitter, linkedln.
4. User browses top presentations.
5. User views the next set of presentations.
User repeats step 3-4 until user decides to switch to other Slideshare features.
6. Use –case ends successfully.

2. Alternative Sequence:
A4a. User decides to view a Presentation.
1. User proceeds to view presentations use case.
A4b. User decides to like or comment on a presentation.
1. User proceeds to comment/like a presentation use case.
A4c. User refreshes the top presentations.
1. Use-case proceeds to step 3.
Post-Conditions:
1. Like for the presentation updated.
2. Comment for the presentation updated.
3. The view of the presentation will count.

3. Identification Summary
Title: Upload Presentation
Summary: This use case describes the steps to be followed to upload a certain presentation.
Actors:
1. User – the one who uploads presentations.
2. Slideshare system – the one that makes the presentation available online.
Creation Date: July 8, 2013 Date of update: July 8, 2013
Version: v1.0 Person in Charge: Richmond Roy R. Roldan
Flow of Events
Preconditions:
1. User and Slideshare have already undergone Login use-case.
2. User has already selected a file to upload.
Main Success Scenario:
1. Slideshare refreshes its page and will display the user’s newsfeed.
2. User presses upload button.
3. User will select the file and upload it to Slideshare.
4. User will name, describe, add topics, and select a category on where to put the
uploaded file.
5. User will save the changes that were made. User will view the uploaded presentation.
6. Use –case ends successfully.

4. Alternative Sequence:
A5a. User decides to share the presentation on other sites.
1. User proceeds to share the presentations use case.
A5b. User edits the information that was given to the uploaded file.
1. User proceeds to edit the information use case.
Post-Conditions:
1. The uploaded file is now available in Slideshare.
Identification Summary

5. Title: View Videos
Summary: This use case describes the steps to view a certain video.
Actors:
1. User – the one who browse or view videos.
2. Slideshare system – the one that makes the videos available online.
Creation Date: July 8, 2013 Date of update: July 8, 2013
Version: v1.0 Person in Charge: Richmond Roy R. Roldan
Flow of Events
Preconditions:
1. User and Slideshare have already undergone Login use-case.
Main Success Scenario:
1. User selects videos under browse.
2. User selects to view the top videos for the day, week, month, year, or all time.
3. User will browse the videos available on Slideshare.
4. User views the video. User will like or comment on the video.
5. User repeats steps 3-4 until the user decides to switch to any Slideshare features .
6. Use –case ends successfully.
Alternative Sequence:

6. A4a. User decides to like or comment on a video.
1. User proceeds to like/comment a presentation use case.
A4b. User refreshes the top videos.
1. Use-case proceeds to step 3.
Post-Conditions:
1. Like for the presentation updated.
2. Comment for the presentation updated.
3. The view of the video will count.