1. Conceptual Model of Alabama Law Enforcement Traffic Crash Report System By: Wanda Eugene Kinnis Gosha Andrea Williams

2. System Description When an accident occurs in Alabama, law enforcement officers record accident information onto a crash report form. This crash report system is designed for Alabama law enforcement officers to enter crash information recorded from that crash report form into a database containing all other crash report information for the state of Alabama with ease and accuracy.

3. System Specifications Software –System must mimic actual report form in order to maintain user comfort ability and familiarity. –System must be user friendly (novice users) –System must be secure and only accessible by Alabama law enforcement officers. Hardware –System must be compatible with existing PCs at the station –System must also be able to be run from a tablet PC with same accuracy and ease.

4. Task Scenario/Prototype

5. Task 1 Officer Seals arrives at the scene of an accident. As is custom, Officer Seals takes out her crash report form and starts recording the crash information on the form. To the left you can see the report form. Actual Report Form Task 2 Officer Seals must now go back to the station and record this information from the report form into the traffic crash report system.

6. Welcome message Officer Login Question Section Here users can send comments or questions to designers about the system Task 3 Officer Seals is back at the station and is greeted by this Welcome Page from the Alabama Highway Traffic Citation Entry System. Officer Seals enters her login information and is guided to the next page where she can then begin her accident reporting.

7. Task 4 Officer Seals is given the option of recording a citation, completing an unfinished citation, etc. Today Officer Seals only wants to record her new accident report so she clicks add a new citation. She is then guided to the next page where she can begin reporting her new citations. Officer is given options on which step to take next: Add new citation, complete unfinished citation, add comments to existing citation, etc. Officer can search database by different categories to find existing records or even compare notes. Log off option Officers can read Tip of the Day, which gives them tips about the system.

8. Task 5 Officer Seals is now at the Location page where she enters the time and location of the accident. Since the system mimics the actual report form, Officer Seals enters the information quickly and with ease. Tab showing driver/vehicle information, also gives review option Officer is given the option to save the report as a draft, reset the form or go to the next page. Drop down boxes save officer time of entering information into each box.

9. Task 6 Officer Seals begins entering the first driver’s information, when she gets a call about another accident. She must now save this report because she cannot finish it. She goes to save draft and is guided to another page confirming her decision.

10. Task 7 Before seeing a confirmation page, Officer Seals sees a warning page prompting her to make another decision, whether to submit the report (yes, finish), go back to the report (no, go back), or to continue saving the report as a draft. Officer Seals continues saving it as a draft.

11. Task 8 Officer Seals then receives an affirmative feedback message saying her task has completed and she can either return to the homepage or logoff. She logs off and goes to another accident scene to start the process all over again.

12. Additional Notes The prototype shown in the task scenario does not include all the functionality and capabilities of the system. To see the actual prototype, go to: http://www.goshanet.com/csci/classes/userinterface/index.html