Triton Team
Lab III
Prototype Test Plan/Procedure
Date: 04/28/2008
Triton Lab III – Prototype Test Plan/Procedure
Table of Contents
1 Objective ...................................................................................................................... 3
2 References ................................................................................................................... 4
3 Test Plan ...................................................................................................................... 5
3.1 Testing Approach................................................................................................... 5
3.2 Identification of Tests ............................................................................................. 7
3.3 Test Schedule ........................................................................................................ 8
3.4 Fault Reporting and Data Recording ..................................................................... 9
3.5 Resource Requirement .......................................................................................... 9
3.6 Test Environment................................................................................................. 10
3.7 Test Responsibilities ............................................................................................ 12
4 Test Procedures ......................................................................................................... 12
4.1 RuBee™ Setup Test Cases ................................................................................. 13
4.2 RuBee™ Communication Test Cases ................................................................. 14
4.3 Triton System Prototype Software Test Cases .................................................... 15
4.4 Access Database Test Cases. ............................................................................. 19
4.5 System Scenarios Test Cases. ............................................................................ 20
5 Traceability to Requirements ...................................................................................... 22
List of Tables
Table 1 - Triton Prototype Test Identification ................................................................... 8
Table 2 - Triton Prototype Test Sequence....................................................................... 9
Table 3 - Triton Prototype Test Resource Requirements .............................................. 10
Table 4 - Demonstration Responsibilities and Assignment ........................................... 12
Table 5 - RuBee™ Tests ............................................................................................... 13
Table 6 - RuBee™ Communication Tests ................................................................ 14-15
Table 7 - Triton System Prototype Software Tests ................................................... 15-19
Table 8 - Access Database Tests ................................................................................. 19
Table 9 - System Scenarios Test ............................................................................. 20-22
Table 10 - Traceability matrix for the Triton prototype ................................................... 23
List of Figures
Figure 1 - Triton Prototype Architecture .......................................................................... 6
Figure 2 - ECS Conference Room Layout ..................................................................... 11
2
Triton Lab III – Prototype Test Plan/Procedure
1 Objective
The purpose of the Test Plan/Procedure document is to establish the overall
approach, testing sequence, and specific tests to be conducted to demonstrate
successful operation of the Triton prototype. The Triton prototype will demonstrate that
its sensor based surveillance system is feasible. Triton will prove four functional
objectives: underwater communication between RuBeeTM tags and an antenna
connected to a RuBeeTM receiver, detection of possible drowning scenarios, output, and
access control. The first functional objective deals with underwater communication. It is
very important to successfully demonstrate that RuBee TM tags can send signals to a
RuBeeTM receiver. The RuBeeTM receiver will use an antenna to capture signals from
RuBeeTM tags; furthermore, Triton will use the RuBeeTM Finder Software, provided by
Visible Assets Inc., to show the unique ID of each RuBee TM tag that is read by the
antenna. The RuBeeTM receiver will transfer the data to a laptop, provided by the ODU
Computer Science department, used to simulate the base station where the RuBee TM
Finder Software will be installed.
The second functional objective deals with the detection of possible drowning
scenarios. Based on a formula and pre-established parameters such as water density,
gravity, atmospheric pressure, and the swimmer’s arm length, the formula returns the
depth of the swimmer. In addition, the Triton System Prototype Software needs data
from a wet/dry and pressure sensor, which will be simulated, to determine when a
swimmer is in the pool and underwater. The formula is applied every second. A
drowning scenario is determined if a swimmer is in the pool, underwater, and his depth
does not change after 15 seconds.
3
Triton Lab III – Prototype Test Plan/Procedure
The third functional objective deals with the Triton System Prototype Software’s
output. The output is based on three elements: alarm, location, and archive file. Once a
drowning scenario is determined, the Pool Alert View Interface, part of the Triton
System Prototype Software, notifies lifeguards about the hazardous situation through a
pop-up window alarm; furthermore, the Pool Alert View Interface displays the swimmer’s
information and pool location. In addition, the information of the victim such as date,
time, and depth is stored into an archive file. The file is updated every time a drowning
scenario occurs.
The fourth functional objective deals with access control. Only users with a valid
username and password will have access to the system. When the Pool Alert View
Interface issues an alarm, only authorized users such as lifeguards or administrators will
be able to acknowledge the alarm and disable it. In order to disable the alarm, the
authorized users must verify that the victim is no longer underwater by checking the
pool and Pool Alert View Interface. To demonstrate how the Triton System Prototype
Software works, Triton will use pre-seeded data to simulate different swimmer
scenarios.
2 References
Barbieri, Cesar. (2008). Lab 1.1 – Triton Product Description. Virginia Beach, VA:
Author.
Barbieri, Cesar. (2008). Lab 2.1 – Prototype Product Specification for Triton. Virginia
Beach, VA: Author.
4
Triton Lab III – Prototype Test Plan/Procedure
Red Team. (2007). Room Diagram. [Figure 2]. Figure created during CS411 at Old
Dominion University. Retrieved April 14, 2008 from CPI website:
http://www.cs.odu.edu/~cpi/cpi-2-s2007/himms/diagrams.htm.
Orange Team. (2007, November). Triton Risk Management Plan. Retrieved April 23,
2008, from Triton Web site: http://www.cs.odu.edu/~cpi/cpi-f2007/triton/docs/
RiskManagementPlan.doc. Document created during CS 410 at Old Dominion
University.
3 Test Plan
The following sections will describe the types of test, methods, and tools that are
required to validate the Triton prototype. The purpose of each test is to verify that each
requirement is met. Each test will be performed in sequential order and according to
Triton’s test schedule. The result of each test will be recorded by a Triton member. The
results will be used to improve the quality of the Triton prototype.
3.1 Testing Approach
The Triton prototype performance will be verified by a successful demonstration
of each major component of the Triton Prototype Architecture and through a series of
tests cases. The components of the Triton Prototype Architecture are shown in Figure 1.
[This space is intentionally left blank]
5
Triton Lab III – Prototype Test Plan/Procedure
Figure 1 - Triton Prototype Architecture
Performance will be verified through the following components and system level
tests:
1. RuBeeTM Setup tests will verify that all hardware and software is connected
and installed properly for an optimum performance.
2. RuBeeTM Communication tests will verify that communication out-of-water,
underwater, and through concrete is possible.
3. Triton System Prototype Software tests will verify that each of the seven
interfaces of the Triton prototype software work as intended.
4. Access Database tests will verify the database tables’ schema and the
connection with the software application.
6
Triton Lab III – Prototype Test Plan/Procedure
Since dry/wet and pressure sensor’s readings will be simulated, testing at
hardware and software integration level will not be required. All tests will be conducted
in a controlled ODU classroom environment. An aquarium filled with water and a brick
will be used to test RuBeeTM transmission capabilities. During the Triton System
Prototype Software tests, pre-seeded data will be used to simulate different system
users, swimmers, and drowning scenarios; however, the system will be capable of
adding and deleting new system users and swimmers. Verification of the Triton System
Prototype Software and Access Database tests will be completed through observation
and by verifying the archive log, which will be updated every time the software detects a
drowning scenario. In addition, risks will be mitigated. Test 1 and test 2 will help mitigate
RuBeeTM software and hardware interoperability; furthermore, since the RuBeeTM Finder
Software displays only operating tags, it will help mitigate unit malfunctioning. False
positives will be mitigated by testing the system’s Pool Alert View Interface functionality
(Orange Team, 2007).
3.2 Identification of Tests
Table 1 shows a list of test cases that will be performed to validate each
component of the Triton prototype. The test cases are grouped in four categories:
RuBeeTM Setup, RuBeeTM Communication, Triton System Prototype Software, and
Access Database. A detailed description of each test case will be discussed in sections
4.1 through 4.4.
[This space is intentionally left blank]
7
Triton Lab III – Prototype Test Plan/Procedure
Category ID
Description
1
RuBeeTM Setup
2
RuBeeTM
Communication
3
Triton System
Prototype Software
4
Access Database
5
System Scenarios
Test
Case
1.1
1.2
2.1
2.2
2.3
2.4
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4.1
4.2
5.1
5.2
5.3
5.4
5.5
Description
Hardware connection
Software operation verification
Dry environment communication
Underwater communication
Underwater-brick communication
Integration testing with multiple tags
User Login Interface
Swimmer Registration Interface
Swimmer Administration Interface
Pool Alert View Interface
Prototype Detection Algorithm
Prototype Settings Interface
User Administration Interface
Verify Login table
Verify ID table
Swimmer outside the pool
Swimmer in the pool, but above water level
Swimmer in the pool moving down and up
Swimmer drowning
Multiple Swimmers
Table 1 - Triton Prototype Test Identification
3.3 Test Schedule
Triton will have 45 minutes for the setup and demonstration of the prototype. The
first five minutes will be used to set up the hardware and software required for the
demonstration. A ten minutes introduction to the scope, concepts, and feasibility of the
Triton System will follow. The last 30 minutes of the demonstration will be used to
execute the test cases in accordance with the schedule shown in Table 2.
[This space is intentionally left blank]
8
Triton Lab III – Prototype Test Plan/Procedure
Start Time
(Hours:Min)
Duration
(Minutes)
0:15
10
0:25
2
0:27
0:30
3
15
Test Objective
RuBeeTM
Communication
Access
Database
Simulated Data
Triton System
Prototype
Software
Test
Event
Dependencies
Comments
2.1, 2.2
2.3, 2.4
4.1, 4.2
None
None
None
None
3.6
3.1-3.7,
5.1-5.5
None
None
None
None
Table 2 - Triton Prototype Test Sequence
3.4 Fault Reporting and Data Recording
Two members of the Triton team will be designated to record the results of each
functional test on a printed checklist and on a power point slide during the prototype
demonstration. The purpose of the slides is to help the review panelists, during the
prototype demonstration, to easily track the results of each test. If a test result is
positive, the test will be marked as pass; otherwise, it will be marked as fail. Comments
will be recorded based on each test’s result and any error message. Triton System
Prototype Software tests results will be verified by observing the response and output of
each interface. Access Database tests results will be verified by observing the
information stored in the database. Performance tests will be verified by comparing the
results with the performance requirements.
3.5 Resource Requirement
The Triton prototype demonstration will require an ODU laptop, a RuBeeTM demo
kit, an aquarium filled with water, a brick, a projector, Microsoft Access, Microsoft .NET
9
Triton Lab III – Prototype Test Plan/Procedure
Framework, Microsoft PowerPoint, and the Triton System Prototype Software. Table 3
summarizes a detailed description of each resource.
Resource Name
ODU laptop
RuBeeTM demo kit
The aquarium
The brick
Triton Prototype Software
Microsoft Access
Microsoft .NET Framework
Microsoft PowerPoint
Projector
Description
Laptop is provided by Old Dominion University
Department of Computer Science. Laptop should include
a USB or a RS 232 communication port and an operating
system of Windows XP or Vista
The kit includes tags, a receiver, antennas, a demo kit
manual, accessories, and RuBeeTM Finder Software
The aquarium is purchased by Old Dominion University
Department of Computer Science
The brick is provided by Janet Brunelle from her backyard
The software includes seven interfaces as shown in figure
1 - Triton Prototype Architecture. The software interacts
with an Access database and uses simulated, pre-seeded
swimmer data
Microsoft Access is used to create the database for the
Triton Prototype Software
Microsoft .NET Framework is required to run the Triton
System Prototype Software
Microsoft PowerPoint is used during the feasibility
presentation
A projector is essential for the feasibility presentation
Table 3 - Triton Prototype Test Resource Requirements
3.6 Test Environment
The prototype demonstration will take place in the
Engineering and
Computational Science building’s conference room on the ODU campus. Figure 2
shows the layout of this room.
[This space is intentionally left blank]
10
Triton Lab III – Prototype Test Plan/Procedure
Figure 2 - ECS Conference Room Layout
The elements required during the demonstration are the RuBeeTM demo kit,
aquarium, brick, and laptop. These elements will be placed on the table at the left side
of Laptop 1, which is in front of the Panel of Experts. The two Triton members that will
use the elements to demonstrate underwater communication will be seated in front of
the Panel of Experts. One team member will be responsible for using the aquarium and
operating the RuBeeTM hardware while the other will be responsible for operating the
RuBeeTM Finder Software. The team member demonstrating the Triton System
Prototype Software will use Laptop 1 and will sit in front of it; furthermore, this team
member will use Projector Screen 2 to visually guide the panel of experts through each
step of the demonstration.
11
Triton Lab III – Prototype Test Plan/Procedure
3.7 Test Responsibilities
Kate Nguyen will be responsible for introducing the Triton team to the panel of
experts and concluding the overall presentation; also, she will be one of the test
recorders. Dave Larnerd will be responsible for delivering the Triton’s feasibility
presentation and will be responsible for demonstrating RuBeeTM underwater
communication. Cesar Barbieri will be responsible for demonstrating RuBeeTM
underwater communication and record the results of each test. Brandon Simpkins will
be responsible for the demonstration of the Triton System Prototype Software. All
members will field questions at the end of the presentation. Table 4 summarizes the list
of team members and their responsibilities.
Team Member
Cesar Barbieri
Responsibility








Kate Nguyen
Dave Larnerd
Brandon Simpkins
RuBeeTM underwater communication
Data recording
Introduction
Conclusion
Data recording
Feasibility presentation
RuBeeTM underwater communication
Triton System Prototype demonstration
Table 4 - Demonstration Responsibilities and Assignment
4 Test Procedures
A list of detailed tests has been prepared to ensure the Triton prototype’s
optimum performance. Each category has been divided into test cases that are
discussed in the following sections.
[This space is intentionally left blank]
12
Triton Lab III – Prototype Test Plan/Procedure
4.1 RuBee™ Setup Test Cases
Table 5 describes the RuBeeTM Setup test cases activities and their expected
results.
Description: RuBeeTM Setup: Hardware connection
Purpose: This test will verify that the RuBeeTM can be connected and
integrated
Setup Conditions: RuBeeTM demo kit required
Test Case Activity
Pass/Fail Comments Expected Result
1
Plug in the power supply and
The power light
connect it to the receiver
illuminates on the
receiver
2
Connect the receiver to the ODU
The laptop recognizes
laptop’s RS-232 serial or USB
the receiver
port using the null modern cable
3
Connect the antenna to the
The Finder Software
receiver
should recognize the
receiver
Test Category ID: 1
Test Case: 1.1
Description: RuBeeTM Setup: Software operation verification
Purpose: This test will verify that the RuBeeTM Finder Software can
operate on the ODU student laptop
Setup Conditions: RuBeeTM Finder Software and ODU laptop required
Test Case Activity
Pass/Fail Comments Expected Result
1
Locate the RuBeeTM Finder
The icon is found
Software icon
2
Open the Finder Software by
The software can be
double clicking on it
opened
3
Verify that the software can
The antenna, tags, and
recognize the antenna and the
receiver are verified by
receiver
the software
Test Category ID: 1
Test Case: 1.2
Table 5 - RuBee™ Tests
[This page is intentionally left blank]
13
Triton Lab III – Prototype Test Plan/Procedure
4.2 RuBee™ Communication Test Cases
Table 6 describes the RuBeeTM Communication test cases activities and their
expected results.
Description: RuBeeTM Communication: Dry environment communication
Purpose: This test will verify that RuBeeTM tags can transmit in a dry
environment
Setup Conditions: Test 1.1 and 1.2 should be successfully completed
Test Case Activity
Pass/Fail Comments Expected Result
1
Position the tag outside of
Tag ID is displayed on
aquarium and within antenna
the RuBeeTM Finder
range
Software screen
2
Position the tag outside of
Tag ID is not displayed on
aquarium and outside of
the RuBeeTM Finder
antenna range
Software screen
Test Category ID: 2
Test Case: 2.1
Description: RuBeeTM Communication: Underwater communication
Purpose: This test will verify that RuBeeTM tags can transmit underwater
Setup Conditions: Test 1.1 and 1.2 should be successfully completed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Position the tag inside of
The tag ID is displayed
aquarium and within antenna
on the RuBeeTM Finder
range
Software screen
Test Category ID: 2
Test Case: 2.2
Description: RuBeeTM Communication: Underwater-brick communication
Purpose: This test will verify that RuBeeTM tags can transmit underwater
and through a brick
Setup Conditions: Test 1.1 and 1.2 should be successfully completed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Position the tag inside of the
The tag ID is displayed
aquarium, under the brick, and
on the RuBeeTM Finder
within antenna range
Software screen
Test Category ID: 2
Test Case: 2.3
[This page is intentionally left blank]
14
Triton Lab III – Prototype Test Plan/Procedure
Description: RuBeeTM Communication: Integration testing with multiple tags
Purpose: This test will verify that multiple RuBeeTM tags can transmit
underwater
Setup Conditions: Test 1.1 and 1.2 should be successfully completed
Test Case Activity
Pass/Fail
Comments Expected Result
1
Position all tags inside of
Each tag ID is displayed
aquarium and within antenna
on the RuBeeTM Finder
range
Software screen
Test Category ID: 2
Test Case: 2.4
Table 6 - RuBee™ Communication Tests
4.3 Triton System Prototype Software Test Cases
Table 7 describes the Triton System Prototype Software test cases activities and
their expected results.
Test Category ID: 3
Test Case: 3.1
Description: Triton System Prototype Software: User Login Interface
Purpose: This test will verify that the User Login Interface accepts
authorized users and rejects unauthorized users. Also, verified users are
granted appropriate access
Setup Conditions: Triton System Prototype installed and running on ODU
laptop
Test Case Activity
Pass/Fail Comments
Expected Result
1
An error message is
Invalid username and/or
displayed and system
password attempt login
access is not granted
2
Administrator user type attempt
Full system access
login
granted
System access granted to
Swimmer Registration,
3
Cashier user type attempt login
Swimmer Administration,
and Prototype Settings
System access granted to
Lifeguard user type attempt
4
Pool Alert View and
login
Prototype Settings
[This page is intentionally left blank]
15
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 3
Description: Triton System Prototype Software: Swimmer Registration
Interface
Test Case: 3.2
Purpose: This test will verify that the Swimmer Registration Interface
allows the addition of new swimmers
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. Swimmer Registration Interface tab is selected
Test Case Activity
Pass/Fail Comments
Expected Result
1
Add a new swimmer by filling
New swimmer is added
out all fields listed in Lab II
and visible in the
Prototype Product Specification
Swimmer Administration
for Triton section 3.1.4.1 and
Interface
3.1.4.2
2
Add a new swimmer filling out
New swimmer is not
all fields listed in Lab II
added and an error
Prototype Product Specification
message is displayed
for Triton section 3.1.4.1 with a
wristband that is already in use
Test Category ID: 3
Description: Triton System Prototype Software: Swimmer Administration
Interface
Test Case: 3.3
Purpose: This test will verify that the Swimmer Administration Interface
allows the removal of individual swimmers or all registered swimmers
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. Swimmer Administration Interface tab is selected
Test Case Activity
Pass/Fail Comments
Expected Result
1
Select a swimmer from the
Swimmer’s information is
swimmer selection list
displayed
2
Select one swimmer from the
Selected swimmer is
swimmer selection list and click
removed and visibly
Remove Swimmer button to
verifiable in the Swimmer
remove swimmer
Administration Interface
Select Clear Fields button to
3
All swimmers are
remove all active swimmers
removed
[This page is intentionally left blank]
16
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 3
Test Case: 3.4
Description: Triton System Prototype Software: Pool Alert View Interface
Purpose: This test will verify that the Pool Alert View Interface provides a
visual representation of all the swimmers and alarms the lifeguard of a
potential drowning victim
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. Pool Alert View Interface tab is selected
Test Case Activity
Pass/Fail Comments
Expected Result
1
Verify that a list of active
A list of active swimmers
is displayed in the Safe
swimmers is displayed in the
Safe Swimmers box
Swimmers box
2
Verify that potential drowning
A list of potential drowning
victims are displayed in the
victims is displayed in the
Potential Drowning Victims box
Potential Drowning
Victims box
3
Simulation of a potential
An alarm message will be
drowning victim (see test case
displayed and the location
3.6 for detail)
of the victim will be
highlighted on the aerial
view of the pool and all
active swimmers’ data is
archived
4
Disable an alarm with a proper
Alarm is disabled
username and password.
Potential drowning victim is no
longer underwater
5
Disable an alarm with a proper
Alarm is not disabled
username and password.
Potential drowning victim is still
underwater
6
Disable an alarm with invalid
Alarm is not disabled
combination of username and
password
7
Step through simulated
Scenario results display
scenario
second by second view
where a user can
progress and digress
through the scenario
[This page is intentionally left blank]
17
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 3 Description: Triton System Prototype Software: Prototype Detection
Algorithm Interface
Test Case: 3.5
Purpose: This test will verify that the Prototype Detection Algorithm Interface
can calculate the depth of a swimmer using simulated sensor readings,
swimmer arm length, and environments constants
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. Prototype Detection Algorithm Interface tab is selected
Test Case Activity
Pass/Fail Comments Expected Result
1
Fill out the required fields under
The swimmers’ depth is
Sensor Readings and
displayed
Environment Variables
Test Category ID: 3
Test Case: 3.6
Description: Triton System Prototype Software: Prototype Settings Interface
Purpose: This test will verify that the Prototype Settings Interface loads
swimmers’ data and swimmers’ scenarios into the Triton System Prototype
Software
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. Prototype Settings Interface tab is selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Select the swimmers information
Swimmers’ data loaded
file. Click the load button
and viewable through the
Swimmer Administration
Interface
2
Select the swimmer scenario file.
Swimmers’ scenario
Click the load button
loaded and viewable
through the Pool Alert
View Interface
[This page is intentionally left blank]
18
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 3
Description: Triton System Prototype Software: User Administration
Interface
Test Case: 3.7
Purpose: This test will verify that the User Administration Interface adds
users to the login database table
Setup Conditions: Triton System Prototype installed and running on ODU
laptop. User Administration Interface tab is selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Add a new user to the system by
New user added to the
entering username, password,
database
and user type
2
List all valid users
Display of all valid users
3
Remove user(s) from the
User(s) removed from the
system.
database.
4
Reset a user’s password
Old password in database
is deleted. New password
is saved in database
Table 7 - Triton System Prototype Software Tests
4.4 Access Database Test Cases.
Table 8 describes the Access Database test cases activities and their expected
results.
Test Category ID: 4
Test Case: 4.1
Description: Access Database: Login table
Purpose: This test will verify that the database contains a login table
Setup Conditions: Microsoft Access installed and running on ODU laptop
Test Case Activity
Pass/Fail
Comments Expected Result
1
Check Login table schema as
Login table has the
specified in Lab II Prototype
required schema
Product Specification for Triton
section 3.1.9.1
Test Category ID: 4
Test Case: 4.2
Description: Access Database: ID table
Purpose: This test will verify that the database contains an ID table
Setup Conditions: Microsoft Access installed and running on ODU laptop
Test Case Activity
Pass/Fail
Comments Expected Result
1
Check ID table schema as
ID table has the required
specified in Lab II Prototype
schema
Product Specification for Triton
section 3.1.9.2
Table 8 - Access Database Tests
19
Triton Lab III – Prototype Test Plan/Procedure
4.5 System Scenarios Test Cases.
Table 9 describes the System Scenarios test cases activities and their expected
results.
Test Category ID: 5
Test Case: 5.1
Description: System Testing: Swimmer outside the pool
Purpose: This test will verify the behavior of the Triton System Prototype
Software with one swimmer outside the water
Setup Conditions: The Triton System Prototype Software and Access
Database must be installed and running properly; furthermore, the Pool Alert
View tab must be selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load swimmer outside the pool
A successful loading
scenario
scenario message is
displayed
2
Click on the desired swimmer’s
The swimmer ID is
wristband ID
highlighted and a brown dot
representing the location of
the swimmer outside the
pool is displayed
Click the Next and Previous
3
Simulated swimmer in the
buttons to step through the
pool will move.
scenario in one second interval
Test Category ID: 5
Test Case: 5.2
Description: System Testing: Swimmer in the pool, but above water level
Purpose: This test will verify the behavior of the Triton System Prototype
Software with one swimmer in the water
Setup Conditions: The Triton System Prototype Software and Access
Database must be installed and running properly; furthermore, the Pool Alert
View tab must be selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load swimmer in the pool, but
A successful loading
above water level scenario
scenario message is
displayed
2
Click on the desired swimmer’s
The swimmer ID is
wristband ID
highlighted and a brown dot
representing the location of
the swimmer above the
water level is displayed
Click the Next and Previous
3
Simulated swimmer in the
buttons to step through the
pool will move.
scenario in one second interval
20
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 5
Test Case: 5.3
Description: System Testing: Swimmer in the pool moving down and up
Purpose: This test will verify the behavior of the Triton System Prototype
Software with one swimmer in the water moving down and up
Setup Conditions: The Triton System Prototype Software and Access
Database must be installed and running properly; furthermore, the Pool Alert
View tab must be selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load swimmer in the pool, but
A successful loading
above water level scenario
scenario message is
displayed
2
Click on the desired swimmer’s
The swimmer ID is
wristband ID
highlighted and a brown dot
representing the location of
the swimmer underwater is
displayed
Click the Next and Previous
3
Simulated swimmers in the
buttons to step through the
pool will move. When the
scenario in one second interval
swimmer is underwater, the
brown dot changes to blue
Test Category ID: 5
Test Case: 5.4
Description: System Testing: Swimmer drowning
Purpose: This test will verify the behavior of the Triton System Prototype
Software with one swimmer drowning
Setup Conditions: The Triton System Prototype Software and Access
Database must be installed and running properly; furthermore, the Pool Alert
View tab must be selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load swimmer in the pool, but
A successful loading
above water level scenario
scenario message is
displayed
2
Click on the desired swimmer’s
The swimmer ID is
wristband ID
highlighted and a brown dot
representing the location of
the swimmer is displayed
Click the Next and Previous
3
Simulated swimmer in the
buttons to step through the
pool will move. When the
scenario in one second interval
swimmer is underwater, the
brown dot changes to blue.
If the swimmer is drowning,
a pop-up window alarm will
be displayed
4
Make sure the swimmer is no
Alarm is deactivated
longer underwater and enter
the username and password to
deactivate the alarm.
21
Triton Lab III – Prototype Test Plan/Procedure
Test Category ID: 5
Test Case: 5.5
Description: System Testing: Multiple swimmers
Purpose: This test will verify the behavior of the Triton System Prototype
Software with multiple swimmers
Setup Conditions: The Triton System Prototype Software and Access
Database must be installed and running properly; furthermore, the Pool Alert
View tab must be selected
Test Case Activity
Pass/Fail
Comments Expected Result
1
Load multiple swimmers
A successful loading
scenario
scenario message is
displayed
Click
the
Next
and
Previous
2
Simulated swimmers in the
buttons to step through the
pool will move and events
scenario in one second interval
described in test cases 5.1
– 5.4 will be illustrated
Table 9 - System Scenarios Test
5 Traceability to Requirements
Each test case has been designed to verify that one or more prototype
requirements are met. The traceability matrix shown in Table 10 illustrates the
relationship between requirements and test cases.
[This page is intentionally left blank]
22
Triton Lab III – Prototype Test Plan/Procedure
Requirements
Component
Req ID
RuBeeTM Setup
3.1.1
3.1.2.1
Underwater
3.1.2.2
Communication
3.1.2.3
3.1.3.1
3.1.3.2
User Login
3.1.3.3
Interface
3.1.3.4
3.1.3.5
Swimmer
3.1.4.1
Registration
Interface
3.1.4.2
Swimmer
3.1.4.3
Administration
Interface
3.1.4.4
3.1.5.1
3.1.5.2
Pool Alert View
Interface
3.1.5.3
3.1.5.4
3.1.6.1
Prototype
3.1.6.2
Detection
Algorithm
3.1.6.3
Interface
3.1.6.4
Prototype Settings
3.1.7.1
Interface
3.1.7.2
3.1.8.1
3.1.8.2
User
Administration
3.1.8.3
Interface
3.1.8.4
3.1.8.5
3.1.9.1
Access Database
3.1.9.2
3.1.10.1
Simulated Data
3.1.10.2
3.1.11.1
3.1.11.2
Swimmer
Simulation
3.1.11.3
3.1.11.4
1.1
X
1.2
X
2.1
2.2
2.3
2.4
X
X
X
X
X
X
3.1
Test Cases
3.2 3.3 3.4
3.5
3.6
3.7
4.1
4.2
5
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Table 10 - Traceability matrix for the Triton prototype
23