Identification Summary

TITLE: REGISTER ACCOUNT SUMMARY: This use case describes the steps associated with registering an account for Task Rabbit ACTORS: 1. User registers account 2. API System processes and saves the information that has been inputted by the User

Flow of Events
PRECONDITIONS: 1. A valid e-mail address MAIN SUCCESS SCENARIO: 1. User opens TaskRabbit Webpage and proceeds to its Homepage. 2. User clicks on Join For Free. 3. API will redirect you to a sign up form. 4. User enters information such as full name, email address, password, and zip code. 5. User clicks on Create Your Account button. 6. The website will redirect user to a new page. 7. The system has already sent a confirmation message to the users email address. 8. User confirms email and will be able to Log In. ALTERNATIVE SEQUENCE: A1. User logged in with Facebook Account 1. The system redirects user to a new page. 2. User logs in to his Facebook account to complete the task. 3. User will immediately be directed to his TaskRabbit account. ERROR SEQUENCE: E3a. User email address does not exist 1. API will not be able to send user confirmation of the account created. a. Wrong mail address was inputted. 1. User will have to repeat the procedure from step 1. 2. Use-case ends E3b. User puts wrong information 1. The system will redirect the user to a page with the message Oops! Something has gone terribly wrong. Our engineers have been notified and are working to get thing right. 2. The user may proceed to Step 3 3. Use Case ends E3c. User already has an existing account, lost password 1. The system will redirect to a page and will automatically send user a link to change his password. 2. The user may log in then. 3. Use Case End

POST-CONDITIONS: 1. An email will be sent to user as confirmation. UI REQUIREMENTS: 1. Valid Email Address 2. Complete User Information NON-FUNCTIONAL REQUIREMENTS: 1. The System is responsive within <1 second>

Identification Summary
TITLE: CREATE TASK SUMMARY: This use case describes the steps in making tasks in TaskRabbit. ACTORS: 1. User creates tasks 2. API System processes transactions and saves the information that has been inputted by the User

Flow of Events
PRECONDITIONS: 1. Registered Account 2. Valid Credit Card MAIN SUCCESS SCENARIO: 1. User Logs In to his account. 2. User clicks on Create Task button. 3. API will redirect user to a sign up form. 4. User enters required information. 5. User summarizes task in one sentence. 6. User chooses which category the task belongs. 7. User sets the time and place the task is to be accomplished. 8. User sets a fixed amount on how much the user is willing to pay its runner. 9. User will be asked to place instructions. 10.User is required to place credit card number before posting task. 11.Post task and wait for a response within 24 hours. ALTERNATIVE SEQUENCE: A1. User may choose to bid his task 1. After step 7, the user will be asked of its willingness to pay. 2. User may choose to make set a fixed amount or put its task up to a bidding. 3. User proceeds to Step 8. 4. Use-Case End. ERROR SEQUENCE: E3a. User does not have a valid credit card 1. User is not allowed to post a task without filling up credit card number. a. User has to repeat Step 10. 2. Use-case ends. POST-CONDITIONS: 1. An email will be sent to user as confirmation. UI REQUIREMENTS: 1. Valid Email Address 2. Complete User Information 3. Valid Credit Card NON-FUNCTIONAL REQUIREMENTS:

1. The System is responsive within <1 second>

Identification Summary
TITLE: CANCEL TASK SUMMARY: This use case describes the steps in cancelling tasks ACTORS: 3. User cancels 4. API System processes transactions and records the changes by the User.

Flow of Events
PRECONDITIONS: 1. Registered Account MAIN SUCCESS SCENARIO: 1. User Logs In to his account. 2. User clicks on he Task he wishes to cancel. 3. Task is not yet assigned to a TaskRabbit. 4. API will redirect user to another page. 5. User will accomplish a questionnaire. 6. User clicks on Cancel Task. 7. User may now log out. ALTERNATIVE SEQUENCE: A1. Users Task is already assigned to a TaskRabbit 1. User follows steps 1-2. 2. User will be redirected to a different page. 3. User will be accomplishing a different questionnaire form. 4. Users Task will be cancelled after 24hours or upon confirmation of his TaskRabbit. 5. Use-Case End. ERROR SEQUENCE: E3a. User s not logged in 1. User must follow step 1 first before doing task. 2. Use-case ends. POST-CONDITIONS: 1. An email will be sent to user as confirmation of your cancellation of your task. UI REQUIREMENTS: 1. Valid Email Address 2. Complete User Information