Lab 3 – Don’t Forget Me: Prototype Test Plan/Procedure
Brandon Fields
CS411
Janet Brunelle
April 16, 2008
Brandon Fields - Lab 3
Table of Contents
1
2
3
Objectives ................................................................................................................... 1
References ................................................................................................................... 3
Test Plan...................................................................................................................... 3
3.1
Testing Approach ................................................................................................ 4
3.2
Identification of Tests ......................................................................................... 7
3.3
Test Schedule ...................................................................................................... 8
3.4
Fault Reporting and Data Recording .................................................................. 9
3.5
Resource Requirements .................................................................................... 10
3.6
Test Environment .............................................................................................. 10
3.7
Test Responsibilities ......................................................................................... 12
4 Test Procedures ......................................................................................................... 12
4.1
Test Case Names and Identifiers....................................................................... 13
5 Traceability to Requirements .................................................................................... 20
List of Figures
Figure 1- Phase 1 prototype major functional component diagram ................................... 4
Figure 2. Presentation room layout ................................................................................. 11
List of Tables
Table 1- DFM system prototype test cases by category ..................................................... 8
Table 2- DFM system prototype test schedule ................................................................... 9
Table 3, Traceability to requirements table ...................................................................... 21
ii
Brandon Fields - Lab 3
1 Objectives
The first functional objective is to test the installation of LabVIEW to determine if
it is suitable for running the DFM prototype. Since LabVIEW is the interface
environment used to interact with the sensors and holds the logic of the DFM system’s
operation, it will be the focus of the presentation. LabVIEW’s drivers and time to load
will be scrutinized in this portion of the demonstration. Success in demonstrating the
DFM system will rely on LabVIEW being fully functional.
The second objective is to demonstrate the various sensors that the DFM system
utilizes. The first sensor to be demonstrated is the one and only environmental sensor, the
temperature sensor. Through the LabVIEW interface, one will be able to see the current
room temperature and a graph of recently retrieved values. As with all of the other
sensors, a virtual instrument (VI) has been programmed to interpret the sensor’s data into
meaningful information. To begin the Life detection sensors, a pulse oximeter sensor
will be used to aid in determining if life is present in a vehicle. The pulse oximeter will
be attached to an individual’s finger to detect the presence of a pulse. The third device,
the motion sensor, will indicate movement in real time when LabVIEW displays a value
of one for motion detected and zero for none. The hardware alone is capable of
indicating this through a light emitting diode (LED) that turns on when motion is
detected. The fourth device is the pressure sensor; this sensor will be implemented with
simulated data. When the data values reached a threshold indicating a significant
pressure value, LabVIEW will register a positive reading for human detection. The fifth
device is the microphone. The microphone will simply indicate the level of noise
detected through the computer’s microphone. LabVIEW has been programmed to give a
1
Brandon Fields - Lab 3
positive life detection value when the noise level reaches volume of a normal
conversation within five feet. Lastly, the CO2 sensor will be demonstrated in LabVIEW
with the use of prerecorded data. The simulated sensor will demonstrate a steadily rising
CO2 value which will indicate life. Each sensor has a pre-defined value that is used in the
life detection algorithm. If the sum of the values returned from sensors is greater than
five, then the algorithm will determined that life is present.
The following objectives address the aspects of the DFM system that require direct
human interaction. The first to be demonstrated is the transmitter/receiver system. A set
of radio frequency devices will interact, one inside the laptop and the other a handheld
device, until one goes out of range. The demonstration of the transmitter/receiver system
will simulate a parent walking away from the vehicle with a key fob communicating with
the vehicle. The alarm will turn on in response to the prior demonstration as well as one
requiring an extreme temperature value. Lastly, the reset will be used in both previously
mentioned cases to restore the state of the DFM system.
For the last objective the development team will demonstrate the DFM system’s
ability prevent false alarms in order to ensure that the system has a high success rate and
performs its overall goal of saving lives. Risk of false alarms will be assessed based on
the DFM system ability to analyze the different values each sensor provides. If there is
the correct value for life detection the system will accept that a person is present. Adding
more sensors to the implementation would further mitigate that risk. The DFM system
development team increased the number of life detection sensors to five to give the life
detection algorithm a means of accurately assessing the environment. By increasing the
number of sensors further, accuracy could be increased. The development team will be
2
Brandon Fields - Lab 3
able to demonstrate this concept by disabling a range of sensor so that the audience can
better understand who the DFM system relies exclusively on the sensors to make
decisions.
Finally, a run-through of the activation process will take place to demonstrate the
DFM system’s ability to assess its own performance. Since this process would run each
time the vehicle is shut off, it is necessary to demonstrate that it can run autonomously.
Successfully passing all objectives will prove that the DFM system can be implemented
inside of a vehicle with minimal human interaction.
2 References
Fields, Brandon. (2008). Lab 1 – DFM Product Description. Norfolk, VA: Author.
Kids and Cars. (n.d.). Kids and Cars. Retrieved January 28, 2007, from Kids and Cars
Web site: http://www.kidsandcars.org/.
Oximity. (2002). Principles of Pulse Oximetry Technology. Retrieved January 21, 2007,
from Internet World Stats Web site: http://www.oximetry.org/pulseox/principles.
htm.
3 Test Plan
This section covers the types of tests to be performed, testing schedule, reporting
procedures, resource requirements, the testing environment, and team member
responsibilities. The test plan describes the tests that will take place when demonstrating
the DFM system. The functions of the DFM system that are tested are described in the
team member responsibilities.
(This space intentionally left blank.)
3
Brandon Fields - Lab 3
3.1 Testing Approach
The DFM system prototype is tested through unit, integration, system testing
procedures. By partitioning the prototype in separate elements, the review panel can
better follow the evaluation of the DFM system’s performance. Steps one through six are
the unit tests, step seven is the integration test, step eight is the system test, and step nine
is risk mitigation. A basic layout of the DFM system is provided in the major functional
components diagram in Figure 1.
Figure 1- Phase 1 prototype major functional component diagram
4
Brandon Fields - Lab 3
The first step of testing the individual components of the DFM system is to test
the LabVIEW setup. LabVIEW will be tested to ensure that it is installed and can be run
with no delays. LabVIEW is absolutely necessary for the DFM system since all of the
logic and interface was implemented using LabVIEW.
The second step is making sure that the environmental sensor performs accurately
and can make adjustments in a relatively short period of time. The thermistor will
generate values to be displayed in LabVIEW, which will coincide with the temperature of
the room or the temperature extremes it will be exposed to. A temperature sensor will
determine when it is unsafe for anyone to be in the vehicle and therefore must take
measurements at all times.
The third step is to test the life detection sensors to make sure that each sensor can
perform its task with a high level of precision and accuracy. The first of the life detection
sensors is the pulse oximeter. The pulse oximeter will generate values to indicate that it
is working, and then it will be evaluated based on its ability to generate values within an
acceptable range. The pulse oximeter will be expected to generate values within an
acceptable time period as well. The motion sensor will also generate values to indicate
that it is working, and then it will be evaluated based on its ability to generate values
within an acceptable range. The motion sensor will be expected to generate values within
an acceptable time period as well. The pressure sensor will be simulated. The sensor will
still need to send the signal in the required time. The microphone after receiving sound
data will indicate when a specified decibel level is reached and will do so within a
specified period of time. The CO2 sensor will be simulated. The sensor will still need to
send the signal in the required time.
5
Brandon Fields - Lab 3
The fourth, fifth, and sixth steps will test the human interaction devices to ensure
they are working properly. The transmitter/receiver system will be used to indicate that
the driver has left the vehicle. The transmitter and receiver must be test in tandem since
they confirm one another’s data. The transmitter will send a signal to the receiver and the
receiver will indicate that it is receiving data from that particular device. The transmitter
and receiver will also need to send and respond it the required time. The next device is
the alarm; the alarm will receive an activation signal and a signal to stop. This will cause
the alarm sound file to play for a short instance. The alarm also needs to go off in the
specified time. Lastly, the reset is tested. The system needs to reset the DFM system to
its initial state when pressed. It also needs to reset the DFM system is the required time.
The seventh step will test the DFM system activation process. The activation
process will be tested for checking each sensor and that is finishes the activation in the
specified time. The activation process is necessary to ensure that the system can run
autonomously. The activation process tests each of the sensors values to make sure they
are acceptable.
The ninth step is system testing, which will involve running the DFM system
trough a set of scenarios to ensure that all of the logic is correctly implemented. This test
involves setting off enough sensors for the DFM system to detect life while the
preemptive reset is enabled and the temperature sensor is forced off. The DFM system
should continue to run until the preemptive reset is disabled of the temperature value
reaches 89. Pressing the reset button will reset the system and disable the preemptive
reset. The second feature that the system test must cover is testing when the driver is
gone and the temperature is low, which will cause an alarm. The last feature is the error
6
Brandon Fields - Lab 3
system that was programmed into the DFM. In the event that too few sensors are
working, the driver will be alerted. Likewise, if both the key fob and temperature devices
are not work the driver must also be alerted.
All of the tests will be performed using LabVIEW, the DFM system software, and
the previously mentioned sensors. Each of the sensors will be verified using the graph
data that the DFM interface provides and the LEDs programmed to indicate exceptional
values. Logs of all the data generated during the prototype demonstration can be
observed for further validation.
3.2 Identification of Tests
The system will be tested based on a break-down or its constituent parts. To
ensure that the system is thoroughly tested, the DFM system will test the software
interface, the two groups of sensors, the 3 aspects of human interactivity, and the
automated self test. The items required to identify the tests are category id, category
description, test case number, and the description the test case. Table 1 shows the test
cases that will be performed; specific details for each test are described in section 4.1.
(This space intentionally left blank.)
7
Brandon Fields - Lab 3
Category ID
1
2
Description
LabVIEW
1.1
Environmental Sensor
2.1
4.2
Verify receiver’s behavior and
performance.
3.3
3.4
3.5
4
Transmitter and Receiver
5
Alarm
6
Reset
5.1
6.1
7.1
7.2
7
7.3
Activation
Verify temperature sensor’s behavior
and performance.
4.1
3.2
Life Detection Sensors
Verity LabVIEW is installed and
operational.
Verify pulse oximeter sensor’s behavior
and performance.
Verify pressure sensor’s behavior and
performance.
Verify microphone’s behavior and
performance.
Verify C02 sensor’s behavior and
performance.
Verify motion sensor’s behavior and
performance.
Verify transmitter’s behavior and
performance
3.1
3
Description
Test Case
7.4
7.5
8
Risks Mitigation
8.1
9
System Integration
9.1
Verify alarm’s behavior and
performance.
Verify behavior of the DFM system while
reset is activated.
Verify each sensor will send a signal to
LabVIEW.
Verify each sensor’s value will be greater
or equal to its rated minimum value.
Verify each sensor’s value will be less
than or equal to its rated maximum
value.
Verify each sensor will return a value
within 10 seconds.
Verify the entire activation will take no
more than 60 seconds.
Verify error detection
Verify behavior and performance for all
components of the DFM system when
components are integrated.
Table 1- DFM system prototype test cases by category
(This space intentionally left blank.)
8
Brandon Fields - Lab 3
3.3 Test Schedule
The demonstration of the DFM system prototype is scheduled to take 60 minutes.
The first five minutes of the presentation will be devoted to the setup of the DFM system.
The following 10 minutes will be used to explain the concept of the DFM system and
give an introduction of the development team. The remaining time has been scheduled
out in Table 2.
Start Time
(hours:min)
0:15
0:16
0:21
Duration
(minutes)
1
5
10
Test Objective
0:31
0:32
0:33
0:34
1
1
1
5
Transmitter and Receiver
Alarm
Reset
Activation
0:39
0:40
1
5
Risks Mitigation
System Integration
LabVIEW
Environmental Sensor
Life Detection Sensors
Test
Event(s)
1.1
2.1
3.1, 3.2,
3.3, 3.4,
3.5
4.1, 4.2
5.1
6.1
7.1, 7.2,
7.3, 7.4
8.1
9.1
Dependencies
Comments
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Table 2- DFM system prototype test schedule
3.4 Fault Reporting and Data Recording
A member from the development team is responsible for recording the results of
each of the tests and taking notes on the DFM system’s performance. The tests will be
recorded as either passing or failing. Each test case will be verified using the graph data
generated in LabVIEW and the static data each sensor displays in the DFM interface. As
each of the virtual instruments run in LabVIEW a log file will be generated with the
values that were displayed on the DFM interface. Performance can be assessed by
observing the log files generated throughout the demonstration.
9
Brandon Fields - Lab 3
3.5 Resource Requirements
The demonstration of the DFM system prototype will require a copy of the
LabVIEW software to be installed at least two laptops with one available USB port. One
laptop will be used for the presentation and the other one for a backup. A DAQ USB6008 must be used to interact with the sensors, and two nine volt batteries must be used
to power the sensors. Both laptops will need the drivers for interfacing with the DAQ to
be installed. Also all of the virtual instruments and accompanying media files must be
present on both laptops. Each of the sensors that interface with LabVIEW through the
DAQ must be connect appropriately. A thermistor will be used for measuring the room
temperature. A hair dryer will be used for heating the thermistor to a temperature above
90 degrees Fahrenheit, and a cup filled with ice will be used to demonstrate that the
thermistor can be cooled. A radio controlled car controller will be used to interface with
the DFM systems radio frequency system. The motion sensor, which was assembled
with a circuit kit and ultrasonic motion sensors, will be used to detect movement. A
pulse oximeter will be used to measure the heart rate of one of the team members. A
computer microphone will be used to measure the amount of noise in the room, and the
computer’s speakers will be used to play the alarm sound file. The laptop will also need
a program capable of viewing ASCII text files generating by the logging feature of the
DFM system.
3.6 Test Environment
The prototype demonstration will take place in the conference room on the third
floor of Computer Science and Engineering building. A depiction of the room is
provided in Figure 2. The DFM system development team will be seated at the back of
10
Brandon Fields - Lab 3
the room in front of “Projector Screen 2”, with the review panel facing the development
team on the opposite side of the room.
Figure 2. Presentation room layout
The team member responsible for taking notes and performing documentation
will sit on the same side of the room as the review panel. The team member responsible
for running the LabVIEW software will sit at the table behind the depiction of “Laptop 2”
from figure 2. The LabVIEW interface will be displayed on both projector screens. Prior
to the demonstration the hardware will be connected to either the computer directly or
through the data acquisition unit (DAQ). The sensors will be placed across the table for
the review panel to observe prior to their use in the presentation.
(This space intentionally left blank.)
11
Brandon Fields - Lab 3
3.7 Test Responsibilities
The project manager is responsible for beginning the presentation and introducing
the development team. A second team member will assist the project manager in
delivering the presentation of the DFM system by performing the tests in LabVIEW. A
third team member will be responsible for influencing each of the sensors in order to
make them generate data within a desired range. The third member of the team will heat
and cool the temperature sensor and will be responsible for making the motion sensor
detection movement. A fourth team member will be responsible for influencing the
microphone and the pulse oximeter. The fourth team member will have to place the pulse
oximeter on their finger and may have to direct the microphone so that it may receive an
optimal reading. The fifth team member will be responsible for documenting which of
the test cases passed and notes pertaining to the performance of the system throughout the
presentation.
4 Test Procedures
The test procedures describe the each of the tasks that will take place in order to
effectively test the DFM system. Likewise, this section will address each test’s
relationship with the previously defined requirements, and what the expected outcome
will be for each of the test cases. The procedures will effectively map out the
demonstration of the DFM system prototype.
(This space intentionally left blank.)
12
Brandon Fields - Lab 3
4.1 Test Case Names and Identifiers
Requirements Traceability – a reference to the requirements that the
test case will address.
Description of Test - a short description of the test’s goals.
Test Inputs – details of the input parameters used when performing
the test.
Test Procedure – instructions of how to perform the test.
Expected Result – the results that are desired for the test used to verify
that the test had a positive result.
Special Instructions – details about performing the test the team
member needs to be aware of in order to successfully perform the
operation.
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedure
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
1.1
3.1.7.1, 3.1.7.2, 3.1.7.3, 3.1.7.4, 3.1.7.5, 3.1.7.6, 3.1.7.7, 3.1.8.1,
3.1.8.2, 3.1.8.3
Verify LabVIEW is installed and operational
N/A
1. Double click the LabVIEW the DFM.vi file to launch the
program.
2. Check version to match version 8.2 or greater.
3. Locate DFM VI, go to the block diagram and double click
the DAQ assistant block to verify the DAQ is working.
4. Verify sensors are connected to the correct channels on
DAQ.
5. Verify Data points are correct.
6. Verify the wires within the prototype box are connected
correctly.
LabVIEW installed and fully operational
1. Exit all non-essential programs before launching LabVIEW.
2.1
3.1.1.1.1, 3.1.1.1.2, 3.1.1.3.1, 3.1.1.3.2, 3.1.3.1, 3.1.3.2, 3.1.8.1,
3.1,8.2, 3.1.8.3, 3.2.2.2.1, 3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5,
3.2.3.1.1, 3.2.3.1.2, 3.2.3.1.3, 3.2.3.1.4, 3.2.3.2.1, 3.2.3.2.2, 3.2.3.2.3
Verify temperature sensor’s behavior and performance
1. Input value greater than 30 ºF and less than 90 ºF
13
Brandon Fields - Lab 3
Test Procedures
Expected Results
2.
3.
1.
2.
3.
4.
5.
6.
7.
8.
1.
2.
3.
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
1.
2.
Input value less than or equal to 30 ºF
Input value greater than or equal to 90 ºF
Turn Temperature sensor switch on.
Turn all other sensors off.
Turn DFM VI on.
Verify temperature value.
Apply cool air to the temperature sensor.
Verify temperature value.
Apply hot air to the temperature sensor.
Verify temperature value.
System will not react when temperature is between 30º F and
90º F.
Alarm will sound when temperature is below or equal to 30
ºF.
Alarm will sound when temperature is above or equal to 90 º
F.
For cooling the temperature sensor, place sensor in ice.
For heating the sensor, place sensor in close proximity to
hair dryer or heater.
3.1
3.1.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.2, 3.1.2.1, 3.1.2.2, 3.1.2.3,
3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.8.1, 3.1.8.2, 3.1.8.3, 3.2.2.1.3, 3.2.2.2.1,
3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5
Verify pulse oximeter sensor’s behavior and performance
Pulse sensor’s signal
1. Turn pulse oximeter sensor switch on.
2. Turn all other sensors off.
3. Turn DFM VI on.
4. Verify value from sensor.
5. Verify danger value.
6. Attach pulse oximeter’s clip to finger of test subject.
7. Verify value from sensor.
8. Verify danger value.
1. No occupant was detected while pulse oximeter’s clip was
not attached to test subject’s finger and danger value of zero
is returned.
2. Occupant was detected when pulse oximeter was attached to
finger of subject and danger value of four is returned.
N/A
3.2
3.1.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.3, 3.1.2.1, 3.1.2.2, 3.1.2.3,
3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.8.1, 3.1.8.2, 3.1.8.3, 3.2.2.1.2, 3.2.2.2.1,
3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5
Verify pressure sensor’s behavior and performance.
14
Brandon Fields - Lab 3
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
1. Simulated signal
1. Turn on pressure sensor’s switch.
2. Turn off all other sensors.
3. Verify value from sensor.
4. Verify danger value.
5. Apply simulated pressure signal.
6. Verify value from sensor.
7. Verify danger value
1. LED turned off with no simulated signal and danger value of
zero is returned.
2. LED turned on with simulated signal and danger value of
two is returned.
N/A
3.3
3.1.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.4, 3.1.2.1, 3.1.2.2, 3.1.2.3,
3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.8.1, 3.1.8.3, 3.2.2.1.1, 3.2.2.2.1,
3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5
Verify microphone’s behavior and performance.
1. Tester’s voice
1. Turn on microphone’s switch.
2. Turn off all other sensors.
3. Verify value from microphone.
4. Verify danger value.
5. Tester speaks into microphone.
6. Verify value from microphone.
7. Verify danger value.
1. LED turned off when no existence of noise and danger value
of zero is returned.
2. LED turned on when tester speaks into microphone and
danger value of one is returned.
1. Ensure silence during testing, except for the voice of the tester.
3.4
3.1.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.5, 3.1.2.1, 3.1.2.2, 3.1.2.3,
3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.8.1, 3.1.8.2, 3.1.8.3, 3.2.2.1.4, 3.2.2.2.1,
3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5
Verify C02 sensor’s behavior and performance.
1. Simulated signal.
1. Turn on C02 sensor’s switch.
2. Turn off all other sensors.
3. Verify value from sensor.
4. Verify danger value.
5. Apply simulated C02 signal.
6. Verify value from sensor.
7. Verify danger value.
15
Brandon Fields - Lab 3
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
1. LED turned off with no simulated signal and danger value of
zero is returned.
2. LED turned on with simulated signal and danger value of
three is returned.
N/A
3.5
3.1.1.1.1, 3.1.1.1.2, 3.1.1.2.1, 3.1.1.2.6, 3.1.2.1, 3.1.2.2, 3.1.2.3,
3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.8.1, 3.1.8.2, 3.1.8.3, 3.2.2.2.1, 3.2.2.2.2,
3.2.2.2.3, 3.2.2.2.4, 3.2.2.2.5
Verify motion sensor’s behavior and performance.
1. Displacement of object.
1. Turn on motion sensor’s switch.
2. Turn off all other sensors.
3. Verify value from sensor.
4. Verify danger value.
5. Move object greater than one inch.
6. Verify value from sensor.
7. Verify danger value.
1. LED turned off without movement and danger value of zero
is returned.
2. LED turned on with movement and danger value of three is
returned.
1. Ensure there is no movement in range of the motion sensor,
except for the movement of the test subject.
4.1
3.1.4.1, 3.1.4.2, 3.1.4.3, 3.2.2.2.1, 3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4,
3.2.2.2.5, 3.2.4.1, 3.2.4.2, 3.2.4.3
Verify transmitter’s behavior and performance.
N/A
1. Turn on transmitter’s switch.
2. Turn off all other sensors.
3. Verify results.
1. LED turned off when transmitter’s switch turned off.
2. LED turned on when transmitter’s switch turned on.
1. Ensure no other BluTooth devices are enabled or in range during
testing.
4.2
3.1.4.1, 3.1.4.2, 3.1.4.3, 3.2.2.2.1, 3.2.2.2.2, 3.2.2.2.3, 3.2.2.2.4,
3.2.2.2.5, 3.2.4.1, 3.2.4.2, 3.2.4.3
Verify receiver’s behavior and performance.
1. Signal from transmitter.
1. Turn on receiver and transmitter’s switch.
2. Turn off all other sensors.
16
Brandon Fields - Lab 3
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
3. Verify results.
4. Locate transmitter beyond 20 ft.
5. Verify results.
1. LED turned on when transmitter is within 20 ft.
2. LED turned off when transmitter is beyond 20 ft.
1. Ensure no other BluTooth devices are enabled or in range during
testing.
5.1
3.1.5.1, 3.1.5.2, 3.1.5.3, 3.1.5.4, 3.1.5.5, 3.1.5.6, 3.1.5.7, 3.1.5.8,
3.1.5.9
Verify alarm’s behavior and performance.
1. Signal from LabVIEW.
1. Send signal to alarm.
2. Verify alarm goes off.
1. Alarm will sound when signal is received.
1. Ensure speaker volume is enabled.
6.1
3.1.6.1, 3.1.6.2, 3.1.6.3, 3.1.6.4, 3.1.6.5, 3.1.6.6
Verify behavior of the DFM system while reset is activated.
N/A
1. Set temperature high and occupancy level to 5.
2. Press reset button.
3. Verify state of DFM system.
4. Set temperature back to normal state and occupancy level to
5.
5. Press reset button.
6. Verify state of DFM system.
1. If reset is pressed while occupancy has been detected and
temperature is high, the system is not reset.
2. If reset is pressed and temperature is not high but an
occupant is detected and transmitter is out of range, the
system and alarm are reset.
3. If the reset is pressed with no current alarm sounding, the
system is reset.
N/A
7.1
3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.1.4, 3.2.1.5
Verify each sensor will send a signal to LabVIEW.
1. What each sensor is sensing.
2. Simulated signal if sensor is simulated
1. Turn on the switch for one of the sensors.
17
Brandon Fields - Lab 3
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
2. Verify result.
3. Turn off the sensor.
4. Repeat steps 1-3 for each of the remaining sensors.
1. For each sensor, a signal is received.
N/A
7.2
3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.1.4, 3.2.1.5
Verify each sensor’s value will be greater than or equal to its rated
minimum value.
1. What each sensor is sensing.
2. Simulated signal if sensor is simulated.
1. Turn on the switch for one of the sensors.
2. Verify result.
3. Turn off the sensor.
4. Repeat steps 1-3 for each of the remaining sensors.
1. For each sensor, the signal that is received is greater than or equal
to its rated minimum value.
N/A
7.3
3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.1.4, 3.2.1.5
Verify each sensor’s value will be less than or equal to its rated
maximum value.
1. What each sensor is sensing.
2. Simulated signal if sensor is simulated.
1. Turn on the switch for one of the sensors.
2. Verify result.
3. Turn off the sensor.
4. Repeat steps 1-3 for each of the remaining sensors.
1. For each sensor, the signal which is received is less than or equal
to its rated maximum value.
N/A
7.4
3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.1.4, 3.2.1.5
Verify each sensor will return a value within 10 seconds.
1. What each sensor is sensing.
2. Simulated signal if sensor is simulated.
1. Turn on the switch for one of the sensors.
2. Verify result.
18
Brandon Fields - Lab 3
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
Test Case
Requirements
Traceability
Description of Test
Test Inputs
Test Procedures
Expected Results
Special Instructions
3. Turn off the sensor.
4. Repeat steps 1-3 for each of the remaining sensors.
1. For each sensor, the signal was received in less than 10 seconds.
N/A
7.5
3.2.1.1, 3.2.1.2, 3.2.1.3, 3.2.1.4, 3.2.1.5
Verify the entire activation will take no more than 60 seconds.
1. What each sensor is sensing.
2. Simulated signal if sensor is simulated.
1. Start the system.
2. Verify results.
1. System was activated in less than or equal to 60 seconds.
N/A
8.1
3.1.2.1, 3.1.2.2, 3.1.2.3, 3.1.2.4
Verify error detection.
N/A
1. Disable various sensors in order to change total value for
priority codes.
1. 1. When total priority values for disabled sensors is greater
that 7 then error message will be generated.
N/A
9.1
3.1.2.1, 3.1.2.2, 3.1.2.3, 3.1.2.4, 3.1.3.1, 3.1.3.2, 3.1.4.1, 3.1.4.2,
3.1.4.3, 3.1.5.1, 3.1.5.2, 3.1.5.3, 3.1.5.4, 3.1.5.5, 3.1.5.6, 3.1.5.7,
3.1.5.8, 3.1.5.9, 3.1.8.1, 3.1.8.2, 3.1.8.3
Verify behavior and performance for all components of the DFM
system when components are integrated.
1. All sensor signals.
2. Transmitter signal.
1. Create movement alone.
2. Verify no alarm.
3. Create movement and a heartbeat signal to demonstrate
occupancy detection.
4. Verify alarm.
1. 1. No alarm with motion only and alarm sounded with
motion and heartbeat.
N/A
19
Brandon Fields - Lab 3
5 Traceability to Requirements
Component
Requirement ID
Sensor
overview
3.1.1.1.1
3.1.1.1.2
3.1.1.2.1
3.1.1.2.2
3.1.1.2.3
3.1.1.2.4
3.1.1.2.5
3.1.1.2.6
3.1.1.3.1
3.1.1.3.2
3.1.2.1
3.1.2.2
3.1.2.3
3.1.2.4
x
x
3.1.3.1
3.1.3.2
3.1.4.1
3.1.4.2
3.1.4.3
3.1.5.1
3.1.5.2
3.1.5.3
3.1.5.4
3.1.5.5
3.1.5.6
3.1.5.7
3.1.5.8
3.1.5.9
3.1.6.1
3.1.6.2
3.1.6.3
3.1.6.4
3.1.6.5
3.1.6.6
Life detection
sensors
Environmental
sensor
Life detection
procedures
Environmental
evaluation
procedures
Transmitter
and receiver
functions
Alarm system
Reset
procedures
labView setup
Simpulation
procedures
Component
3.1.7.1
3.1.7.2
3.1.7.3
3.1.7.4
3.1.7.5
3.1.7.6
3.1.7.7
3.1.8.1
3.1.8.2
3.1.8.3
Requirement ID
1.1 2.1 3.1 3.2 3.3 3.4 3.5 4.1 4.2 5.1 6.1 7.1 7.2 7.3 7.4 7.5 8.1 9.1
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
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
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
1.
1
x
x
x
2.
1
x
x
x
3.
1
x
x
x
3.
2
x
x
x
3.
3
20
x
x
x
3.
4
x
x
x
3.
5
4.
1
4.
2
5.
1
6.
1
7.
1
7.
2
7.
3
7.
4
7.
5
8.
1
x
x
x
9.
1
Brandon Fields - Lab 3
DFM system
activation
Sensor
performance
Procedure
performance
Sensor
Performance
Procedure
performance
Transmitter
and receiver
functions
3.2.1.1
x
x
x
x
3.2.1.2
3.2.1.3
3.2.1.4
3.2.1.5
3.2.2.1.1
3.2.2.1.2
3.2.2.1.3
3.2.2.1.4
3.2.2.2.1
3.2.2.2.2
3.2.2.2.3
3.2.2.2.4
3.2.2.2.5
3.2.3.1.1
3.2.3.1.2
3.2.3.1.3
3.2.3.1.4
3.2.3.2.1
3.2.3.2.2
3.2.3.2.3
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
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
3.2.4.1
x
x
3.2.4.2
3.2.4.3
x
x
x
x
Table 3, Traceability to requirements table
21
x
x
x
x
x