Running head: Lab 3 – Current Intelligent Transport System Prototype Specification
Lab 3 – Current Intelligent Transport System Prototype Specification
RED Team
Author: Akeem Edwards
Old Dominion University
CS 411W
Professor Janet Brunelle
October 30th 2012
1
Lab 3 – Current Intelligent Transport System Prototype Specification
2
Table of Contents
1.
OBJECTIVES .......................................................................................................................... 3
2.
REFERENCES ........................................................................................................................ 5
3.
TEST PLAN ............................................................................................................................ 6
3.1 Testing Approach .................................................................................................................. 6
3.2 Identification of Tests............................................................................................................ 6
3.3 Test Schedule ...................................................................................................................... 22
3.4 Fault Reporting and Data Recording ................................................................................... 23
3.5 Resource Requirements ....................................................................................................... 24
3.6 Test Environment ................................................................................................................ 25
List of Figures
Figure 1. Classroom Layout……………………………………………………………………26
List of Tables
Table 1. Test Category Identification ............................................................................................. 7
Table 2. Test Schedule .................................................................................................................. 22
Table 3. Fault Reporting and Data Recording .............................................................................. 23
Lab 3 – Current Intelligent Transport System Prototype Specification
3
1. Objectives
Transit organizations around the world are constantly confronted by a lack of complete
information that prevents adequately serving light rail end users and ultimately preventing new
riders from traveling. Current ITS is a product designed to solve these problems and improve the
efficiency of current light rail systems. The topics that will be discussed will be the real world
product description, the major functional components of the product, and the prototype used for
demonstration of the proof of concept.
The light rail system that will be examined will be the Hampton Road Transit’s (HRT) Tide
Light Rail System called The Tide (or simply Tide). The problem that will be examined with The
Tide is the lack of real-time, reliable information available about each train’s location and
occupancy level. After extensive research with the HRT Tide system, communication between
the trains and HRT was also found to be a problem (Serpe). The current implementation of The
Tide light rail system does not allow HRT to track the location, occupancy level of each train,
nor integrate local businesses into the rider destinations, creating problems for riders, businesses,
and HRT as well.
There is a loss of ridership for the Tide light rail system due to frustration and the current
process flow. There is no way for riders to be notified of any incidents that may occur with the
Tide’s light rail, or be informed of alternate routes to their destination of choice. This ends with
riders either lost or abandoned at their station with no communication from HRT.
The prototype of Current ITS is intended to demonstrate valuable information such as train
location, occupancy levels, and historical data available through a web interface to a fake transit
authority. Fake Businesses will be allowed to submit advertisements as well as promote events.
A simulated rider will be able to receive notifications from transit authority, and view train
Lab 3 – Current Intelligent Transport System Prototype Specification
4
occupancy levels. The purpose of this test plan and procedure is to establish the arrangement,
and classification of test to be conducted in order to show that the operational prototype has
achieved these objectives.
(This space was intentionally left blank.)
Lab 3 – Current Intelligent Transport System Prototype Specification
5
2. References
Serpe, R. (n.d.). Responsibilities of The Tide's Light Rail Controllers & Operators. Retrieved
from Serpe Firm:
http://www.serpefirm.com/responsibilities:the:tide:light:rail:controller:operator.aspx
Lab1-- Current Intelligent Transport System Product Description.V2.( 2012 October). Red
Team CS411W:Akeem Edwards.
Lab2-- Current Intelligent Transport System Product Specification.V2.( 2012 October). Red
Team CS411W:Akeem Edwards.
(This space was intentionally left blank.)
Lab 3 – Current Intelligent Transport System Prototype Specification
6
3. Test Plan
This section provides a comprehensive explanation of the Current ITS test plan. It
provides the types of tests to be performed, the testing schedule, reporting procedures,
resources requirements, and testing environment.
3.1 Testing Approach
Current ITS testing will consist of unit, integration, and system tests to verify
performance of the system. The unit tests will verify individual software components of
the prototype. Integration tests will evaluate the communication between one or more
related software components. Each major functional component of the Current ITS
prototype will be tested through these means.
The Current ITS database, Decision Engine, Web Application Engine (WAE), and test
harness must all be tested. The database will be tested by visually examining the tables
and using SQL queries to ensure the contents of each table. The Decision Engine and the
WAE will be tested through a specialized test harness designed to demonstrate particular
features based on simulated data.
3.2 Identification of Tests
The test cases for the Current ITS prototype are identified in Table 1. These tests
cases are divided into different categories with their own names and descriptions to
define them. Test cases may prove one or more functional requirements specified for the
Current ITS prototype as outlined in Lab 2.
(This space was intentionally left blank.)
Lab 3 – Current Intelligent Transport System Prototype Specification
Category
ID
7
Test
Description
Case
Description
Objective
Visually examine the entries for date
1.1
Formats
(YYYYMMDD) and time
(HHMMSS) formats.
Read/Write
Test create, read, update, and delete
Procedures
stored procedures on the database.
1.2
Test updateable views for
Refresh
functionality and response/refresh
1.3
1
Database
Times
time.
Test triggers for proper functionality
Read/Write
on various create, read, and delete
1.4
Triggers
commands.
Test tables for proper schema,
Schema
functionality, and efficiency and ease
1.5
Efficiency
of use, and for proper data values.
Test
Category
Description
Case
Requirements
Description
Objective
Referenced
Lab 3 – Current Intelligent Transport System Prototype Specification
8
Database
Test Current ITS
Connectivity
database connection
3.1.2.1.iv
2.1
Decision
Integration
Test ability to query
3.1.2.1.v.a,
the database and
3.1.2.1.vi.a,
necessary tables
3.1.2.1.vi.d,
3.1.2.1.vi.g,
Engine –
3.1.2.2.iii,
DB Interface
2.2
Select Ability
3.1.2.2.iv,
3.1.2.2.v,
3.1.2.2.vii,
3.1.2.3.iii,
3.1.2.3.iv
Validate Input of
3.1.2.1.i,
Input
date, time range,
2.3
Validation
stop id
Decision
Engine –
Unit
Ridership
3.1.2.1.ii
Interval
Test future/past
Validation
date determination
3.1.2.1.iii
2.4
Trend
Test average of
Analysis
Average
embark/disembark
2.5
Function Test
for past 15 days
3.1.2.1.vi.b
Lab 3 – Current Intelligent Transport System Prototype Specification
9
Past Event
Test past Event
Test
Detection
Future Event
Test future Event
Test
Detection
3.1.2.1.vi.c
2.6
3.1.2.1.vi.f
2.7
Test accuracy of
3.1.2.1.vi.h
variance between
Ridership
established
2.8
Variance
disembark/embark
Function Test
averages and past
event values
Ridership
Test output of
3.1.2.1.vii
embark/disembark
2.9
Integration
Output
Validation
to Ridership Trend
Report function
Validate input of
3.1.2.2.i.
Input
Decision
GPS coordinates
2.10
Validation
3.1.2.2.ii
and dates
Engine –
Unit
Delay Impact
Test ability to
Train Activity
Calculator
determine if a train
2.11
Test
is active or not
3.1.2.2.iii
Lab 3 – Current Intelligent Transport System Prototype Specification
10
Delay
Test accuracy of
Average
average variance
Calculation
from the schedule
3.1.2.2.vi
2.12
Test
2.13
Alert
Test ability to
Detection
correctly identify
Test
active alerts
Alert Delay
Test accuracy of
Interval
alert severity level
Application
delay interval on
Test
variance average
3.1.2.2.vii,
3.1.2.2.viii
2.14
Test accuracy of
2.15
Total
comparison
Calculated
between calculated
Delay Test
expected time-ofarrival and schedule
Integration
Delay
Test output of delay
Estimate
time to Train Data
Output
Report Module
2.16
Validation
3.1.2.2.ix
Lab 3 – Current Intelligent Transport System Prototype Specification
11
Validate input of
3.1.2.3.i,
Input
Date range and
2.17
Validation
3.1.2.3.ii
Stop ID
Unit
Test accuracy of
Decision
Engine –
Ontime
variance between
Accuracy Test
past arrival times
3.1.2.3.v
2.18
Ontime
and schedule times
Performance
Test output of
Reporting
3.1.2.4.vi
Ontime
variance from the
Performance
schedule to the
2.19
Integration
Output
Train Data Report
Validation
Module
Categories
Sub
Test
Category
Case
Test
GPS Data
3.1
Harness
tester
3.2
3.3
Name
Description
GPS stop
Verify each virtual stop has an
tester
associated GPS coordinate.
GPS format
Verify GPS coordinate is in the correct
test
format
GPS route test
Verify the GPS route list contains a
proper GPS coordinates
3.4
GPS train test
Verify a train’s coordinate is updated
and valid.
Lab 3 – Current Intelligent Transport System Prototype Specification
Ridership
Ridership
Test virtual rider generation for each
Data Control
Data
stop
tester
generation test
Ridership
3.5
12
3.6
Data Control
Ridership
Ensure realistic proportions of riders
Data test
are generated conforming to variable
tester
thresholds which can be changed by the
user
Train control
3.7
tester
3.8
3.9
3.10
Train GPS
Verify each active train return
test
assigned GPS coordinate
Train sensor
Verify each train has the ability to
failure test
simulate sensor failure
Train outage
Verify the ability for a train to no
failure
return a GPS coordinate.
Ridership test
Verify each train has the ability to
return the current amount of riders on
board
Business ad
3.11
End date test
control tester
Verify access to each advertisement’s
end date
3.12
Start date test
Verify access to each advertisement’s
start date
3.13
Advertisement Verify Ability to assign and view
stop test
advertisements assigned at each stop
Lab 3 – Current Intelligent Transport System Prototype Specification
3.14
Advertisement Verify access to each advertisement’s
start time
3.15
3.16
Interface
3.17
3.18
3.19
start time
Advertisement Verify access to each advertisement’s
end time
Test harness
13
end time
Train property Verify interface has the ability to
GUI
display each trains properties
Train settings
Verify interface has the ability to edit
test
different train settings
Stop property
Verify interface has the ability to
test
display ridership at each stop
Stop Property
Verify interface has the ability to edit
edit test
different ridership numbers at each
stop.
Test
Category
Description
Case
Description
Objective
Verify user a able to insert name,
Webpage
desired user name, email address and
9.1.1
Layout
User
password.
Unit
Management
Username
Ensure username is validated and
Validation
return error if username exists.
9.1.2
Lab 3 – Current Intelligent Transport System Prototype Specification
Username
14
Prove username is provided after
9.1.3
9.1.4
Retrieve
validation method.
User Self
Confirm user is able to reset password.
Password
Reset
Administratio
Validate administrator can change user
n Application
information, groups, and passwords
9.1.5
User
9.1.6
Information
Verify user can edit personal
information.
Update
Group
9.1.7
Administratio
Demonstrate the administrators ability
to create and manage groups
n
(This space was intentionally left blank.)
Lab 3 – Current Intelligent Transport System Prototype Specification
Category
Description
Test Case
15
Description
Objective
Confirm user is able to access
Application
application through one-factor
10.1.1
Access
authentication.
Token
Validate proper identification
10.1.2
Generation
token generation.
Prove access is granted only
10.1.3
Access Control
after token validation.
Confirm user is unable to access
Authentication
Unit
Module
Security Timethe system after a predetermined
10.1.4
out
time of non-use.
Validate user account is locked
Account
after multiple login failure
10.1.5
Locking
attempts.
Verify recording of a users login
time, location, authentication
10.1.6
Logging
success or failure and the page
requested.
Lab 3 – Current Intelligent Transport System Prototype Specification
16
Demonstrate the administrators
Group
ability to create and manage
10.1.7
Administration
groups
Category
Description
Test Case
Description
Objective
Confirm application opens
Database
access to the database for data
11.1.1
Connection
transfer
Validate query and result
transfer between the database
11.1.2
Query Transfer
and the Web Application Engine
modules.
Authentication
Demonstrate capability to
Integration
Module
11.1.3
Security
prevent a SQL injection attack.
11.2.1
Decision
Verify data is sent between the
Engine
Decision Engine and the Web
Connection
Application Engine.
Validate data is sent between the
Test Harness
Test Harness and the Web
11.3.1
Connection
Application Engine.
Lab 3 – Current Intelligent Transport System Prototype Specification
17
Requirements
Category ID
Description
Test Case
Description
List
Objective
Referenced
Verify listing
3.1.4.8.1
of
x.1
Advertisements advertisemen
ts.
Verify
3.1.4.8.3
submission
Business Ad
Create
of
x.2
Unit
Campaign
Advertisement
advertisemen
Module
t input fields.
Verify
modification
Edit
of
x.3
Advertisement
advertisemen
t input fields.
3.1.4.8.2
Lab 3 – Current Intelligent Transport System Prototype Specification
18
Verify
3.1.4.11.1
interface
Integration
Database
with
Interface
database for
x.4
data
input/output.
Verify
3.1.4.6.4
display of
Display
default
x.1
Default Report
ridership
trend report.
Verify
Ridership
Display
display of
Detailed
custom
3.1.4.6.4
Unit
Trend Report
x.2
Report
ridership
trend report.
Verify input
Request
fields for
x.3
Custom Report
custom
report query.
3.1.4.6.2
Lab 3 – Current Intelligent Transport System Prototype Specification
19
Verify
3.1.4.11.2
interface
Decision
Integration
x.4
Engine
Interface
with
Decision
Engine for
data
retrieval.
Verify
Display
3.1.4.7.3
display of
x.1
Default Report
default train
data report.
Display
Verify
Detailed
display of
3.1.4.7.3
Train Data
Unit
x.2
Report
Report
custom
Verify input
Request
fields for
x.3
Custom Report
custom
report query.
3.1.4.7.2
Lab 3 – Current Intelligent Transport System Prototype Specification
20
Verify
3.1.4.11.2
interface
Decision
Integration
x.4
Engine
Interface
with
Decision
Engine for
data
retrieval.
Verify
Display Rider
3.1.4.12.1
display of
x.1
Modules
modules on
Rider GUI.
Verify
Graphical User
Unit
Interface
x.2
Framework
Display
display of
Business
modules on
Modules
Business
3.1.4.12.2
GUI.
Verify
Display HRT
display of
x.3
Modules
modules on
HRT GUI.
3.1.4.12.3
Lab 3 – Current Intelligent Transport System Prototype Specification
21
Verify
interface
Module
with all Web
Interface
Application
x.4
Engine
modules.
Table 1. Test Category Identification
(This space was intentionally left blank.)
3.1.4.12
Lab 3 – Current Intelligent Transport System Prototype Specification
22
3.3 Test Schedule
The Current ITS Team will have a total of forty-five minutes to demonstrate the prototype
of Current ITS. The first ten minutes of the presentation will be allotted to setup time and
presentation of the scope of the prototype. Table 2 defines the testing schedule and the time
allotted for each section of testing. After the conclusion of the prototype demonstration, the final
fifteen minutes will be dedicated for the Current ITS team to take questions from the review
board.
Start Time
Duration
Description
Test Cases
(minutes)
(minutes)
0:00
10
Feasibility
0:10
5
Database Demo
1.0
0:15
10
Algorithm Unit
2.0,3.0
Covered
Tests
0:25
10
Integration Tests
4.1 – 4.7
-HRT
-Business
-Rider
0:35
10
System Tests
-HRT
-Business
-Rider
0:45
15
Q&A
Table 2. Test Schedule
5.0-10
Lab 3 – Current Intelligent Transport System Prototype Specification
23
3.4 Fault Reporting and Data Recording
The Current ITS team will be recording the results, success or failure, of the tests during
the prototype demonstration. The test components are defined as Database, Decision Engine
Algorithms, Test Harness and Web App Engine GUI screens. Table 3 describes these testing
components and the actions that will be taken to record potential failures of the components.
Recording Process
Component
-
Database
Report failures through visual inspection of
database records using SQL queries
Test Harness GUI
-
Document using paper forms
-
Report failures through visual inspection of
output
Decision Engine Algorithms
-
Document using paper forms
-
Report failures through visual inspection of
output in log
Web App Engine GUI
-
Document using paper forms
-
Report failures using visual inspection of GUI
screens in Web App Engine and in Test
Harness
-
Document using paper forms
Table 3. Fault Reporting and Data Recording
(This space was intentionally left blank.)
Lab 3 – Current Intelligent Transport System Prototype Specification
3.5 Resource Requirements
To demonstrate the functionality of the Current ITS prototype, specific hardware and
software resources will be required. Hardware resources will consist of a workstation with an
Internet connection to connect to the Current ITS server. Software resources will consist of the
PPHMyadmin software to view the database, an Apache webserver to host the software
application, and MySQL database software.
(This space was intentionally left blank.)
24
Lab 3 – Current Intelligent Transport System Prototype Specification
25
3.6 Test Environment
The demonstration presentation for the Current ITS prototype will take place at Old
Dominion University in Norfolk, VA, in the Gornto Center building second floor classroom. The
Current ITS team will utilize workstation at the front of the room for this purpose. Figure one
shows the layout of the classroom being used for the presentation.
Figure 1 Classroom layout