Running head: LAB 3 – PROTOTYPE TEST PLAN/PROCEDURE
Lab 3 – Defensive Driver Prototype Test Plan/Procedure
Barbara A. Dixon
CS410
Professor Janet Brunelle
Old Dominion University
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
2
Table of Contents
1
Objectives .................................................................................................................... 3
2
References ................................................................................................................... 4
3
Test Plan ...................................................................................................................... 4
3.1 Testing Approach ........................................................................................................ 5
3.2 Identification of Tests .................................................................................................. 6
3.3 Test Schedule ............................................................................................................. 14
3.4 Fault Reporting and Data Recording ......................................................................... 15
3.5 Resource Requirements ............................................................................................. 15
3.6 Test Environment ...................................................................................................... 16
4
Test Responsibilities .................................................................................................. 16
5
Test Procedures.......................................................................................................... 17
5.1 Test Case Names and Identifiers ............................................................................... 18
6
Traceability to Requirements..................................................................................... 50
List of Figures
Figure 1: Prototype Major Functional Components Diagram ........................................... 5
Figure 2: E&CS Conference Room Layout ..................................................................... 16
List of Tables
Table 1: Identification of Tests ..............................................................................................7
Table 2: Test Schedule ...........................................................................................................14
Table 3: Fault Reporting and Data Recording .......................................................................15
Table 4: Test Responsibilities ................................................................................................17
Table 5: Traceability Matrix ..................................................................................................51
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
1
3
Objectives
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.
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). 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 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
2
4
References
CS410 Defensive Driver Documentation
CS411 Lab 1 – Defensive Driver Product Description
CS411 Lab 2 – Defensive Driver Prototype Specification
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.
3
Test Plan
Sentinel, Inc. is developing a prototype that demonstrates the essentials of the
Defensive Driver. The test plan will analyze and check the functionality of the Defensive
Driver Prototype. The test plan will test each demonstrational aspect of the prototype and
will identify the tests involved and the test schedule. It will also identify the resource
requirements, test environment and responsibilities of each team member. The test plan
will describe the test procedures to be demonstration. The prototype must meet
predefined expectations to be considered a successful prototype.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
3.1
Testing Approach
The functionality of the Defensive Driver prototype will be verified through test
cases developed by Sentinel, Inc. The test cases will validate the functionality of the
major functional components identified in Figure 1. The primary components of the
Defensive Driver Prototype are the GPS, fingerprint reader, accelerometer, LCD
touchscreen, OBD-II, flash memory, SD memory and audio speakers. The On-Board
Unit (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. Prototype
functionality will be proven by demonstrating all components successfully pass the test
cases described in Section 5.1.
{This space is intentionally left blank.}
5
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
Figure 1: Prototype Major Functional Components Diagram
3.2
Identification of Tests
The functionality of the Defensive Driver Prototype is verified through test cases
identified in Table 1. These test cases have been placed into one of four categories and
include a top level description of the test cases that will be performed for each category.
These test cases may prove one or more functional requirements specified for the
Defensive Driver Prototype. A more detailed description of each test case can be found
in Section 5.1.
{This space is intentionally left blank.}
6
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
7
Table 1: Identification of Tests
Cat ID
Description
Test Case #
Description
1
Hardware - BU-353 USB
GPS receiver
1.1
Verify GPS receiver is connected
properly
Verify GPS is recording information
in the correct GGA (Global
Positioning System Fix Data) format
1.2
2
3
Hardware - Vernier Go!
Motion Distance Sensor
Database Schema and
Interface
2.1
Verify Distance Sensor is connected
properly
2.2
Verify distance information is being
reported properly
3.1
Verify all fields are created correctly
3.2
Verify OBU database interface is
functional and allows for insertion
and retrieval of information from the
MySQL tables.
Verify Client Software database
interface is functional and allows for
insertion and retrieval of information
from the MySQL tables.
Verify DSM is functional and data is
properly propagated between the
Client Software database
NewSpeedLimit and NewStopSigns
tables and the OBU database
SpeedLimit and StopSigns tables.
Verify DSM is functional and data is
properly propagated between the
OBU database Log tables and the
Client Software database Log tables.
3.3
4
Database Synchronization
Module
4.1
4.2
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
5
6
Speed Limit Detection
Algorithm
Stop Sign Detection
Algorithm
8
5.1
Verify Input from Databases and
Sensors stays consistent
5.2
Verify Alert Generation occurs
properly
5.3
Verify Event Start/Stop Timer as
accurate
5.4
Verify Event Logging as accurate to
Logging Requirements
6.1
Verify Input from Databases and
Sensors stays consistent
6.2
Verify Alert Generation occurs
properly
6.3
Verify Event Start/Stop Timer as
accurate
6.4
Verify Event Logging as accurate to
Logging Requirements
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
7
8
9
Following Too Close
Algorithm
Seat Belt Algorithm
Algorithm Controller Class
9
7.1
Verify Input from Databases and
Sensors stays consistent
7.2
Verify Alert Generation occurs
properly
7.3
Verify Safe Driving Distance is
calculated properly using 4.0 meters
as an average car length
7.4
Verify Event Start/Stop Timer as
accurate
7.5
Verify Event Logging as accurate to
Logging Requirements
8.1
Verify Input from OBU Database as
consistent
8.2
Verify Alert Generation occurs
Properly
8.3
Verify Event Start/Stop Timer as
accurate
8.4
Verify Event Logging as accurate to
Logging Requirements
9.1
Verify all Event Detection
Algorithms are active
9.2
Verify all Event Detection
Algorithms are working in parallel
9.3
Verify Algorithm Start/Stop Timer as
accurate
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
10
Analysis Algorithm
10.1
10.2
10.3
10.4
10
Verify the frequency is collected for
Stop Sign Event;
Verify the duration is collected for
Following Too Closely, Speeding,
and Seat Belt Unengaged
Verify the weight is collected for
Stop Sign Violations, Following Too
Closely, Speeding, and Seat Belt
Unengaged
Verify the Driver Points are
calculated for Stop Sign Violations,
Following Too Closely, Speeding,
and Seat Belt Unengaged
Verify the Driver Points are collected
for each driving session/date
10.5
Verify Points Per Hour is calculated
10.6
Verify the date is collected for each
event recorded
10.7
Verify the report is generated
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
11
Graphical User Interface –
On-Board Unit
11
11.1
Verify login is displayed correctly,
login is successful for authorized
users and reject unauthorized users.
11.2
Verify a new user can be added
through the OBU
11.3
Verify the information about the
OBU is displayed correctly.
11.4
Verify the information about the
Owner is displayed correctly.
11.5
Driving Display Screen: Verify the
information to be displayed while the
user is driving is shown correctly.
11.6
Speed Limit Alert Screen: Verify the
alert is shown correctly when the
conditions for the alert are met.
11.7
Following Too Closely Alert Screen:
Verify the alert is shown correctly
when the conditions for the alert are
met.
Seat Belt Usage Alert Screen: Verify
the alert is shown correctly when the
conditions for the alert are met.
11.8
11.9
Stop Sign Alert Screen: Verify the
alert is shown correctly when the
conditions for the alert are met.
11.10
Driver Information Screen: Verify
the user's information is displayed
correctly.
11.11
Completed Session Screen: Verify
the session is saved correctly.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
12
Graphical User Interface –
Administrator
12.1
12.2
12
Login Screen: Verify login is
displayed correctly, login is
successful for authorized users and
reject unauthorized users.
About Screen: Verify the
information about the Administrator
Software is displayed correctly.
12.3
List of Units Screen: Verify each
unit associated with the current
administrator is listed correctly.
12.4
List of Drivers Screen: Verify each
driver associated with the current
administrator is listed correctly.
12.5
Driver Profile and Report Processing
Screen: Verify the information about
the driver is displayed correctly.
12.6
Display Alerts Screen: Verify all the
alerts issued to the driver are
displayed correctly.
12.7
Driver Analysis Screen: Verify the
driver analysis data is displayed
correctly.
12.8
Driver Statistics Screen: Verify the
driver statistics are displayed
correctly.
12.9
Alert Database Synchronization
Screen: Verify the button initiates
and completes the synchronization
process.
New Driver Screen: Verify a new
driver can be added through the
Administrator interface.
12.10
12.11
Stop Sign/Speed Limit Database
Synchronization Screen: Verify the
button initiates and completes the
synchronization process.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
13
Graphical User Interface –
Test Harness
13
13.1
Welcome Screen: Verify the
Welcome Screen is rendered
correctly.
13.2
Driver Controls Panel: Verify the
Driving Controls panel is rendered
correctly.
13.3
Speed Control: Verify the Speed
Control increases and decreases the
speed of the simulated car.
13.4
Seat Belt Toggle Switch: Verify the
Seatbelt Toggle Switch engages and
disengages the simulated seatbelt.
13.5
Steering Control: Verify the Steering
Control changes the direction of the
simulated car.
13.6
Braking Control: Verify the Braking
Control decreases the speed of the
car.
13.7
Display Alerts Window: Verify the
Display Alerts window shows all
alerts issued to the tester.
13.8
Instance of OBU Prototype: Verify
the Instance of the OBU Prototype is
displayed.
13.9
Road Control Panels: Verify the
Road Controls Panel is rendered
correctly.
13.10
Change Speed Limit Button: Verify
the Change Speed Limit button
works correctly.
13.11
Modify Space Between Vehicle
Button: Verify the Modify Space
Between Vehicle button works
correctly.
Add Stop Sign Button: Verify the
Add Stop Sign button works
correctly.
13.12
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
3.3
14
Test Schedule
Sentinel, Inc. is allowed 45 minutes to demonstrate the functionality of the
Defensive Driver Prototype. The first ten minutes of the demonstration will be used to
setup the Prototype and re-introduce the scope of the Defensive Driver. Table 2 shows
the test schedule for the Prototype and the time allotted for each part of the
demonstration. The last part of the demonstration will allow time for the Review Board
to ask questions.
Table 2: Test Schedule Table
Start Time
(min)
0:10
Duration Description
Test Case #
5
1.1, 1.2, 2.1, 2.2
0:15
5
0:20
8
Test GPS Receiver and
Distance Sensor
Show Database Schema and
Test Interface
OBU Tests
- Create User
- Authenticate
- Initiate Driving Session
0:28
10
Test Harness Simulation
- Test Driver Controls
- Test Road Controls
13.1 through 13.12
0:38
7
Client Software Tests
- Database
Synchronization
- List Drivers
- Display Reports
4.1, 4.2, 10.1 through 10.7,
12.1 through 12.11,
0:45
59 sec
Questions
3.1, 3.2, 3.3
5.1, 5.2, 5.3, 5.4, 6.1, 6.2,
6.3, 6.4, 7.1, 7.2, 7.3, 7.4,
7.5, 8.1, 8.2, 8.3, 8.4, 9.1,
9.2, 9.3, 11.1 through 11.11
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
3.4
15
Fault Reporting and Data Recording
Sentinel, Inc. will record the failures and successes during the Prototype
demonstration. The test components for the Defensive Driver Prototype are hardware,
GUIs, database and algorithms. Table 3 describes the test components and the process
for recording failures.
Table 3: Fault Reporting and Data Recording Table
Component
Hardware
GUI
Database
Algorithms
3.5
How/Process of Recording
 Report failures through visual inspection of GPS
Receiver and Distance Sensor
 Document through hardcopy forms
 Report failures through visual inspection of GUI
screens
 Document through hardcopy forms
 Report failures through visual inspection of returned
SQL Statements
 Document through hardcopy forms
 Report failures through visual inspection of OBU alert
generation
 Document through hardcopy forms
Resource Requirements
To demonstrate the functionality of the Defensive Driver Prototype, both
hardware and software resources will be required. The hardware resources will consist of
the LCU, GPS Receiver and Distance Sensor. The software resources will consist of
MySQL Database software, GPS Receiver software (GPS-NMEA Monitor v1.60) and
Distance Sensor software (Defensive Driver Distance Interpretation Interface). The test
harness and GUI requirements will also be required for the demonstration.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
3.6
16
Test Environment
The Defensive Driver Prototype demonstration will take place in the Engineering
and Computational Sciences (E&CS) building in third-floor conference room on the Old
Dominion University campus. The layout of the conference room is shown in Figure 2.
The LCU, connected with the GPS Receiver and Distance Sensor and preloaded with all
applicable software, will be connected to the projector and utilize both projector screens
for the demonstration.
Figure 2: E&CS Conference Room Layout
4
Test Responsibilities
Sentinel, Inc.’s members will be responsible for different aspects of the Defensive
Driver Prototype demonstration. Table 4 describes the responsibilities of each team
member during the demonstration. Tihomir Hristov will be the presenter and database
tester. Aimee Dineros will represent the Client and will also conduct the report
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
17
generation tests. Barbara Dixon will be the recorder for the demonstration, noting
statuses of each test case and also documenting questions and/or comments from the
Review Board. Alan Hill will act as the Driver and will also conduct the GUI tests. John
Marr will act as the Instructor to the Driver and will also be the OBU tester. Drew Will
be perform all hardware setup and associated testing.
Table 4: Test Responsibilities Table
Team Member
Tihomir Hristov
Aimee Dineros
Barbara Dixon
Alan Hill
John Marr
Drew Will
5
Responsibilities
Presenter/DB Tester
Report Generation Tester/Client
Recorder
GUI/Driver
OBU Tester/Instructor
Hardware Setup/Tester
Test Procedures
Test procedures have been developed to ensure that the functionality of the
Defensive Driver Prototype is attained. The test procedures are represented in a format
that contains the category, purpose, actual activity, expected results, and a space to
identify whether or not the test case passed or failed and comments that may be
associated with these.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
5.1
18
Test Case Names and Identifiers
Test category one verifies the functionality of the GPS Receiver that supports the
Defensive Driver Prototype. The expected results, when proven, confirm adherence to
the outline specifications and requirements of the Defensive Driver Prototype.
Test Category ID: 1
Test Case: 1.1
Test Case Activity
Description: Defensive Driver hardware functionality
Purpose: Verify GPS receiver is connected properly
Setup Conditions: NMEA Monitor version 1.6 installed
Pass/Fail Comments
Expected Result
1
Connect GPS to computer
GPS driver is recognized
2
Execute NMEA Monitor v1.6
NMEA Monitor opens
3
Scan COMM ports to find GPS
receiver
Select COMM port on which GPS
is located
GPS receiver is found
4
Test Category ID: 1
Test Case: 1.2
Test Case Activity
GPS data streams into
program
Description: Defensive Driver hardware functionality
Purpose: Verify GPS is recording information in the correct GGA (Global
Positioning System Fix Data) format
Setup Conditions: Test case 1.1 passed
Pass/Fail Comments
Expected Result
1
Start logging GPS data
NMEA Monitor creates
*.txt log file
2
Open log file and check contents
Data should be logged in
the following format:
DegreesMinutes.Seconds,
N,
DegreesMinutes.Seconds,
W, knots
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
19
Test category two verifies the functionality of the Distance Sensor that supports
the Defensive Driver Prototype. The expected results, when proven, confirm adherence
to the outline specifications and requirements of the Defensive Driver Prototype.
Description: Defensive Driver hardware functionality
Purpose: Verify distance sensor is connected properly
Setup Conditions: Defensive Driver OBU Software Installed
Test Case Activity
Pass/Fail Comments
Expected Result
1
Connect distance sensor to
Distance Sensor is
computer
recognized
Test Category ID: 2
Test Case: 2.1
Description: Defensive Driver hardware functionality
Purpose: Verify distance information is being reported properly
Setup Conditions: Test case 2.1 Passed
Test Case Activity
Pass/Fail Comments
Expected Result
1
Execute OBU Software
Distance sensor reports
correct distance to object
in front
Test Category ID: 2
Test Case: 2.2
Test category three verifies the functionality of the Defensive Driver Database
that supports the Defensive Driver Prototype. The expected results, when proven,
confirm adherence to the outline specifications and requirements of the Defensive Driver
Prototype.
Description: Defensive Driver database schema and interface
Purpose: Verify all fields are created correctly
Setup Conditions: MySQL installed and database tables created
Test Case Activity
Pass/Fail Comments Expected Result
1
Run queries to display database
All fields are displayed
tables’ structure
2
Visually verify all required fields
Database fields displayed
are created correctly
will match database
schemas.
Test Category ID: 3
Test Case: 3.1
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
20
Description: Defensive Driver database schema and interface
Purpose: Verify OBU database interface is functional and allows for insertion
and retrieval of information from the MySQL tables.
Setup Conditions: Test case 3.1 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Create a OBUdb object and call the
All OBU Student table
addStudent function
fields will be populated
2
Run query to display inserted data
All OBU Student table
and visually verify results
fields will display the
inserted data
3
Create a OBUdb object and call the
All data stored in the
getStudent function
OBU Student table is
properly retrieved and
displayed
4
Run query to display data and
All data stored in the
visually verify results
OBU Student table
should not be modified
5
Repeat Steps 1 through 4 for
Identical to steps 1
NewStudent object
through 4 for NewStudent
table
6
Repeat Steps 1 through 4 for
Identical to steps 1
Instructor object
through 4 for Instructor
table
7
Repeat Steps 1 through 4 for School
Identical to steps 1
object
through 4 for School table
8
Repeat Steps 1 through 4 for the
Identical to steps 1
four different log object
through 4 for each
respective log table
9
Repeat Steps 1 through 4 for
Identical to steps 1
StopSign object
through 4 for StopSigns
table
10
Repeat Steps 1 through 4 for
Identical to steps 1
SpeedLimit object
through 4 for
SpeedLimits table
Test Category ID: 3
Test Case: 3.2
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
21
Description: Defensive Driver database schema and interface
Purpose: Verify Client Software database interface is functional and allows for
insertion and retrieval of information from the MySQL tables.
Setup Conditions: Test case 3.1 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Create a CSdb object and call the
All ClientSoftware
addStudent function
Student table fields will
be populated
2
Run query to display inserted data
All Client Software
and visually verify results
Student table fields will
display the inserted data
3
Create a CSdb object and call the
All data stored in the
getStudent function
Client Software Student
table is properly retrieved
and displayed
4
Run query to display data and
All data stored in the
visually verify results
Client Software Student
table should not be
modified
5
Repeat Steps 1 through 4 for
Identical to steps 1
Instructor object
through 4 for Instructor
table
6
Repeat Steps 1 through 4 for School
Identical to steps 1
object
through 4 for School table
Test Category ID: 3
Test Case: 3.3
7
Repeat Steps 1 through 4 for the
four different log object
8
Repeat Steps 1 through 4 for
StopSign and NewStoptSigns object
9
Repeat Steps 1 through 4 for
SpeedLimit and NewSpeedLimit
object
{This space is intentionally left blank.}
Identical to steps 1
through 4 for each
respective log table
Identical to steps 1
through 4 for StopSigns
and NewStopSigns table
respectively
Identical to steps 1
through 4 for
SpeedLimits and
NewSpeedLimits table
respectively
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
22
Test category four verifies the functionality of the Defensive Driver Database
Synchronization Module that supports the Defensive Driver Prototype. The expected
results, when proven, confirm adherence to the outline specifications and requirements of
the Defensive Driver Prototype.
Description: Defensive Driver Database Synchronization Module
Purpose: Verify DSM is functional and data is properly propagated between the
Client Software database NewSpeedLimit and NewStopSigns tables and the
OBU database SpeedLimit and StopSigns tables.
Setup Conditions: Test case 3.1 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Run query to display OBU data and
Stored data is displayed
visually verify results
2
Run query to display Client
Stored data is displayed
Software data and visually verify
results
3
Run DSM module
OBU and Client Software
databases are properly
synchronized
4
Run query to display OBU data and
SpeedLimits and
visually verify results
StopSigns are updated
5
Run query to display Client
NewSpeedLimits and
Software data and visually verify
NewStopSigns tables
results
have been cleared
Test Category ID: 4
Test Case: 4.1
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
23
Description: Defensive Driver Database Synchronization Module
Purpose: Verify DSM is functional and data is properly propagated between the
OBU database Log tables and the Client Software database Log tables.
Setup Conditions: Test case 3.1 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Run query to display OBU data and
Stored data is displayed
visually verify results
2
Run query to display Client
Stored data is displayed
Software data and visually verify
results
3
Run DSM module
OBU and Client Software
databases are properly
synchronized
4
Run query to display OBU data and
NewStudent and Log
visually verify results
tables have been cleared
5
Run query to display Client
have been cleared;
Software data and visually verify
Student and Log tables
results
have been updated
properly
Test Category ID: 4
Test Case: 4.2
Test category five verifies the functionality of the Speed Limit Detection
Algorithm that supports the Defensive Driver Prototype. The expected results, when
proven, confirm adherence to the outline specifications and requirements of the
Defensive Driver Prototype.
Description: Verify Input from Databases and Sensors are consistent
Purpose: To establish that input is stored and used properly in the Speeding
Algorithm
Setup Conditions: Database and Sensors Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in conformance with
Algorithms given data
Specific Requirements from Lab 2
values shall return stored
and establish they are consistent in
copies of that value.
algorithms.
Test Category ID: 5
Test Case: 5.1
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
24
Description: Verify Alert Generation occurs properly
Purpose: To establish that the Speeding Algorithm issues alerts only when a
Speeding Event Occurs
Setup Conditions: GUI Alerts are completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Alert will be called by the
should occur.
algorithm once
2
Issue test data in which an event
Alert will not be called by
should not occur.
the algorithm
Test Category ID: 5
Test Case: 5.2
Description: Verify Event Start/Stop Timer as Accurate
Purpose: To establish that recorded times are accurate
Setup Conditions:
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Duration time recorded
occurs and finishes in a set time.
should match testing set
time
Test Category ID: 5
Test Case: 5.3
Description: Verify Event Logging as Accurate to logging requirements
Purpose: To establish that event logs contain accurate data
Setup Conditions: Database Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
An event should be stored
must occur and have set duration
into the Driver Profile
values.
Database with the test
data duration time.
Test Category ID: 5
Test Case: 5.4
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
25
Test category six verifies the functionality of the Stop Sign Detection Algorithm
that supports the Defensive Driver Prototype. The expected results, when proven,
confirm adherence to the outline specifications and requirements of the Defensive Driver
Prototype.
Description: Verify Input from Databases and Sensors are consistent
Purpose: To establish that input is stored and used properly in the Stop Sign
Algorithm
Setup Conditions: Database and Sensors Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in conformance with
Algorithms given data
Specific Requirements from Lab 2
values shall return stored
and establish they are consistent in
copies of that value.
algorithms.
Test Category ID: 6
Test Case: 6.1
Description: Verify Alert Generation occurs properly
Purpose: To establish that the Speeding Algorithm issues alerts only when a
Stop Sign Event Occurs
Setup Conditions: GUI Alerts are completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Alert will be called by the
should occur.
algorithm once
2
Issue test data in which an event
Alert will not be called by
should not occur.
the algorithm
Test Category ID: 6
Test Case: 6.2
Description: Verify Event Start/Stop Timer as Accurate
Purpose: To establish that recorded times are accurate
Setup Conditions:
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which a Stop Sign
Duration time recorded
is present and driver stops for less
should match testing set
than/more than/and exactly 3
time
seconds.
Test Category ID: 6
Test Case: 6.3
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
26
Test category seven verifies the functionality of the Following Too Closely
Algorithm that supports the Defensive Driver Prototype. The expected results, when
proven, confirm adherence to the outline specifications and requirements of the
Defensive Driver Prototype.
Description: Verify Input from Databases and Sensors are consistent
Purpose: To establish that input is stored and used properly in the Distance
Algorithm
Setup Conditions: Database and Sensors Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in conformance with
Algorithms given data
Specific Requirements from Lab 2
values shall return stored
and establish they are consistent in
copies of that value.
algorithms.
Test Category ID: 7
Test Case: 7.1
Description: Verify Alert Generation occurs properly
Purpose: To establish that the Distance Algorithm issues alerts only when a
Distance Event Occurs
Setup Conditions: GUI Alerts are completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Alert will be called by the
should occur.
algorithm once
2
Issue test data in which an event
Alert will not be called by
should not occur.
the algorithm
Test Category ID: 7
Test Case: 7.2
Description: Verify Safe Driving Distance is calculated properly using 4.0
meters as an average car length
Purpose: To maintain accurate safe driving distance for Distance Algorithm
Test Case: 7.3
Setup Conditions: GUI Alerts are completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which current
Safe Driving Distance
speed is increased by 10 mph each
will increase by 4 meters
iteration.
each 10 mph increase.
Test Category ID: 7
Description: Verify Event Start/Stop Timer as Accurate
Purpose: To establish that recorded times are accurate
Setup Conditions:
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Duration time recorded
occurs and finishes in a set time.
should match testing set
time
Test Category ID: 7
Test Case: 7.4
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
27
Description: Verify Event Logging as Accurate to logging requirements
Purpose: To establish that event logs contain accurate data
Setup Conditions: Database Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
An event should be stored
must occur and have set duration
into the Driver Profile
values.
Database with the test
data duration time.
Test Category ID: 7
Test Case: 7.5
Test category eight verifies the functionality of the Seat Belt Algorithm that
supports the Defensive Driver Prototype. The expected results, when proven, confirm
adherence to the outline specifications and requirements of the Defensive Driver
Prototype.
Description: Verify Input from OBU Database is consistent
Purpose: To establish that input is stored and used properly in the Seat Belt
Algorithm
Setup Conditions: Database and Sensors Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in conformance with
Algorithms given data
Specific Requirements from Lab 2
values shall return stored
and establish they are consistent in
copies of that value.
algorithms.
Test Category ID: 8
Test Case: 8.1
Description: Verify Alert Generation occurs properly
Purpose: To establish that the Speeding Algorithm issues alerts only when a
Seat Belt Event Occurs
Setup Conditions: GUI Alerts are completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Alert will be called by the
should occur.
algorithm once
2
Issue test data in which an event
Alert will not be called by
should not occur.
the algorithm
Test Category ID: 8
Test Case: 8.2
Description: Verify Event Start/Stop Timer as Accurate
Purpose: To establish that recorded times are accurate
Setup Conditions:
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
Duration time recorded
occurs and finishes in a set time.
should match testing set
time
Test Category ID: 8
Test Case: 8.3
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
28
Description: Verify Event Logging as Accurate to logging requirements
Purpose: To establish that event logs contain accurate data
Setup Conditions: Database Functioning Properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Issue test data in which an event
An event should be stored
must occur and have set duration
into the Driver Profile
values.
Database with the test
data duration time.
Test Category ID: 8
Test Case: 8.4
Test category nine verifies the functionality of the Algorithm Controller Class that
supports the Defensive Driver Prototype. This algorithm ensures that the previous
algorithms are running properly. The expected results, when proven, confirm adherence
to the outline specifications and requirements of the Defensive Driver Prototype.
Description: Verify all Event Algorithms are active
Purpose: To ensure that all four detection Algorithms are running.
Setup Conditions: Detection Algorithms are functioning properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Initialize Algorithm Controller
Stop Sign, Speed Limit,
Seat Belt, Distance
Detection algorithms
should be running
Test Category ID: 9
Test Case: 9.1
Description: Verify all Event Algorithms are working in parallel
Purpose: To ensure that all four detection Algorithms are writing to the
Database in parallel.
Setup Conditions: Detection Algorithms are functioning properly
Test Case Activity
Pass/Fail Comments Expected Result
1
Initialize Algorithm Controller and
Each event should be
provide test case data for each
recorded into the
algorithm in which a worst case
database.
scenario occurs (All 4 events
occur/end at same time)
Test Category ID: 9
Test Case: 9.2
Description: Verify Algorithm Stop/Start event timer as accurate
Purpose: To establish that recorded time is accurate
Setup Conditions:
Test Case Activity
Pass/Fail Comments Expected Result
1
Provide a set time of Algorithm
Total Driving Time
Controller being on.
recorded must match set
time.
Test Category ID: 9
Test Case: 9.3
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
29
Test category 10 verifies the functionality of the Analysis Algorithm that supports
the Defensive Driver Prototype. The expected results, when proven, confirm adherence
to the outline specifications and requirements of the Defensive Driver Prototype.
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the frequency is collected for Stop Sign Event;
Verify the duration is collected for Following Too Closely, Speeding, and Seat
Belt Unengaged
Setup Conditions: Functions to collect event log frequency and duration created
Test Case Activity
Pass/Fail Comments Expected Result
1
Run function to display the
Functions return the
frequency for Stop Sign violations;
frequency and duration
Run function to display duration for
values
the required events
2
Visually verify functions return
Frequency and duration
frequency and duration values for
values displayed are
their corresponding events
correct
Test Category ID: 10
Test Case: 10.1
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the weight is collected for Stop Sign Violations, Following Too
Closely, Speeding, and Seat Belt Unengaged
Setup Conditions: Test case 10.1 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Display each event and it’s
The weight corresponds
corresponding weight
to the correct event
Test Category ID: 10
Test Case: 10.2
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the Driver Points are calculated for Stop Sign Violations,
Following Too Closely, Speeding, and Seat Belt Unengaged
Setup Conditions: Test cases 10.1 and 10.2 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Run function to collect frequency
The frequency is returned
for Stop Sign violations
2
Run function to collect duration for
The duration is returned
Following Too Closely, Speeding,
and Seat Belt Unengaged
3
Get the weight for the
A value for the weight is
corresponding event
returned
4
Calculate Driver Points
A value for Driver Points
is returned
5
Visually verify the function returns
The correct value for
Driver Points
Driver Points is displayed
Test Category ID: 10
Test Case: 10.3
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
30
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the Driver Points are collected for each driving session/date
Setup Conditions: Test cases 10.1 through 10.3 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Collect first driving date and
The driving date and
corresponding Driver Points
Driver Points are correct
2
Repeat test case activity (1) until all
Driving dates and Driver
successive driving dates and
Points are displayed in
Driving Points are displayed
ascending order of date
Test Category ID: 10
Test Case: 10.4
Description: Defensive Driver Analysis Algorithm
Purpose: Verify Points Per Hour is calculated
Setup Conditions: Test cases 10.1 through 10.4 passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Collect and add all Driver Points for
Total Driver Points is
an individual student
calculated
2
Collect the student’s hours driven
Total Driving Hours is
collected
3
Calculate the quotient of Total
A value between 0-1 is
Driver Points and Total Driving
calculated for Points Per
Time
Hour
Test Category ID: 10
Test Case: 10.5
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the date is collected for each event recorded
Setup Conditions: Test cases 10.1 through 10.5 have passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Run function to gather the date each
The date is returned
event was recorded
2
Visually verify the function returns
The correct value for
the Date
Date is displayed
Test Category ID: 10
Test Case: 10.6
Description: Defensive Driver Analysis Algorithm
Purpose: Verify the report is generated
Setup Conditions: Test cases 10.1 through 10.6 have passed
Test Case Activity
Pass/Fail Comments Expected Result
1
Run function to generate report
Functions return the
report
2
Visually verify functions return
Report information
report information requested
displayed is correct
Test Category ID: 10
Test Case: 10.7
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
31
Test category 11 verifies the functionality of the OBU GUI that supports the
Defensive Driver Prototype. The expected results, when proven, confirm adherence to
the outline specifications and requirements of the Defensive Driver Prototype.
Test Category ID:
11
Test Case: 11.1
Description: OBU Graphical User Interface: Login Screen
Purpose: Verify login is displayed correctly, login is successful for authorized
users and reject unauthorized users.
Setup Condition: Database tables created and properly populated
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load OBU by double clicking on
Welcome message will
the icon on the desktop.
be in the center of the
upper edge of the screen,
and login instructions
will be directly below it.
New User Button will
appear at the bottom
center of the screen.
2
Input an invalid fingerprint.
An error message is
displayed and access is
not granted.
3
Input a valid fingerprint.
Granted access to the
OBU, and will be shown
the Driving Display
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
32
Description: OBU Graphical User Interface: New User Screen
Purpose: Verify a new user can be added through the OBU
Setup Condition: Database tables created and properly populated
Test Case Activity
Pass/Fail
Comments Expected Result
1
Click on New User button on the
Screen will change to
Login screen.
show the New User form.
2
Examine the screen to ensure
The instructions are at
correct formatting.
the top of the screen, a
text box is displayed at
the below the
instructions, the
keyboard will be shown
in the center, bottom
portion of the screen, the
OK button is below the
keyboard.
3
Input a new user's name.
The user's name will be
displayed in the text box
as typed.
4
Press the OK button.
A progress bar is shown
and results in the new
user being inserted into
the database. View
database to ensure proper
insertion. Access will be
granted to the OBU and
the user will be shown
the Driving Display.
Test Category ID: 11
Test Case: 11.2
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
33
Description: OBU Graphical User Interface: About Screen
Purpose: Verify the information about the OBU is displayed correctly.
Setup Condition: Test Case 11.1 or Test Case 11.2 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select the About screen from the
The Driving Display is
Driving Display.
hidden and the About
screen is displayed.
2
Examine the screen to ensure
All information is listed
correct formatting.
in the following format:
Unit Number: ###
Software Version: ###
Copyright © 2010 to
Sentinel, Inc.
3
Compare the information displayed
All information listed
to the data in Student table.
will match the
information in the
database.
Test Category ID: 11
Test Case: 11.3
Test Category ID:
11
Test Case: 11.4
Description: OBU Graphical User Interface: Owner Information Screen
Purpose: Verify the information about the Owner is displayed correctly.
Setup Condition: Test Case 11.1 or Test Case 11.2 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select Owner Info. screen from the
The Driving Display is
Driving Display.
hidden and the Owner
Information screen is
displayed.
2
Examine the screen to ensure
All information is listed
correct formatting.
in the following format:
Owner: John Smith
Website:
http://www.johnsmith.co
m
Email Address:
john.smith@somecompan
y.com
Phone Number: (555)
555-5555
3
Compare the information displayed
All information listed
to the data in School and Instructor
will match the
table.
information in the
database.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
34
Description: OBU Graphical User Interface: Driving Display Screen
Purpose: Verify the information to be displayed while the user is driving is
shown correctly.
Setup Condition: Test Case 11.1 or Test Case 11.2 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the screen to ensure
The following distance
correct formatting.
and current speed are
listed in the following
format:
Following Distance: ###
Current Speed: ###
A seatbelt graphic is
shown below the
following distance and
current speed.
2
Compare the information
All information will
displayed to the input from the test
match the input from the
harness.
test harness.
Test Category ID: 11
Test Case: 11.5
Test Category ID:
11
Test Case: 11.6
Description: OBU Graphical User Interface: Speed Limit Alert Screen
Purpose: Verify the alert is shown correctly when the conditions for the alert are
met.
Setup Condition: Test Case 11.5 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Increase the speed of the simulated
The Driving Display is
car, using the speed control of the
hidden and the Speed
test harness, so that it is above the
Limit Alert is shown.
posted speed limit through the test
harness.
2
Examine the alert to ensure it is
A graphic of the speed
being displayed correctly.
limit and the car's current
speed below it are
shown.
3
Compare the information
All information will
displayed to the input from the test
match the input from the
harness.
test harness.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
35
Test Category ID: 11 Description: OBU Graphical User Interface: Following Too Closely Alert Screen
Purpose: Verify the alert is shown correctly when the conditions for the alert are
Test Case: 11.7
met.
Setup Condition: Test Case 11.5 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Decrease the distance between the
The Driving Display is
user's simulated car and another
hidden and the Following
car in front of it using the modify
Too Closely Alert is
distance control of the test harness.
shown.
2
Examine the alert to ensure it is
The following distance
formatted correctly.
and current speed are
shown in the following
format:
Current Following
Distance: ###
Current Speed: ###
The message is at the
bottom, center of the
screen telling the drivier
to slow down and the
minimum safe following
distance.
3
Compare the information
All information will
displayed to the input from the test
match the input from the
harness.
test harness.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
Test Category ID:
11
Test Case: 11.8
36
Description: OBU Graphical User Interface: Seatbelt Usage Alert Screen
Purpose: Verify the alert is shown correctly when the conditions for the alert are
met.
Setup Condition: Test Case 11.5 passed, the seatbelt has been previously
engaged.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Disengage the user's simulated
The Driving Display is
seatbelt.
hidden and the Seatbelt
Usage Alert is shown.
2
Examine the alert to ensure it is
The message is displayed
formatted correctly.
at the top center of the
screen and tells the user
to engage their seatbelt.
A red graphic of a
disengaged seatbelt is
shown below the
message.
3
Compare the information
All information will
displayed to the input from the test
match the information in
harness.
the test harness.
Description: OBU Graphical User Interface: Stop Sign Alert Screen
Purpose: Verify the alert is shown correctly when the conditions for the alert
are met.
Setup Condition: Test Case 11.5 passed, the simulated vehicle is close to a
stop sign.
Test Case Activity
Pass/Fail
Comments Expected Result
1
"Drive" the simulated vehicle
The Driving Display is
through a stop sign without
hidden and the Stop Sign
stopping correctly.
Alert is shown.
2
Examine the alert to ensure it is
The graphic is at the
displayed correctly.
center top of the screen
with the message
explaining to the user
how to stop correctly
below the graphic.
3
Compare the information displayed
All information will
to the input from the test harness.
match the input from the
test harness.
Test Category ID: 11
Test Case: 11.9
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
Test Category ID:
11
Test Case: 11.10
37
Description: OBU Graphical User Interface: Driver Information Screen
Purpose: Verify the user's information is displayed correctly.
Setup Condition: Test Case 11.1 or Test Case 11.2 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select the Driver Information
The Driving Display is
screen from the Driving Display.
hidden and the Driver
Information is shown.
2
Examine the screen to ensure it is
All information is
displayed correctly.
displayed in the
following format:
Driver's Name: John Doe
Mailing Address: …
School: Some School
Instructor: John Smith
Hours Driven: ###
3
Compare the information displayed
All information matches
to the data in Student table.
the data stored in the
database.
Test Category ID: 11 Description: OBU Graphical User Interface: Completed Session Screen
Purpose: Verify the session is saved correctly.
Test Case: 11.11
Setup Condition: Test Case 11.1 or Test Case 11.2 passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Turn off the simulated vehicle by
A progress bar is
closing the test harness.
displayed telling the user
the session is being saved
to the database.
2
Examine the database.
All information was
correctly inserted into the
database.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
38
Test category 12 verifies the functionality of the Administrator GUI that supports
the Defensive Driver Prototype. The expected results, when proven, confirm adherence
to the outline specifications and requirements of the Defensive Driver Prototype.
Test Category
ID: 12
Test Case: 12.1
Description: Administrator Graphical User Interface: Login Screen
Purpose: Verify login is displayed correctly, login is successful for authorized users
and reject unauthorized users.
Setup Condition: Database tables created and properly populated
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load Administrator Program by
Welcome message will
clicking on the icon on the desktop.
be in the center of the
upper edge of the screen,
and login instructions are
directly below it. The
username and password
textboxes are at the
bottom center of the
screen, with the login
button beneath them.
2
Input an invalid username and/or
An error message is
password.
displayed and access is
not granted.
3
Input a valid username and
Granted access to the
password.
Administrator screens,
and will be shown the list
of drivers associated with
the logged in
administrator.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
39
Description: Administrator Graphical User Interface: About Screen.
Purpose: Verify the information about the Administrator Software is displayed
correctly.
Setup Condition: Test Case 12.1 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select the About screen from the
The List of Drivers is
List of Driver.
hidden and the About
screen is displayed.
2
Examine the screen to ensure the
All information is listed
information is being displayed in
in the following format:
the correct format.
Owner: John Smith
Mailing Address: …
Website:
www.johnsmith.com
Email: john@smith.com
Defensive Driver
Administrator v. .01
3
Compare the data displayed to the
All information listed
data in School and Instructor table.
matches the information
in the database.
Test Category ID: 12
Test Case: 12.2
Description: Administrator Graphical User Interface: List of Units Screen.
Purpose: Verify each unit associated with the current administrator is listed
correctly.
Setup Condition: Test Case 12.1 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select List of Units from the List of
The List of Drivers is
Drivers.
hidden and the List of
Units screen is displayed.
2
Examine the screen to ensure the
Each unit is listed,
list is being displayed correctly.
ordered by their unit
number, in the following
format:
Unit: #### Driver: John
Smith
3
Compare the data displayed to the
All information listed
data in GeneralLogs table.
matches the database.
Test Category ID: 12
Test Case: 12.3
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
40
Description: Administrator Graphical User Interface: List of Drivers Screen.
Purpose: Verify each driver associated with the current administrator is listed
correctly.
Setup Condition: Test Case 12.1 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the screen to ensure each
Each driver is listed,
driver is being displayed correctly.
ordered by their name, in
the following format:
Driver: John Smith
Unit: ####
2
Compare the data displayed to the
All information listed
data in GeneralLogs table.
matches the database.
Test Category ID: 12
Test Case: 12.4
Description: Administrator Graphical User Interface: Driver Profiling and
Report Processing Screen.
Purpose: Verify the information about the driver is displayed correctly.
Test Case: 12.5
Setup Condition: Test Case 12.3 or 12.4 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select a driver or unit number from
The List of Drivers or
the List of Drivers or List of Units,
List of Units is hidden
respectively.
and the Driver Profiling
and Report Processing
screen is displayed.
2
Examine the screen to ensure it is
The driver's information
being displayed correctly.
is displayed in the
following format:
Driver: John Smith
Address: …
Phone Number: (555)
555-5555
Email: smith@john.com
Underneath the driver's
information, in a row, are
the different buttons to
access the sub-screens.
3
Compare the data displayed to the
All information listed
data in Student table.
matches the database.
Test Category ID: 12
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
41
Description: Administrator Graphical User Interface: Display Alerts Screen.
Purpose: Verify all the alerts issued to the driver are displayed correctly.
Setup Condition: Test Case 12.5 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Press the Display Alerts button on
The Driver Profiling and
the Driver Profiling and Report
Report Processing
Processing Screen.
Screen is hidden and the
Display Alerts Screen is
shown.
2
Examine the screen to ensure it is
Each alert issued to the
being displayed correctly.
driver is organized by
date and time and
displayed in the
following format:
MM/DD/YYY ##:##.##
Alert Type
3
Compare the data displayed to the
All information listed
data in SpeedLogs, StopSignLogs
matches the database.
and DistanceLogs tables.
Test Category ID: 12
Test Case: 12.6
Description: Administrator Graphical User Interface: Driver Analysis Screen.
Purpose: Verify the driver analysis data is displayed correctly.
Setup Condition: Test Case 12.5 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Press the Driver Analysis button on
The Driver Profiling and
the Driver Profiling and Report
Report Processing
Processing Screen.
Screen is hidden and the
Driver Analysis Screen is
shown.
2
Examine the screen to ensure it is
The format is consistent
being displayed correctly.
with Figure *** in the
appendix.
3
Examine the data.
All the data has been
calculated correctly as
described by the analysis
algorithm.
Test Category ID: 12
Test Case: 12.7
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
42
Description: Administrator Graphical User Interface: Driver Statistics Screen.
Purpose: Verify the driver statistics are displayed correctly.
Setup Condition: Test Case 12.5 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Press the Driver Statistics button on
The Driver Profiling and
the Driver Profiling and Report
Report Processing
Processing Screen.
Screen is hidden and the
Driver Statistics Screen
is shown.
2
Examine the screen to ensure it is
The statistics are
being displayed correctly.
displayed in the
following format:
Mistake/Alert
Frequency(###)
3
Compare the data displayed to the
All information displayed
data in Student and Log tables.
is consistent with the
information stored in the
database.
Test Category ID: 12
Test Case: 12.8
Description: Administrator Graphical User Interface: Alert Database
Synchronization Screen.
Purpose: Verify the button initiates and completes the synchronization process.
Test Case: 12.9
Setup Condition: Test Case 12.5 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Insert the SD Memory card into the
A pop-window with a
computer and press the Alert
progress bar is displayed.
Database Synchronization button
on the Driver Profiling and Report
Processing Screen.
2
Examine the screen to ensure it is
As the process is
being displayed correctly.
completed the progress
bar is filled.
3
Compare the Alerts and Logs
The information from the
database on the administrators
SD Memory card has
computer to the Alerts and Logs
been inserted into the
database on the SD Memory card.
database.
Test Category ID: 12
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
43
Description: Administrator Graphical User Interface: New Driver Screen.
Purpose: Verify a new driver can be added through the Administrator interface.
Setup Condition: Test Case 12.1 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Click on the New Driver button on
The List of Drivers is
the List of Drivers screen.
hidden and the New
Driver screen is shown.
2
Examine the screen to ensure the
The text boxes are shown
text boxes are formatted correctly.
in the following order:
Driver's Name: …
Instructor's Name: …
School: …
School Address: …
Driver's Address: …
OBU Unit: …
At the bottom left corner
of the screen is the save
button.
3
Enter the new driver's information.
The information is
displayed as typed into
the text boxes.
4
Click the save button and examine
The new driver's
the database.
information is inserted
correctly into the
database.
Test Category ID: 12
Test Case: 12.10
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
44
Description: Administrator Graphical User Interface: Stop Sign/Speed Limit
Database Synchronization Screen.
Purpose: Verify the button initiates and completes the synchronization process.
Test Case: 12.11
Setup Condition: Test Case 12.1 Passed.
Test Case Activity
Pass/Fail
Comments Expected Result
1
Insert the SD Memory card into the
A pop-window with a
computer and press the Stop
progress bar is displayed.
Sign/Speed Limit Synchronization
button on the List of Drivers
Screen.
2
Examine the progress bar.
As the process is
completed the progress
bar will be filled.
3
Compare the databases on the
The information from the
administrator's computer to the
databases on the
databases on the SD Memory card.
administrator's computer
has been inserted into the
databases on the SD
Memory card.
Test Category ID: 12
Test category 13 verifies the functionality of the Test Harness GUI that supports
the Defensive Driver Prototype. The expected results, when proven, confirm adherence
to the outline specifications and requirements of the Defensive Driver Prototype.
Test Category ID:
13
Test Case: 13.1
Description: Test Harness Graphical User Interface: Welcome Screen
Purpose: Verify the Welcome Screen is rendered correctly.
Setup Condition: Database tables created and properly populated
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load the test harness by clicking on
The welcome message is
the icon on the desktop.
at the top center of the
screen with the prototype
description below it and
the instructions under the
description. After a few
seconds the Driving
Controls panel, Instance
of OBU Prototype, and
Road Controls panel are
displayed.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
45
Test Category ID:
13
Test Case: 13.2
Description: Test Harness Graphical User Interface: Driving Controls Panel
Test Category ID:
13
Test Case: 13.3
Description: Test Harness Graphical User Interface: Speed Control
Purpose: Verify the Driving Controls panel is rendered correctly.
Setup Condition: Test Case 13.1 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the panel to ensure it is
The Steering Control is
formatted correctly.
at the top center of the
panel with the Braking
Control and Speed
Control beneath it. To
the right of the Steering
Control is the Seatbelt
Toggle Switch.
Purpose: Verify the Speed Control increases and decreases the speed of the
simulated car.
Setup Condition: Test Case 13.2 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the control to ensure it is
The two buttons are
formatted correctly.
stacked on top of each
other, the button to
increase the speed is
above the button to
decrease the speed.
2
Click on the control to increase the
The speed of the
speed.
simulated car is increased
by one mile per hour.
3
Click on the control to decrease the
The speed of the
speed.
simulated car is
decreased by one mile
per hour.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
46
Description: Test Harness Graphical User Interface: Seatbelt Toggle Switch
Purpose: Verify the Seatbelt Toggle Switch engages and disengages the
simulated seatbelt.
Setup Condition: Test Case 13.2 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the control to ensure it is
The button has the
formatted correctly.
graphic of a seatbelt on it
and the label says the
seatbelt is currently
disengaged.
2
Click on the button to engage the
The label next to the
simulated seatbelt.
button will say "Seatbelt
Engaged"
3
Click on the button to disengage the
The label next to the
simulated seatbelt.
button will say "Seatbelt
Disengaged"
Test Category ID: 13
Test Case: 13.4
Test Category ID: 13 Description: Test Harness Graphical User Interface: Steering Control
Purpose: Verify the Steering Control changes the direction of the simulated car.
Test Case: 13.5
Setup Condition: Test Case 13.2 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the control to ensure it is
There are two buttons on
formatted correctly.
a single row next to each
other, the one with the
left hand arrow to the left
and the one with the right
hand arrow to the right.
2
Click on the left hand arrow.
The simulated car is
moved to the left by one
degree.
3
Click on the right hand arrow.
The simulated car is
moved to the right by one
degree.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
47
Test Category ID: 13 Description: Test Harness Graphical User Interface: Braking Control
Purpose: Verify the Braking Control decreases the speed of the car.
Test Case: 13.6
Setup Condition: Test Case 13.2 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the control to ensure it is
The Barking Control has
formatted correctly.
a graphic of a brake on it.
2
Press the button to slow down the
The speed of the
simulated car.
simulated car is
decreased by five miles
per hour.
Test Category ID:
13
Test Case: 13.7
Description: Test Harness Graphical User Interface: Display Alerts window.
Purpose: Verify the Display Alerts window shows all alerts issued to the tester.
Setup Condition: Test Case 13.1 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Press the Display Alerts button.
A pop-up window with all
the alerts issued to the
driver is displayed and
updated as new alerts are
issued to the user. Each
alert is listed according to
the time they were issued
and in the following
format:
Time: ##:##.## Alert
Type: ...
2
Click on a speeding alert.
Verify the following
information is shown:
Speed of Car at Time of
Alert: ###
Posted Speed Limit: ###
3
Click on a following too closely
Verify the following
alert.
information is shown:
Following Distance: ###
Speed of Car: ###
4
Click on a seatbelt usage alert.
Verify the following
information is shown:
Time: ###
5
Click on a stop sign alert.
Verify the following
information is shown:
Time Stopped: ###
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
48
Test Category ID: 13 Description: Test Harness Graphical User Interface: Instance of OBU Prototype
Purpose: Verify the Instance of the OBU Prototype is displayed.
Test Case: 13.8
Setup Condition: Test Case 13.1 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the test harness to ensure
The OBU Prototype is
the OBU is displayed.
displayed appropriately, for
OBU tests see Test
Category: 13
Test Category ID:
13
Test Case: 13.9
Description: Test Harness Graphical User Interface: Road Controls Panel
Test Category ID:
13
Test Case: 13.10
Description: Test Harness Graphical User Interface: Change Speed Limit button
Purpose: Verify the Road Controls Panel is rendered correctly.
Setup Condition: Test Case 13.1 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the panel to ensure proper
The buttons are displayed
formatting.
in a column with the
Change Speed Limit on
top, the Modify Space
Between Vehicles in the
middle, and Add Stop Sign
at the bottom.
Purpose: Verify the Change Speed Limit button works correctly.
Setup Condition: Test Case 13.9 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Click on the Change Speed Limit
A pop-up window is
button on the Road Controls Panel.
displayed.
2
Examine pop-up window.
3
Enter starting and ending GPS
coordinates, press OK and examine
the Speed Limit Database.
{This space is intentionally left blank.}
There are two text boxes,
one for the starting GPS
coordinates and one for
the ending GPS
coordinates of the new
speed limit zone with an
OK button on the bottom
left of the window.
The new speed limit zone
is correctly inserted into
the Speed Limit database.
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
49
Description: Test Harness Graphical User Interface: Modify Space Between
Vehicle buttons
Purpose: Verify the Modify Space Between Vehicle button works correctly.
Test Case: 13.11
Setup Condition: Test Case 13.9 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Examine the buttons.
There are two buttons, one
with an up arrow to
increase the distance and
one with a down arrow to
decrease the distance.
2
Press the increase distance button.
The distance between the
users simulated vehicle
and another car is
increased by one meter.
3
Press the decrease distance button.
The distance between the
users simulated vehicle
and another car is
decreased by one meter.
Test Category ID: 13
Test Category ID: 13 Description: Test Harness Graphical User Interface: Add Stop Sign button
Purpose: Verify the Add Stop Sign button works correctly.
Test Case: 13.12
Setup Condition: Test Case 13.9 Passed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Click on the Add Stop Sign button.
A pop-up window is
displayed.
2
Verify pop-up window is rendered
There is a text box to enter
properly.
the GPS Coordinates of
the new stop sign and an
OK button in the bottom
left corner of the window.
3
Enter GPS Coordinates, press OK,
A new stop sign location
and examine the Stop Sign
is entered correctly into
Database.
the Stop Sign database.
{This space is intentionally left blank.}
LAB 3 – DEFENSIVE DRIVER PROTOTYPE TEST PLAN/PROCEDURE
6
50
Traceability to Requirements
The traceability matrix shows the relationship between a prototype component
and the specific requirements. It also shows the associated test cases identified in the test
plan. Table 5 illustrates the relationships between the Defensive Driver test plan and the
specific functional requirements of the Prototype.
{This space is intentionally left blank.}