Running head: LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
Lab 1 – Defensive Driver Product Description - Rewrite
Barbara A. Dixon
CS410
Professor Janet Brunelle
Old Dominion University
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
2
Table of Contents
1
Introduction ....................................................................................................................3
2
Defensive Driver Product Description ...........................................................................5
2.1 Key Product Features and Capabilities ..........................................................................5
2.2 Major Components.........................................................................................................10
2.3 Target Market/Customer Base .......................................................................................11
3
Product Prototype Description .......................................................................................13
3.1 Prototype Introduction ...................................................................................................13
3.2 Prototype Function Goals and Objectives......................................................................15
3.3 Prototype Architecture ...................................................................................................19
3.4 Prototype Features and Capabilities...............................................................................20
3.5 Prototype Development Challenges ...............................................................................20
Figures
Figure 1: Real-World Product Input/Output Processing Diagram ........................................8
Figure 2: Real-World Product Process Flow ........................................................................9
Figure 3: Real-World Product Major Function Component Diagram ..................................11
Figure 4: Prototype Input/Output Processing Diagram ........................................................18
Figure 5: Prototype Process Flow .........................................................................................19
Figure 6: Prototype Major Functional Component Diagram ................................................20
Tables
Table 1: Real-World Product and Prototype Comparison ....................................................14
Glossary .................................................................................................................................21
References ..............................................................................................................................28
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
1
3
Introduction
According to the National Highway Traffic Safety Administration (NHTSA) (2008):
“Motor vehicle travel is the primary means of transportation in the United States,
providing an unprecedented degree of mobility. Yet for all its advantages, deaths
and injuries resulting from motor vehicle crashes are the leading cause of fatalities
accounting for nearly 95 percent of transportation-related fatalities.” (p. 1)
In 2008, the Virginia Department of Motor Vehicles (DMV) reported 36,000 car
accidents, which were caused by common bad driving habits (DMV 2008). According to
the NHTSA, there were 37,261 fatal accidents in 2008, with the majority of those drivers
being 15 to 20 years of age (NHTSA 2008). In addition to fatalities and injuries, the cost
of accidents is astronomical. According to CNN, the cost of accidents per year is $164.2
billion (Clifford 2008), with $40.4 billion of that being speed-related (NHTSA 2008).
Currently, standardized Driver monitoring methods are either limited or not available at
all. Analysis software to record and report a Driver’s habits is also non-existent. The
lack of monitoring methods and analysis software may hinder a motorist’s ambition to
drive safer.
According to Merriam-Webster’s dictionary, a habit is defined as “a behavior
pattern acquired by frequent repetition or physiologic exposure that shows itself in
regularity or increased facility of performance” (Merriam-Webster). It can also be
described as “an acquired mode of behavior that has become nearly or completely
involuntary” (Merriam-Webster). Currently, to acquire a driver’s license in Virginia, the
applicant must first obtain a learner’s permit. This requires that the applicant be at least
15 years and six months of age and pass a written driver’s test. The applicant then
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
4
completes book and driving courses, whether these are offered through the public school
system or a private driving class. After completion of the driving course, the applicant
must complete a Department of Motor Vehicles (DMV) road test, and upon successful
completion, a judge will grant the applicant a driver’s license. After obtaining the
driver’s license, the Driver must also obtain automobile insurance. Throughout this
process, there is no tangible way to ensure safe consistent driving habits. In driving
courses, the motorist learns the proper techniques of driving from a ride-along instructor,
but does not have sufficient time to acquire safe driving habits. A Driver’s habits are
only realized to be unsafe when a ticket or citation is issued. In many cases, a traffic
citation will result in a Judge ordering the Driver to attend a driving clinic. A driving
clinic is a means of rehabilitation to refresh the Driver with proper driving techniques.
Sentinel Inc. has designed The Defensive Driver, which provides the Driver with
a means to monitor, record and analyze their driving habits. Initially, the Driver must
create a profile that will be used for authentication. While driving, the Defensive Driver
will monitor particular driving factors by using analysis of real-time sensor data. This
data will often be compared to reputable databases to determine if the Driver is
displaying improper or unsafe driving techniques. When the Driver is displaying these
techniques, the Defensive Driver will issue alerts, audio and/or visual, that will inform
the Driver about their unsafe driving. The patterns and alerts of the Driver will be
recorded and used for analysis of their driving habits. After the Defensive Driver learns
the motorist, it will be able to determine improvement in the Driver’s habits based on a
documented analysis.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
5
The Defensive Driver will primarily be used by driver education schools, both
driving courses and driving clinics, and insurance companies. Driver education courses
will utilize the Defensive Driver as a safe habit enforcer, to instill safe driving techniques
within new Drivers. Driver rehabilitation clinics will employ the Defensive Driver as a
tool to aid in the redevelopment of safe driving habits. Automobile insurance rates
usually increase when a traffic citation is issued. The Defensive Driver allows insurance
companies to determine whether a Driver is displaying safe driving habits and is possibly
eligible for lower insurance rates.
2
Defensive Driver Product Description
The overall goal of the Defensive Driver is to monitor and report a Driver’s
habits, to make them more aware of safe driving techniques. The Defensive Driver unit
will record, monitor and analyze a Driver’s techniques by interfacing with the vehicle’s
Engine Control Unit (ECU) and On-Board Diagnostic System (OBD-II). It will also
issue alerts to notify Drivers when they are driving unsafely. The information collected
will be analyzed and allow for report generation. The report will present the Driver’s
detailed habits to show where improvement is needed. The report will also allow the
Driver to focus their future driving efforts on improving their bad habits to become a
safer Driver.
2.1
Key Product Features and Capabilities
The Defensive Driver is based on the current methods and techniques of drivers
today. Currently, no system exists that is able to monitor and produce a report about a
Driver’s habits to aid in learning safer driving techniques. Once a Driver completes the
process to obtain a driver’s license, there is no continuous learning program that enforces
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
6
safe driving habits. The Defensive Driver’s features can assist in creating safer Drivers.
The Defensive Driver will use Real Time Monitoring, Driver Analysis and Driving
Profiling to monitor and report a Driver’s habits.
Real Time Monitoring will be incorporated into the Defensive Driver to ensure
that the data captured for the Driver is up-to-date. This will be accomplished by
developing monitoring algorithms and alert generation software to support the functions
of the system. The monitoring algorithms will be directly related to the Driver’s actions.
The Following Too Close algorithm will determine if the Driver is a safe distance behind
the vehicle directly in front of them by the use of sensors. The Seat Belt Usage algorithm
will determine if the Driver maintains a properly secured seat belt. The Erratic Lane
Changes algorithm will determine if the Driver is changing lanes frequently and within
certain coordinates. The Failure to Use Headlights algorithm will determine if the Driver
is utilizing the headlights on their vehicle during night time hours. The Speeding
algorithm will compare the Driver’s location and speed with the Speed Limit Database
provided by the Virginia Department of Transportation (VDOT) to determine if the
Driver is within the predetermined speed limit. The Stop Signs algorithm will compare
the Driver’s location and speed with the Stop Sign Database provided by the VDOT to
determine if the Driver has successfully stopped at a posted stop sign. The Alert
Generation feature will provide the Driver with notification that they have triggered an
event of unsafe driving. Real-time audio and visual alerts are offered within the
Defensive Driver. Upon initial setup, the Driver will be able to customize their alert
preferences.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
7
Driver Analysis and Driver Profiling are essential to the Defensive Driver. These
capabilities allow the system to learn the Driver’s habits, whether they be good or bad,
and monitor their habits to determine potential improvement. Driver Profiling allows the
system to identify specific characteristics and habits of the Driver, allowing for more indepth report generation to specify which bad habits the Driver displays. Driver Analysis
compares the initial data collection for the Driver and determines if they have exhibited
improvement.
The Real World Product Input/Output Processing Diagram (Figure 1) explains the
logic of the inputs and outputs for the On-Board Unit (OBU) and PC Software. This
incorporates the Real Time Monitoring, Driver Analysis and Driver Profiling (with
authentication) aspects of the system.
{This space is intentionally left blank.}
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
Figure 1: Real World Product Input/Output Processing Diagram
8
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
The Real World Product Process Flow (Figure 2) describes the general flow of
processes within the OBU.
Figure 2: Real World Product Process Flow
9
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
2.2
10
Major Components
The major components for the Defensive Driver are identified in Figure 3. This
diagram shows the hardware, software and interfaces that define the system. Most of the
hardware will be tailored to the needs of the Defensive Driver.
The primary components of the Defensive Driver are the GPS, fingerprint reader,
accelerometer, LCD touchscreen, OBD-II, flash memory, SD memory and audio
speakers. The OBU will essentially consist of a single LCD touchscreen display unit that
encompasses the CPU, internal memory, external memory, fingerprint reader, GPS, and
accelerometer. The primary inputs for the OBU will be the Stop Sign Database, Speed
Limit Database, GPS coordinates and information generated from the ECU. The outputs
of the OBU will be reports and alerts. The reports will provide a detailed analysis
capturing the events logged for the Driver. The alerts, audio and/or visual, will activate
only when it has been triggered that the Driver has displayed an event of unsafe driving.
The alerts generated will be recorded in the event log for each Driver.
{This space is intentionally left blank.}
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
11
Figure 3: Real World Product Major Functional Component Diagram
2.3
Target Market/Customer Base
The primary target market and customer base for the Defensive Driver are driver
schools and insurance companies. Sentinel Inc. may also try to incorporate the Defensive
Driver for future development efforts in courses designed for use by specialized Drivers
of school buses, tractor trailers and taxi cabs. Parents of inexperienced Drivers may also
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
12
want to invest in the Defensive Driver, to assist their child with developing safe driving
habits.
The targeted driver schools include driver education schools and driver
improvement clinics. The driver education schools may be of the private and public
sector. Driver education schools would benefit from utilizing the Defensive Driver
because it would aid them in monitoring and assist with providing an analysis of driving
habits for student Drivers. More often than not, attendance of a driver improvement
clinic is in reference to a conviction of a traffic violation. To benefit driver improvement
clinics, Sentinel Inc. is recommending that the Defensive Driver be installed in all
vehicles used for teaching, and require that a minimum number of safe driving hours be
logged by traffic offenders attending the clinic. This would assist in the overall
improvement efforts displayed by Drivers.
Automobile insurance is essential for Drivers. However, the cost of automobile
insurance is steadily increasing. According to CNN, on average, each American spends
about $1,000 per year for automobile insurance (CNN 2008). If you are a Driver that
excessively receives traffic violations, the cost of insurance will ultimately increase as the
availability of insurance decreases. Insurance companies will often offer incentives for
Drivers that maintain a good driving record, therefore Sentinel Inc. is targeting insurance
companies in hopes of having them offer the Defensive Driver as a device that may
potentially reduce insurance costs among consumers.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
3
13
Product Prototype Description
The prototype of the Defensive Driver will present a scaled-down version of the
Real-World Product. The goals will essentially be the same, such as real-time monitoring
and reporting, historical analysis, driver profiling and driver improvement monitoring.
Some of the algorithms and hardware components have been eliminated to allow for
rapid Prototype development. And, all driving will be simulated or conducted in a
controlled environment.
3.1
Prototype Introduction
Sentinel, Inc. will develop a Defensive Driver Prototype that will provide real-
time monitoring and reporting, historical analysis, driver profiling and driver
improvement monitoring. Table 1 describes the differences in features, hardware and
software. The real-time monitoring feature for the Real-World Product will provide realtime sensor data correlation when the vehicle is in motion, whereas the Prototype will
provide simulated sensor data correlation. The Erratic Lane Change, Failure to Use
Headlights and Improper Turn algorithms will all be eliminated from the Prototype. The
use of the accelerometer will also be removed from the Prototype. To demonstrate the
functionality of the Prototype, Sentinel Inc. will conduct a simulated driving session in a
controlled environment where the Driver is displaying unsafe driving techniques. The
Prototype will consist of a laptop and the Defensive Driver software. The laptop will
essentially represent the capabilities of the LCD Touchscreen, fingerprint reader, audio
speakers and integrated RAM and hard drive. The input from the OBD-II will be
simulated and the Speed Limit and Stop Sign Databases will be scaled-down to focus on
the specific location of the controlled environment.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
14
Table 1: Real-World Product and Prototype Comparison
Features
Real-time monitoring
Driver Analysis/Driver Profiling
Hardware
GPS
Fingerprint reader
Accelerometer
Distance Sensor
LCD Touchscreen
OBD-II
Flash and SD Memory
Audio Speakers
Software
Speed Limit Database
Stop Sign Database
GPS Coordinates
Erratic Lane Change Algorithm
Failure To Use Headlights
Algorithm
Improper Turns Algorithm
Following Too Close Algorithm
Seat Belt Usage Algorithm
Speeding Algorithm
Stop Sign Algorithm
Data Synchronization
Analysis Software
Final Product
Real-time sensor data correlation when
vehicle is in motion
Driving performance user profiling and
analysis
Final Product
On-board Unit (OBU) embedded receiver
Embedded in OBU
OBU component
OBU component
OBU Display component
OBU Interface
OBU internal/external memory
OBU component
Final Product
Microsoft Access database to be
provided by VDOT
Microsoft Access database to be
provided by VDOT
Lat/Long obtained by embedded GPS
receiver
Data Processing Module component
Data Processing Module component
Prototype
Simulated sensor data correlation with
pre-loaded inputs
Driving performance user profiling and
analysis
Prototype
External receiver with USB interface
Laptop component
Not in prototype
External sensor with USB interface
Laptop display
Simulated database input
Laptop memory
Laptop speakers
Prototype
Database of sample speed limit data
Data Processing Module component
Not in prototype
Database of sample stop sign data
Lat/Long obtained by external GPS
receiver
Not in prototype
Not in prototype
Fully functional
{This space is intentionally left blank.}
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
3.2
15
Prototype Functional Goals and Objectives
The overall goals of the Prototype are similar to those of the Real-World Product,
also incorporating ease of use for the Driver. The goals are to accurately demonstrate the
efficiency of the algorithms and analysis methods, mitigate risks and develop a
preliminary user manual. The efficiency of the algorithms and analysis methods will rely
heavily on the accuracy of the inputs. The risks with the highest impact are the inability
to accurately design the Following Too Close algorithm and the inability to effectively
learn the Driver. The possibility that the algorithms produce false positives, ultimately
identifying an unsafe Driver as being safe also poses a risk. The development of a
preliminary user manual will allow the customer to utilize the product to its full
capability.
The objectives of the inputs are to accurately provide data that is useful for the
product development. For the Defensive Driver, the inputs will come from the Stop Sign
Database, Speed Limit Database, GPS coordinates, and simulated seat belt and OBD-II
data. The Stop Sign and Speed Limit Databases will be provided by the Virginia
Department of Transportation.
The outputs of the device will be alert and report generation. Alerts, audio and/or
visual, will be activated once the algorithm detects an unsafe driving technique. The
logged driving information is captured and report can be generated by the Driver.
The test harness will encompass a display that provides the Driver’s current
speed, the posted speed, as retrieved from the Speed Limit Database, and generates a
recommended safety distance that is determined by braking patterns and GPS
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
16
coordinates. The test harness will also issue alerts, audio and/or visual, that warns the
Driver when they have performed an unsafe driving technique. The test harness also
allows the Driver to develop their initial profile.
The flows of the inputs and outputs are described in Figure 4. And, the flows of
the process are described in Figure 5.
{This space is intentionally left blank.}
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
Figure 4: Prototype Input/Output Processing Diagram
17
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
Figure 5: Prototype Process Flow
18
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
3.3
19
Prototype Architecture
The hardware for the Prototype is a laptop that interfaces with a GPS receiver.
The software algorithms, analysis software and databases provide a solid foundation to
accurately perform the features of the Defensive Driver. The information from the Speed
Limit and Stop Sign Databases, the simulated GPS and ECU data, will be directly related
to the actions of the algorithms. The Prototype architecture is described in Figure 6.
Figure 6: Prototype Major Functional Component Diagram
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
3.4
20
Prototype Features and Capabilities
The features and capabilities of the Prototype are designed to provide a concrete
model for which the Real-World Product will be created. Risk mitigation must be
addressed to eliminate the occurrence of false positives. Real-time monitoring and
reporting is one of the major innovative aspects identified by Sentinel Inc. The historical
analysis, driver profiling and monitoring driver improvement all aim to provide the
Driver with a safer experience.
3.5
Prototype Development Challenges
During the development phase of a product, challenges exist and need to be
addressed to minimize the adverse effects. For the Defensive Driver Prototype, reliable
performance of the GPS receiver and consistent memory access may have a negative
impact if the resources are not properly attained. The analysis software generating false
positives is also a development challenge. For customers, confidence in a product is
essential. With any new product development, integration of hardware and software
components will always be an issue. In order for the Defensive Driver to be legally
binding, standards and regulations must be adhered to. If these standards and regulations
are constantly changing, it will be difficult to develop a product that will meet the
criteria.
{This space is intentionally left blank.}
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
21
Glossary
Accelerometer: An instrument for measuring acceleration or for detecting and
measuring vibrations.
ALDB: Abbreviation for Alerts and Logs Database. A database used on both On-Board
Unit and Client Software which allows for historical data storage of users and their data.
Algorithms: A set of algorithm provided to evaluate the safety of an individual’s driving
habits. Implemented within the Runtime Data Processing Module.
CF: An abbreviation for Compact Flash. A non-volatile type of memory that is
commonly used for Operating System and firmware storage of devices.
(the) Client Software: Software components of the Defensive Driver which will run on a
customer’s PC and provide profiling and reporting capabilities.
CPU: An abbreviation for Central Processing Unit. The microprocessor of both a
customer’s PC and the Defensive Driver On-Board Unit.
Defensive Driver: The Defensive Driver is a proposed solution to evaluate the current
driving habits of an individual and equip him with a long-lasting set of safe driving skill.
Defensive Driver Prototype: A modeled environment which will serve as a test-bed for
Defensive Driver product. The environment will processor simulated and real-time input
apply appropriate algorithms and generate output. Goal is proving functionality of the
real-world product.
(the) Device: See Defensive Driver.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
22
Disk Drive: See Hard Drive.
DMS: Driver Monitoring Station. The PC of each client where the Client Software will
be installed.
DMV: An abbreviation for Department of Motor Vehicles.
Driver Education: Class that teaches new drivers how to properly drive.
Driver Improvement Clinics: An education institution that rehabilitates drivers with bad
habits.
Driver Profile: All historical data on a driver.
Driving Attributes: Reflexes, and reaction times relevant to a driver.
DSM: An abbreviation for Database Synchronization Module. The component of the
Client Software that will ensure database consistency.
Erratic Lane Change: Changing lanes erratically.
ECU: An abbreviation for Engine Control Unit. The main microcontroller within a
vehicle that coordinates numerous driving parameters and exports them to external
devices.
End-User: Driver behind the wheel.
False Positives: Recording of an infraction that did not actually happen.
Feedback: See Performance Report.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
23
(the) Fingerprint Reader: A scanning sensor for reading biometrical user data and
provide and authentication layer for the Defensive Driver.
Flash Memory: See CF.
GUI: An abbreviation for Graphic User Interface. GUI refers to the displaying for the
informative reports.
Historical Data: Data recorded on the Logs and Alerts Database; kept for future
reference and profile updates.
GPS: An abbreviation for Global Position System. A GPS receiver will be embedded
within the On-Board Unit to allow location tracking of a vehicle in motion.
Hard Drive: The non-volatile memory storage of a computer system.
Infraction: The breaking of a traffic law.
Insurance Companies: Risk management company.
Internet: Global system of connected computer networks.
(the) Laptop: See LCU.
LCD: An abbreviation for Liquid Crystal Display. A display technology that will be used
for the On-Board Unit of the Defensive Driver.
LCU: An abbreviation for Laptop Computer Unit. The main hardware component of the
Defensive Driver Prototype. The laptop will be used to provide the hardware and
software integration for the prototype.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
24
MFCD: An abbreviation for Major Functional Components Diagram. A diagram
representing the main integral elements of the design of a product.
NHTSA: An abbreviation for National Highway Transportation Safety Administration. A
branch of the Department of Transportation involved with establishing safety requirement
in the US automobile industry.
OBD-II: On-Board System. The interface that provides data access to the Engine Control
Unit of a vehicle.
OBU: Abbreviation for On-Board Unit. The hardware component of the Defensive
Driver that will reside inside of a vehicle. This unit will provide real-time monitoring of a
driver’s performance.
OS: An abbreviation for Operating System. The first application that loads when a
computer starts and facilitates the communication between devices and user.
PC: An abbreviation for Personal Computer. Each customer will need to provide a PC
station for installation of the Client Software.
Performance Report: Report generation capabilities presenting the current performance
statistics regarding the safety habits of an end-user.
(the) Profile: A user-specific set of information referring to his long-turn performance.
(the) Prototype: See Defensive Driver Prototype.
RAM: Random Access Memory. A form of volatile computer storage memory.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
25
RDPM: An abbreviation for Runtime Data Processing Module. The main component of
the OBU’s software application.
RWP: Real-World Product. The final result of the Defensive Driver initiative.
SD: An abbreviation for Secure Digital. A non-volatile type of memory that is available
if large sizes and used for portable devices storage.
SDHC: An abbreviation for Secure Digital High Capacity. A version of Secure Digital
memory that provides for large size inexpensive memory banks to be manufactured.
Sensor: Device that measures some physical quantity.
Sensor Network: Network of distributed sensors.
Speed Limit Database: A database that will store location of posted speed limits. A
copy will be stored on the On-Board Unit for real-time speed comparison. It will be later
updated to reflect new speed signs for the value modifications of current signs in a certain
region.
Stop Sign Database: A database that will store location of posted stop limits. A copy
will be stored on the On-Board Unit for real-time stop sign detection. It will be later
updated to reflect new speed addition or removal of stop signs in a certain region.
(the) System: See Defensive Driver.
Tailgating: Driving too closely behind a vehicle.
Test Harness: Software module of the Defensive Driver Prototype which will be used to
generate sample data sets and test overall algorithm and feature operations.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
26
Touch Screen: A functionality of a display unit to provide user input through physical
contact of a finger or stylist. Will be used as a part of the user input for the On-Board
Unit of the Defensive Driver.
(the) Unit: See OBU
USB: Universal Serial Bus. A standard interface for host and devices interconnectivity.
VDOT: An abbreviation for Virginia Department of Transportation. Government agency
responsible for maintaining roads and bridges in Virginia.
LAB 1 – DEFENSIVE DRIVER PRODUCT DESCRIPTION
27
References
Clifford, Catherine. (2008). U.S. Car Accident Cost: $164.2 billion. Retrieved from
http://money.cnn.com/2008/03/05/news/economy/AAA_study/
Habit. (n.d.). In Merriam-Webster online. Retrieved from http://www.merriamwebster.com/
National Highway Traffic Safety Administration (NHTSA) (2008). Traffic Safety Facts.
Retrieved from http://www-nrd.nhtsa.dot.gov/Pubs/811162.PDF
Virginia Department of Motor Vehicles (DMV) (2008). Driver action contributing to the
crash. Retrieved from
http://www.dmv.state.va.us/webdoc/safety/crash_data/total/pdf/driver_action.pdf