II.

Use Case Narrative Identification summary Title: Sign-up Summary: This use case describes the steps associated with signing up or joining linkedIn. Actors: 1. User the person who will sign-up the website. 2. LinkedIn System This system enables the user to successfully sign-up to linkdin. Creation Date: October 27, 2013 Version: v1.0 Date of Update: October 28, 2013 Create by: Alek Irasusta

Flow of Events Preconditions: 1. The user enters the LinkedIn website. Main Success Scenario: 1. User clicks the sign-up button. 2. System will leave information such as First Name, Last Name, E-mail and Password. 3. The user will type the necessary information regarding to the requirements. 4. The user will click join LinkedIn. 5. System will direct you into creating your profile. 6. User will continue into creating his/her profile. 7. System directs you into confirming your email. 8. System prompts you a request into accessing some certain information. 9. User validates and approves of it. 10. System directs you to into some optional processes. 11. User validates and approves of it. 12. System will confirm and validates your created profile. 13. System directs you to your newly created account. 14. Use case ends successfully.

Alternative Sequences: A3: User decides to join via Facebook. 1. System will sync your Facebook account to Linkdin. 2. Proceed to step 5. A9: User decides to skip the processes. 1. Proceed to step 12. Error Sequences: E3: The user mistakenly inputs the wrong information that is required. 1. System prompts you an error. 2. Use case ends. Post-conditions: 1. The user is signed in. 2. The user account is verified.

Identification summary Title: Log-in Summary: This use case describes the steps associated to logging in into linkdin. Actors: 1. User person who owns the account and will login to his account. 2. LinkedIn System This system enables the user to access his account. Creation Date: October 27, 2013 Version: v1.0 Flow of Events Preconditions: 1. The user is registered to LinkedIn. 2. The user remembers both his username and password. Main Success Scenario: 1. The user goes to the LinkedIn website. 2. System will show the LinkedIn websites homepage. 3. The user will types his/her e-mail and password. 4. The user will click the Login button. 5. The system will verify the e-mail and password of that user. 6. User has been logged in. 7. Use case ends successfully. Error Sequences: E3: The user types in the wrong username or password. 1. The system tells the user that the information is invalid. 2. Use case ends. Post-conditions: 1. The user is in his/her LinkedIn page. Date of Update: October 28, 2013 Create by: Alek Irasusta

Identification summary Title: Edit Profile Summary: This use case describes the process on how to edit the users information. Actors: 1. User Person who will edit the account. 2. LinkedIn System This system allows the user to update his profile. Creation Date: October 27, 2013 Version: v1.0 Flow of Events Preconditions: 1. User has a LinkedIn account. 2. User has logged in to LinkedIn. Date of Update: October 28, 2013 Create by: Alek Irasusta

Main Success Scenario: 1. User will position the mouse to the profile button. 2. System will show choices including the edit profile button. 3. The user will click on the edit profile button. 4. The system will send the user to the edit profile information page. 5. The user will edit or add information for his profile. 6. The user will click on save changes. 7. The system will update the profile. 8. The system will send the user to his newly edited profile. 9. Use case ends successfully.

Error Sequences: E7: The system fails to update the profile. 1. The users edited information are not placed nor updated. 2. Use case ends. Post-conditions: 1. The user has successfully edited his/her profile.

III. Activity Diagram 1. Sign-up or join

2. Login

3. Edit Profile