Identification Summary Title: Submit Report Summary: This use case describes the steps associated with submitting

a report Actors: 1. User person who will use the system 2. Waze global positioning system that shows traffic submitted by users
Creation Date: October 9, 2013 Version: v1.0 Flow of Events Preconditions: 1. GPS must be on 2. Connected to internet 3. User must have Waze account Post-conditions: 1. Database is updated Main Success Scenario: 1. User creates traffic report 2. User chooses type of traffic 3. User chooses which side of the road the traffic to be reported is 4. User sends report 5. Waze adds report to the database 6. Use case ends Alternative Sequences: A1a. Report is about police in the area 1. User chooses to report about police 2. User chooses visibility of police A1b. Report is about accident in the area 1. User chooses accident report 2. User chooses type of accident A1c. Report is about hazard in the area 1. User chooses hazard report 2. User chooses type of hazard A1d. Report is about traffic camera in the area 1. User chooses camera report 2. User chooses type of camera A1e. Report is about map issue 1. User chooses to report about map issue 2. User chooses type of issue A1f. Report is about pavement 1. User chooses to report about paved road 2. User drives until paved road ends Date of Update: October 28, 2013 Person in Charge: Janine Chua

3. User stops report A1g. Report is about closure in the area 1. User chooses closure report A4. Report with picture 1. User takes picture 2. User sends report Error Sequences: E4. Unable to connect to server 1. Waze notifies user of the error 2. Use case ends

Identification Summary Title: Check Location Summary: This use case describes the steps associated with checking the current location with GPS Actors: 1. User - person who will use the system 2. Waze - global positioning system that shows traffic submitted by users
Creation Date: October 9, 2013 Version: v1.0 Flow of Events Preconditions: 1. GPS must be on 2. Connected to internet 3. User must have Waze account Post-conditions: 1. Database is updated Main Success Scenario: 1. User sends location request 2. Waze updates user location 3. Waze shows user on the map 4. Use case ends Alternative Sequences: A1. Rotate map to proper orientation relative to cardinal directions 1. User presses icon to adjust orientation 2. Waze rotates map to proper orientation Error Sequences: E1. Unable to connect to server 1. Waze notifies user of the error 2. Use case ends Date of Update: October 28, 2013 Person in Charge: Janine Chua

Identification Summary Title: Get Directions Summary: This use case describes the steps associated with getting directions Actors: 1. User - person who will use the system 2. Waze - global positioning system that shows traffic submitted by users
Creation Date: October 9, 2013 Version: v1.0 Flow of Events Preconditions: 1. GPS must be on 2. Connected to internet 3. User must have Waze account Post-conditions: 1. Database is updated Main Success Scenario: 1. User requests for directions 2. User types the location desired 3. User sends request 4. Waze calculates directions 5. Waze shows directions 6. Use case ends Alternative Sequences: A2. Location is stored 1. User chooses stored location Error Sequences: E3. Unable to connect to server 3. Waze notifies user of the error 4. Use case ends E4. Unable to calculate directions 1. Waze notifies user of the error 2. Use case ends Date of Update: October 28, 2013 Person in Charge: Janine Chua