COMP 6620 HW4 Alabama Uniform Traffic Crash Report Data Entry System Design Volkan Ustun

System  A web server  Two databases Main database (submitted reports) Temporary database (saved reports for later submittal)  Web interfaces  Querying capabilities from central databases for SSN and Driver License Number  Print-out capability for the filled in forms in the desired format.

Web interface  Four main menu items New  To create a crash report Update  To update previously recorded reports Submit  To submit previously recorded reports Log out  To log out from the system

Menu Item - New  Accident Info  Location/Time  Vehicle/Pedestrian Driver Info (if unit is vehicle) Vehicle Info (if unit is vehicle) Pedestrian Info (if unit is pedestrian)  Save  Submit  Quit

Menu Item – Update  Displays previously recorded or submitted reports by the officer.  Allows the officer to update the previously saved reports  Update pages are similar to new report pages, therefore not presented in the presentation

Menu Item - Submit  Displays previously recorded or saved reports by the officer  Allows the officer to print and/or submit the selected reports

Menu Item – Log out  Logs out the user

Scenario (new form)  Officer logs onto the web server using his personal ID and password.  User selects the new menu item from the menu  Officer fills in the fields for the general accident info (including number of units involved in the accident, vehicles and if there is pedestrians)  Officer clicks on the next button

 Officer fills in the location and time information on the accident  Officer clicks the next button  Units involved in the accident is displayed  For each unit If the unit is vehicle, officer enters driver license no, driver license state and VIN. If the unit is pedestrian, officer enters the SSN of the pedestrian.

 Central database is queried and the results are presented for the first unit (driver or pedestrian).  If no results found, an empty form is presented  Officer makes the necessary changes on driver information and driver license information (it may be necessary to fill out another form to report the changes on driver information to relevant offices).  Officer fills in the necessary fields for driver condition  Officer clicks on the next button

 If unit is vehicle, results on the vehicle and the owner are presented.  If no results found, an empty form is presented  Officer makes the necessary changes on the vehicle information (it may be required to fill out another form to report the change of information of the vehicle)  Officer fills in the fields for vehicle condition  Office clicks on the next button

 If next unit is vehicle, similar steps are repeated. If next unit is pedestrian, results for pedestrian is presented.  Officer makes the necessary changes on the pedestrian information.  Officer fills in the fields for pedestrian condition.

 If data on all units involved in the accident is entered, user can select to save and/or submit the report (There are save and submit buttons only on the last unit page)  Officer selects submit  Officer clicks on the print-out link and gets the printed form.  Officer signs the printed report.  Officer mails the printed report.

Information on the interfaces  Only black menu items can be selected. Red menu items are locked.  User has to quit the current menu in order to select other menu items.  Any time during filling the form user can save the report and quit application.  Main menu items are listed on the top frame.  Menu item options are listed on the left frame.  Results gathered on the driver, vehicle and pedestrians are by default non-editable. User needs to click on the edit button next to the related field to change data.  If results are not found for certain fields, these fields are presented as regular empty fields.  Menu item options presented in the left frame are blue. The option being used turns out white.  Reports are assigned OPS case no only after submitted.  Local case numbers should be entered by the user.