Running head: LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER... Lab 4 – Defensive Driver Prototype User Manual

Running head: LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER MANUAL

Lab 4 – Defensive Driver Prototype User Manual

Sentinel, Inc.

CS411

Professor Janet Brunelle

Old Dominion University

LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER MANUAL 2

Table of Contents

1 Introduction ................................................................................................................. 5

1.1 Defensive Driver Objectives and Goals ............................................................... 7

2.1 Laptop Control Unit Power .................................................................................. 9

2.2 Connect External Hardware Devices ................................................................. 10

2.2.1 Distance Sensor ........................................................................................... 10

2.2.2 GPS Receiver .............................................................................................. 11

3 Using the Prototype ................................................................................................... 13

3.1 OBU Software .................................................................................................... 13

3.1.1 Fingerprint Authentication and New User Setup ........................................ 14

3.1.2 Dashboard ................................................................................................... 15

3.1.2.1 Owner Information .................................................................................. 16

3.1.2.2 About Information ................................................................................... 17

3.1.2.3 Driver Information .................................................................................. 18

3.1.3 Simulation ................................................................................................... 19

3.1.3.1 Alert Detection ........................................................................................ 20

3.2 Client Software ................................................................................................... 22

3.2.1 Alert Generation.......................................................................................... 32

3.2.1.1 Seat Belt Alert ......................................................................................... 32

3.2.1.2 Stop Sign Alert ........................................................................................ 32


3.2.1.3 Distance Detection Alert ......................................................................... 32

3.2.1.4 Speeding Algorithm Alert .......................................................................... 33

4 Error Messages .......................................................................................................... 33

4.1 Invalid Username/Password ............................................................................... 33

4.3 Database Synchronization .................................................................................. 33

4.4 Hardware ............................................................................................................ 34

5 Glossary of Terms ..................................................................................................... 35

6 References ................................................................................................................. 40

Figures

Figure 1: Prototype Major Functional Components Diagram ............................................ 8

Figure 2: LCU Power Button .............................................................................................. 9

Figure 3: LCU Welcome Screen ....................................................................................... 10

Figure 4: Go! Motion Distance Sensor ............................................................................. 11

Figure 5: GPS Driver ........................................................................................................ 12

Figure 6: GPS Receiver .................................................................................................... 13

Figure 7: Welcome Screen ................................................................................................ 14

Figure 8: New User Display ............................................................................................. 15

Figure 9: Driving Display ................................................................................................. 16

Figure 10: Owner Information Display............................................................................. 17

Figure 11: About Information Display ............................................................................. 18

Figure 12: Driver Information Display ............................................................................. 19

Figure 13: Ignition Display ............................................................................................... 19

Figure 14: Speeding Alert Display ................................................................................... 20


Figure 15: Stop Sign Alert Display ................................................................................... 21

Figure 16: Following Too Close Alert Display ................................................................ 21

Figure 17: Administrator Welcome Screen ...................................................................... 22

Figure 18: Invalid Login Display ...................................................................................... 23

Figure 19: List of Drivers Display .................................................................................... 24

Figure 20: Driver Profile Display ..................................................................................... 25

Figure 21: Following Too Closely Alerts Display ............................................................ 26

Figure 22: Stop Sign Alerts Display ................................................................................. 27

Figure 23: Seatbelt Alerts Display .................................................................................... 28

Figure 24: Driver Analysis Display .................................................................................. 29

Figure 25: New Driver Display......................................................................................... 30

Figure 26: About Information for Administrator Interface............................................... 31

Figure 27: Database Synchronization Error ...................................................................... 34

Figure 28: Distance Sensor Error ...................................................................................... 34

Figure 29: GPS Receiver Alert ......................................................................................... 35

[This Space Intentionally Left Blank]


1 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 4 – DEFENSIVE DRIVER PROTOTYPE USER MANUAL 6 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.


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.

1.1 Defensive Driver Objectives and Goals

Sentinel Inc. is developing a prototype that demonstrates the essentials of the

Defensive Driver. The Prototype will prove that it is possible to record and analyze from a GPS Receiver and Distance Sensor to simulate driving scenarios. The prototype will also show that it can provide a historical analysis of the Driver’s habits (both good and bad). The Prototype will provide real-time monitoring and reporting, historical analysis, driver profiling and driver improvement monitoring. The major components for the

Defensive Driver are identified in Figure 1. This diagram shows the hardware, software and interfaces that define the system.


LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER MANUAL

Figure 1: Prototype Major Functional Components Diagram

8

The Prototype of the Defensive Driver will simulate the features and capabilities of the Real-World Product. The purpose of the Prototype is to show that the Defensive

Driver can be developed and that it is easy to use. The Prototype will use a Laptop

Control Unit (LCU), GPS Receiver and Distance Sensor to simulate driving scenarios and provide feedback to the end user. While in motion, the Driver is notified of an alert if they have demonstrated a violation. When this alert is generated, it is recorded as an event in the Alerts and Logs Database, and will be analyzed for report generation.

2 Getting Started

Before you begin using the Defensive Driver prototype, you must first connect power to the Laptop Control Unit (LCU). The LCU will require use of Windows 7 as an


Operating System. You will then connect the Distance Sensor and GPS Receiver to the

LCU.

9

2.1 Laptop Control Unit Power

To power on the Laptop Control Unit (LCU), complete the following steps:

Step 1: Open the LCU Display

Step 2: Press the power button located on top right corner of LCU (as shown in Figure

2).

LCU Power Button

Figure 2: LCU Power Button



Step 3: If Welcome Screen is not displayed as shown in Figure 3, repeat steps 1 and 2.

Figure 3: LCU Welcome Screen

Step 4: Enter password to logon.

2.2 Connect External Hardware Devices

To complete Defensive Driver hardware setup, connect the Distance Sensor and

GPS Receiver. The Distance Sensor and GPS Receiver will provide the real-time information needed to conduct the Defensive Driver simulation.

2.2.1 Distance Sensor

The Distance Sensor will report distance information to the OBU through a USB connection. To install the Distance Sensor, complete the following steps:


Step 1: Insert Go! Motion Plus Distance Sensor’s male USB connector into the female

USB port on the LCU (as shown in Figure 4).

Step 2: Insert opposite end of cable into the Go! Motion Plus Distance Sensor.

Step 3: The LCU will automatically recognize the hardware and install the driver.

Step 4: If hardware is not recognized, unplug USB connection from LCU and repeat Step 1.

Figure 4: Go! Motion Distance Sensor

11

Connects to

Distance Sensor

Connects to LCU

2.2.2 GPS Receiver

The GPS Receiver will gather GPS Coordinates in real-time and send the information to the OBU.

Step 1: Insert Defensive Driver Software Disk into LCU.

Step 2: Click on LCU Start Menu, Click on Computer, right click CD/DVD drive and select Explore.


Step 3: Double click the “PL2303_Prolific_DriverInstaller_v110” file, which is the BU-

353 GPS driver (Figure 5).

Figure 5: GPS Driver

Step 4: Click the “Next” button to install the driver. If installation fails, repeat Steps 1 through 4.

Step 5: Insert the GPS’s male USB connector into the female USB port on the LCU (as shown in Figure 6).



Figure 6: GPS Receiver

Connects to LCU

13

3 Using the Prototype

To use the Defensive Driver Prototype, the On-Board Unit (OBU) Software and

Client Software will be accessed. The OBU Software will provide fingerprint authentication, new user setup, and will display the main driving dashboard. The OBU software will also encompass the simulation. The Client Software will provide the

Administrator Interface allowing for analysis of driving history.

3.1 OBU Software

The OBU Software will be the main interface for Drivers. This will allow the

Driver to login and show the main driving dashboard. The main driving dashboard will show the user’s driving session and display alerts as generated.


3.1.1 Fingerprint Authentication and New User Setup

When first starting the OBU software, you will be prompted with a Fingerprint

Authentication screen. New Users will need to select the “New User” button.

Step 1: Swipe your finger on fingerprint reader (as prompted by Figure 7).

Figure 7: Welcome Screen

14



Step 2: If you are a new user, please enter your first name and last name (as prompted by

Figure 8).

Figure 8: New User Display

Step 3: Press the “OK” button when finished.

3.1.2 Dashboard

Once the User logs in or creates a new account, the Driving Display (Figure 9) will be shown. The Driving Display shows the Following Distance, Posted Speed Limit, the User’s Current Speed and Seatbelt Engagement. It also shows buttons for Owner

Information, Unit Information (About) and Driver Information. The information displayed for Following Distance, Posted Speed Limit, User’s Current Speed and Seatbelt

Engagement will be generated from the driving scenario. This information will update in real-time.



Figure 9: Driving Display

16

3.1.2.1 Owner Information

If it becomes necessary to access Owner Information (Figure 10), use the following steps:

Step 1: Click on the “Owner Information” button.

Step 2: The Owner’s name, address, website (if available), email address and phone number.

Step 3: Click the “Back” button to go back to the Driving Display.



Figure 10: Owner Information Display

17

3.1.2.2 About Information steps:

To learn more about the Defensive Driver unit (Figure 11), use the following

Step 1: Click on the “About Information” button.

Step 2: The Unit Number associated with the device, the version of the software and the

Copyright information will be displayed.




Figure 11: About Information Display

18

3.1.2.3 Driver Information

To learn more about the Driver (Figure 12), use the following steps:

Step 1: Click on the “Driver Information” button.

Step 2: The Driver’s name, mailing address, Instructor name, School name and the number of hours driven are displayed.




Figure 12: Driver Information Display

19

3.1.3 Simulation

The ignition display (Figure 13) will allow the Driver to start and stop the session.

The driving session will not begin until the “Start” button is depressed. When the simulation is complete, or needs to be halted, the Driver will depress the “Stop” button.

Step 1: Click on the “Start” button. This will start the driving session.

Step 2: To end the driving session, click on the “Stop” button.

Figure 13: Ignition Display


3.1.3.1 Alert Detection

Once the session is started, the Driver will be shown alerts that are triggered by speed, stop sign, following too closely and seatbelt engagement events. For alerts generated by speeding, the window shown in Figure 14 will be displayed. It will display the posted speed limit and the Driver’s current speed and advise the Driver to slow down to the posted speed limit.

Figure 14: Speeding Alert Display

For alerts generated by failing to abide by a stop sign, the window shown in Figure 15 will be displayed. It will advise the Driver to come to a complete stop for at least three seconds or until the intersection is empty.



Figure 15: Stop Sign Alert Display

21

For alerts generated by following too close, the window show in Figure 16 will be displayed. It will show the Driver’s following distance, current speed and advise the

Driver to slow down to increase the following distance.

Figure 16: Following Too Close Alert Display

Step 1: Read alert.

Step 2: Follow advice given by alert.

Step 3: Click on the “!” to acknowledge the alert.


3.2 Client Software

The Client Software enables the Owner/Administrator to view the Drivers associated with them. It also allows the Owner to analyze the Driver’s history. To log into the Defensive Driver’s Administrator Interface (as shown in Figure 17):

22

Step 1: Enter your username and password in the indicated text boxes.

Step 2: Click Login.

Figure 17: Administrator Welcome Screen



If the Driver enters incorrection information, an error message will appear (as shown in

Figure 18).

Figure 18: Invalid Login Display

23



If the Owner/Administrator logs in correctly, a list of Drivers associated with them will be displayed (as shown in Figure 19).

Figure 19: List of Drivers Display

24

Step 1: To select a driver, scroll through the list, highlight their student number/name and press the select button. Or type their student number or name into the search field and press the search button, then press the select button.

Step 2: The Driver Profile will be displayed (as shown in Figure 20).

Step 3: To view all the alerts generated for a Driver during a session, click the “Collect

Alerts” button.


The Driver Profile displays the Driver name, phone number, email address and mailing address. Each alert generated is displayed by category. For Speed Limit Alerts, the date the event occurred, the duration of event, the speed recorded at time of event and the posted Speed Limit are displayed (as shown in Figure 20).

Figure 20: Driver Profile Display



For the Following Too Closely Alerts tab, the date the event occurred and the duration of the event are displayed (as shown in Figure 21). Only alerts of this specific type will be shown in this window. In addition, the events displayed will only be relevant to the

Driver shown at the top of the window.

Figure 21: Following Too Closely Alerts Display



For the Stop Sign Alerts tab, the date the event occurs is displayed (as shown in Figure

22). Only alerts of this specific type will be shown in this window. In addition, the events displayed will only be relevant to the Driver shown at the top of the window.

Figure 22: Stop Sign Alerts Display

27



For Seatbelt Alerts tab, the date the event occurred and the duration of event are displayed (as shown in Figure 23). Only alerts of this specific type will be shown in this window. In addition, the events displayed will only be relevant to the Driver shown at the top of the window.

Figure 23: Seatbelt Alerts Display



Step 4:

Click the “Driver Analysis” button to generate the report for the Driver.

The Driver Analysis Display (as shown in Figure 24) shows the Driver name, the date range of the report, the calculated Total Driving Points, the Points Per Hour and the Total

Driving Time.

Figure 24: Driver Analysis Display



To add a new Driver, use the following steps (as shown in Figure 25):

Step 1: Click on “File” and select “New”

Step 2: Enter the Driver’s first and last name.

Step 3: Enter the Driver’s mailing address.

Step 4: Click “Save” button to add the new Driver to the database.

Figure 25: New Driver Display

30



To learn more about the Defensive Driver Administrator Interface (Figure 26), use the following steps:

Step 1: Click on “Help” and select “About.”

Step 2: The Owner name, mailing address, website, email address and software version will be displayed.

Figure 26: About Information for Administrator Interface

31



3.2.1 Alert Generation

Alerts will be issued when Driving Events occur. An alert is generated for each detection algorithm. The Seat Belt Alert, Stop Sign Alert, Distance Detection Alert and

Speeding Algorithm Alert will be displayed on the On-Board Unit in real-time.

3.2.1.1 Seat Belt Alert

The seatbelt alert icon, shown in Figure 9, will appear red when the Driver’s seatbelt is disengaged. The Alert will show that the Driver needs to engage their seat belt. The alert will be disarmed, shown by the icon appearing green, when the Driver reengages their seatbelt.

3.2.1.2 Stop Sign Alert

A Stop Sign Alert window will be generated when the Driver fails to stop at a

Stop Sign (as shown in Figure 15). The Alert will notify the Driver that they need to make a Complete Stop at each Stop Sign. The Driver may click on the Alert window.

After clicking the window the Alert will exit. The alert can also be disarmed by the

Driver by correcting their driving behavior. However, the event will still be recorded into the Driver Profile database.

3.2.1.3 Distance Detection Alert

A Distance Detection Alert window will be generated when the Driver follows another vehicle too closely (as shown in Figure 16). The Alert will notify the Driver of the calculated Safe Driving Distance and that they should maintain it. The Driver may click on the Alert window. After clicking the window the Alert will exit. The alert can

LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER MANUAL 33 also be disarmed by the Driver by correcting their driving behavior. However, the event will still be recorded into the Driver Profile database.

3.2.1.4 Speeding Algorithm Alert

A Speeding Alert window will be generated when the Driver’s current speed is greater than the posted Speed Limit (as shown in Figure 14). The Alert will notify the

Driver of the Posted Speed Limit that they should follow. The Driver may click on the

Alert window. After clicking the window the Alert will exit. The alert can also be disarmed by the Driver by correcting their driving behavior. However, the event will still be recorded into the Driver Profile database.

4 Error Messages

Error messages can be displayed when the Driver inputs incorrect information or when incorrect information is received by the Defensive Driver. These error messages will always be visually displayed. The following subsections describe possible error messages.

4.1 Invalid Username/Password

If the Driver enters incorrection information, an error message will appear (as shown in Figure 18).

4.3 Database Synchronization

If the Database Synchronization Module does not properly establish a connection to the Client Software or OBU databases, an error message is displayed to the User stating which database exhibits the error (as shown in Figure 27).


Figure 27: Database Synchronization Error

34

4.4 Hardware

If the Distance Sensor is not properly recognized by the LCU, a message is displayed stating that the device is not connected (as shown in Figure 28). The User should check all USB connections and if still not working, disconnect the device and refer to Section 2.2.1 to reconnect device.

Figure 28: Distance Sensor Error


If the GPS Receiver is not properly recognized by the LCU, a message is displayed stating that the device is not connected (as shown in Figure 29). The User should check all USB connections and if still not working, disconnect the device and refer to Section 2.2.2 to reconnect device.

Figure 29: GPS Receiver Alert

35

5 Glossary of Terms

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.

(the) Box: A specific set of coordinates on a map that will identify a maximum posted speed limit and stop sign location.

Algorithms: A set of algorithms 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 skills.

Defensive Driver Prototype: A modeled environment which will serve as a test-bed for

Defensive Driver product. The environment will process 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.

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.

(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.

37


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.

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. Specifically, the agency directs the highway safety and consumer programs established by the National Traffic and Motor Vehicle Safety Act of

1966, the Highway Safety Act of 1966, the 1972 Motor Vehicle Information and Cost

Savings Act, and succeeding amendments to these laws.

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.

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.

SDRAM: An abbreviation for Synchronous Dynamic Random Access Memory.

A type dynamic random access memory card that allows for easy transfer of data to computer devices.

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.

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.

6 References

CS410 Defensive Driver Documentation

CS411 Lab 1 – Defensive Driver Product Description

CS411 Lab 2 – Defensive Driver Prototype Specification

CS411 Lab 3 – Defensive Driver Prototype Test Plan/Procedure

Go! Motion Distance Sensor. Retrieved from http://www.vernier.com/go/gomotion.html

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

Virginia Department of Motor Vehicles (DMV). Virginia Driver Manual.

1 Jan 2010.


Running head: LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER... Lab 4 – Defensive Driver Prototype User Manual

Related documents

Products

Support

Running head: LAB 4 – DEFENSIVE DRIVER PROTOTYPE USER... Lab 4 – Defensive Driver Prototype User Manual

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib