STD Oba PDF

Ilimitado Dominio Inc. Software Test Description 05-01-049-0.
Ilimitado Dominio Inc.
SOFTWARE TEST DESCRIPTION (STD)

FOR
ON BOARD AUTOMOBILE SYSTEM (OBA)
OF
DRIVING ASSISTANCE SYSTEM (DAS)
Contract No:
CASE (Man_Doc_001)
CDRL Sequence No:

CASE (Man_Doc_003)
Prepared For:
CENTRE FOR ADVANCED SOFTWARE ENGINEERING
STD Version 0.1 14-May-12

Ilimitado Dominio Inc. Software Test Description 05-01-049-0.1
DOCUMENT APPROVAL
REVISION NAME DATE
Verified By:
Mohd. Ariffin Nizar
_______________
PROJECT LEADER
Authenticated By: Mr. Mohd. Nazri bin

Kama
_______________
PROJECT MANAGER
Mr. Mohd Naz’ri bin

Approved By: Mahrin
_______________
CLIENT
Software : Microsoft Word 2000

Archiving Place : \IlimitadoDominio\SoftwareDocument\STD\ID-05-01-049-0.1
Copies Available : DOC
STD Version 0.1 Page i of viii 14-May-12

REVISION HISTORY
REVISION DESCRIPTION
First draft before TRR

A
.
B
Ind.+ Date A B C D E
08 March
2005
Written by Fitra Darina

Abu Bakar
Verified by Mohd Ariffin

bin Nizar
Authenticated En. Mohd

by Nazri bin
Kama
Approved by En. Naz’ri

Mahrin
STD Version 0.1 Page ii of viii 14-May-12

LIST OF EFFECTIVE PAGES
PAGES REVISION PAGES REVISION
STD Version 0.1 Page iii of viii 14-May-12

TABLE OF CONTENTS
1 SCOPE ......................................................................................................1
1.1 Identification ......................................................................................... 1
1.2 Overview of the System .......................................................................... 1
1.3 Overview of the Document ...................................................................... 2
2 APPLICABLE DOCUMENTS ............................................................................3
2.1 Government documents .......................................................................... 3
2.2 Non- Government documents .................................................................. 3
2.3 Contractual documents ........................................................................... 4
2.4 Non-Contractual documents .................................................................... 4
3.1 OBA01TC0A - Setup\Installation ............................................................. 5
3.2 OBA01TC0B - Launch Bench .................................................................... 7
4 FORMAL QUALIFICATION TEST DESCRIPTIONS ............................................. 11
4.1 Test Case Specification: OBA01TC0A Setup\Installation ........................... 11
4.1.1 Test case name : TC0A Setup\Installation ..................................... 11
4.1.1.1 Requirements traceability ............................................... 11
4.1.1.2 Initialization .................................................................. 11
4.1.1.3 Test input ..................................................................... 11
4.1.1.4 Expected test result ....................................................... 11
4.1.1.5 Criteria for evaluating results .......................................... 11
4.1.1.6 Test procedure .............................................................. 12
4.1.1.7 Assumptions and constraints ........................................... 12
4.2 Test Case Specification: OBA01TC0B Launch Bench ................................. 13
4.2.1 Test Case Name: TC0B Launch Bench ........................................... 13
4.2.1.1 Requirements traceability ............................................... 13
4.2.1.2 Initialization .................................................................. 13
4.2.1.3 Test input ..................................................................... 13
4.2.1.6 Test procedure .............................................................. 13
4.3 Test Case Specification: OBA01TC01 – Initialize OBA ................................ 16
4.3.1 Test case name: TC01 Initialize OBA ............................................ 16
4.3.1.1 Requirements traceability (STD_REQ_100) ....................... 16
STD Version 0.1 Page iv of viii 14-May-12

4.3.1.2 Initialization .................................................................. 16

4.3.1.3 Test input ..................................................................... 16
4.3.1.6 Test procedure .............................................................. 17
4.4 Test Case Specification: OBA01TC02 –Control Cruise Speed ...................... 18
4.4.1 Test case name: TC02 Control Cruise Speed .................................. 18
4.4.1.2 Initialization .................................................................. 18
4.4.1.3 Test input ..................................................................... 18
4.4.1.6 Test procedure .............................................................. 19
4.4.1.7 Assumptions and Constraints .......................................... 29
4.5 Test Case Specification: OBA01TC03– Calculate Average Speed ................. 30
4.5.1 Test case name: TC03Calculate Average Speed ............................. 30
4.5.1.2 Initialization .................................................................. 30
4.5.1.3 Test input ..................................................................... 30
4.5.1.6 Test procedure .............................................................. 30
4.5.1.7 Assumption and Constraints ............................................ 32
4.6 Test Case Specification: OBA01TC04 – Monitor Maintenance Schedule ........ 33
4.6.1 Test case name: TC04 Monitor Maintenance Schedule..................... 33
4.6.1.2 Initialization .................................................................. 33
4.6.1.3 Test input ..................................................................... 33
4.6.1.6 Test procedure .............................................................. 34
4.7 Test Case Specification: OBA01TC05 – Monitor Fuel Consumption .............. 36
4.7.1 Test case name: TC05 Monitor Fuel Consumption ........................... 36
STD Version 0.1 Page v of viii 14-May-12


4.7.1.2 Initialization .................................................................. 36
4.7.1.3 Test input ..................................................................... 36
4.7.1.6 Test procedure .............................................................. 37
4.8 Test Case Specification: OBA01TC06 – Calibrate Pulses ............................ 39
4.8.1 Test case name: TC06 Calibrate Pulses ......................................... 39
4.8.1.2 Initialization .................................................................. 39
4.8.1.3 Test input ..................................................................... 39
4.8.1.6 Test procedure .............................................................. 40
5 NOTES ..................................................................................................... 43
6 APPENDIX………………………………………………………………………………………………………………. 44
STD Version 0.1 Page vi of viii 14-May-12

LIST OF TABLES
Table 3.2: Qualification Methods ........................................................................ 9
Table 3.3: Qualification Levels ......................................................................... 10
Table 4.1: Description of Test Case TC0A .......................................................... 12
Table 4.2: Description of test case TC0B ........................................................... 14
Table 4.3: OBA Initialization Test Cases ............................................................ 17
Table 4.4: Control Cruise Speed Test Cases ....................................................... 19
Table 4.5: Test Condition and Criteria for Cruise Speed Acceleration via “Start
Acceleration” Button ....................................................................................... 21
Table 4.6 : Cruise Speed Acceleration via “Start Acceleration” Button Test Cases ... 21
Table 4.7: Cruise Speed Acceleration via “Start Acceleration” button Response Time
Test Cases .................................................................................................... 22
Table 4.8: Cruise Speed Acceleration via “Accelerator Pedal” and Activation Button 23
Table 4.10: Cruise Speed Acceleration via “Accelerator Pedal” and Activation Button
Response Time Test Case ................................................................................ 25
Table 4.11: Test Condition and Criteria for Auto-Cruise Suspension via “Brake Pedal”
With Deactivation ........................................................................................... 25
Table 4.12: Auto-Cruise Suspension via “Brake Pedal” With Deactivation Test Cases
.................................................................................................................... 25
Table 4.13: Test Condition and criteria for Auto-Cruise Suspension via “Brake Pedal”
With Resume ................................................................................................. 27
Table 4.14: Auto-Cruise Suspension via “Brake Pedal” With Resume Test Cases..... 27
Table 4.15: Auto-Cruise Suspension via “Brake Pedal” With Resume Response Time
Test Case ...................................................................................................... 29
Table 4.16: Test Condition and Criteria for Calculate Average Speed .................... 31
Table 4.18: Trip Stopping Times Test Cases ...................................................... 32
Table 4.19: Average Speed Calculation Response Time Test Cases ....................... 32
Table 4.20: Monitor Maintenance Schedule Test Cases ........................................ 34
Table 4.21: Respective Message Response Time Test Cases ................................ 35
Table 4.22: Fuel Consumption Monitoring during Trip Test Cases ......................... 37
Table 4.23 : Fuel Consumption between Two Filings Test Cases ........................... 38
STD Version 0.1 Page vii of viii 14-May-12

Table 4.24: Average Fuel Consumption Calculation Response Time Test Cases....... 38
Table 4.25: Test Condition and Criteria for Calibrate Pulses ................................. 40
Table 4.26 : Calibrate Pulses Test Cases ........................................................... 40
STD Version 0.1 Page viii of viii 14-May-12

1 SCOPE
The scope of this software test description document is to document

and specify the test description for the OBA CSCI and agreed with
CASE client.
Further, this document will be used as a reference document for the
testing of the OBA CSCI.
1.1 Identification
System Number : 100

System Name : Driving Assistance System
System Abbreviation : DAS
CSCI Identification Number : OBA100

CSCI Title : On Board Automobile
CSCI Abbreviation : OBA
1.2 Overview of the System
Purpose of the DAS System:

The DAS purposes are captured from requirement documents from
client. DAS is designed as driving assistant system of a new car. The
following are main functionality of the DAS:
i. To provide auto cruise functionality.
ii. To provide tracking functionality.
iii. To provide mapping and optimum route designation
functionality.
STD Version 0.1 Page 1 of 43 14-May-12

Purpose of the CSCI OBA:

The statements of OBA purposes are captured from requirement
documents from client. This CSCI is designed as an auto cruise
mechanism during driving for the proposed new car. Main purpose:
i. Auto cruising speed
ii. Maintenance scheduling
iii. Average speed calculation
iv. Fuel consumption
v. Calibrate pulses
1.3 Overview of the Document
This document describes the system test cases and procedures for the
OBA CSCI .
The test cases are design according to the Software Requirement

Specification (SRS) in order to meet the client requirements.
We elaborate the test cases into 6 test plan which are :

i. Initialize OBA (TC01)
ii. Control Cruise Speed (TC02)
iii. Calculate Average Consumption (TC03)
iv. Monitor Maintenance Schedule (TC04)
v. Monitor Fuel Consumption (TC05)
vi. Calibrate Pulses (TC06)
The following paragraph summarizes the contents of this document:
Chapter 1: Describes the identification, system overview and

document overview.
Chapter 2: Describes the applicable documents related to the
project.
Chapter 3: Describes the test preparation requirements.
Chapter 4: Describes the detailed descriptions of the test cases.
Chapter 5: Describes the glossary.

2 APPLICABLE DOCUMENTS
The following documents, for which the exact is indicated, form part of
the specification as far as everything specified hereafter is concerned.
In the event of discrepancy between the documents referred to here
and the content of this specification, it is the content of the
specification, which should be considered to be the background
reference.
Copies of specifications, standards, drawings and publications

requested by suppliers in contact with the specified supplying functions
may be obtained from the contracting agency or directly through the
contracting office.
2.1 Government documents

[1] DoD-Std-2167A Defence System Software
Development
[2] DoD-Std-2168 Defence System Software Quality
Program
[3] MIL-Std-1521B Technical Reviews and Audits
2.2 Non- Government documents

The following documents, which are guidelines standard used in the
project.
[4] CASE (Man_BDoc_001) General organization of the project
[5] CASE (Man_BDoc_002) Presentation of the project
[6] CASE (Man_Doc_002) Statement of Work for an OBA
System
[7] CASE (Tech_Doc_001) Technical Specification for DAS
[8] CASE (Tech_Doc_002) Maintenance Report No1
[9] CASE (Tech_Doc_003) Maintenance Report No2
[10] CASE (Letter_1) Letter 1 from client-Safety
Department
[11] CASE (Letter_2) Letter 2 from client-Safety Human
[12] CASE (Letter_3) Letter from Client – System
Requirements Specification

[13] Guideline UML-1 The Unified Modelling Language

User Guide (Addison Wesley
[14] Guideline UML-2 The Unified Software Development
Process (Addison Wesley)
[15] Guideline C++-1 C++: How To Program (Prentice
Hall)
[16] IRS Interface Requirement
Specification
[17] SRS Software Requirement Specification
[18] SDP Software Development Plan
[19] SDD Software Design Document
[20] SUM Software User’s Manual
[21] SPM Software Programmer’s Manual
[22] Source Code-1 OBATargetMachine.h
[23] Source Code-2 PortsLayout.h
[24] Source Code-3 Appli_OBAMini.cpp
2.3 Contractual documents

[25] CASE (Man_Doc_001) Contract for an OBA System
[26] CASE (Man_Doc_003) Contract Data Requirements List
for the OBA
2.4 Non-Contractual documents

[27] DC150-1 Software Development Reference
System

3 FORMAL QUALIFICATION TEST PREPARATION
3.1 OBA01TC0A - Setup\Installation
This test is to verify the completeness and presided of the setup

installation procedure, as presented in the OBA software Test Bench
and Simulator Manual.
3.1.1 Schedule
The schedule is stated below:

i. Location : CASE Lab
ii. Date : 20/03/2005
iii. Time : 10.00 am
The testing will be conducted by : QM Manager
3.1.2 Pre-test Procedures

3.1.2.1 Hardware Preparation
Testing of the OBA will be performed on the development platforms.
No special hardware preparation is required. The designated machines
must be operational and running.
i. Hardware
The hardware to be used for testing is an LINUX equipped
operating platform consisting of C++ programming language.
ii. The system must include an Ethernet cable and power supply
cables.

Table 3.1: Summary of Hardware needed for testing
Unit Item Description

1 Personal Computer Pentium IV
256 RAM
40GB Hard Disk
Monitor
10/100 Mbps Ethernet Card
CDROM, Floppy disk, keyboard, mouse
- Networking LAN networking environment
1 Printer HP LaserJet
3.1.2.2 Software Preparation
This installation process will be tested and the system shall be left in
an operational condition prior to running the nominal system
capability, project requirements and level of services test cases. As
part of the testing, the OBA will be populated with some dummy data.
The following will be treated us the standards to this test document:
i. The software version under test should be the same as the
software release that may be sent to production.
ii. The storage medium for the items shall be on the LINUX
platform.
iii. The following software modules must be loaded:
i. Simulator
ii. Test Bench
iii. OBA application component
iv. The minimum requirements to install the OBA application are

listed below:
i. Operating System: LINUX
ii. Programming Language: C++ Language

3.1.2.3 Other Pre-test Preparation
The assumptions considered during testing are:
i. Sufficient simulations are available to provide required test

fidelity.
ii. On-Board Automation is fully certified and under configuration
control
3.2 OBA01TC0B - Launch Bench
This test is to verify that once the completed installation procedures is

successful, OBA system can interact with the simulated environment.
3.2.1 Schedule
ii. Date : 17/03/2005
iii. Time : 09.00pm
3.2.2 Pre-test Procedures

The hardware that is mentioned in section 3.1.2.1 must be available
and functioning.
The software that is mentioned in section 3.1.2.2 must be able to

integrate with the simulation environment..
3.2.2.3 Other Pre-test Preparations

None.

3.3 OBA01TC01-OBA01TC6 - Capability Testing
The following test plans identified as follows have a set of shared

hardware, software and other pre-test preparations:
i. Initialize OBA (TC01)
ii. Control Cruise Speed (TC02)
iii. Calculate Average Consumption (TC03)
iv. Monitor Maintenance Schedule (TC04)
v. Monitor Fuel Consumption (TC05)
vi. Calibrate Pulses (TC06)
The detailed test plans are illustrated in chapter 4 of this document.
3.3.1 Schedule

ii. Date : 20/03/2005
iii. Time : 09.15 am
3.3.2 Pre-test procedures
The hardware that is mentioned in section 3.1.2.1 must be available

and functioning.
The software that is mentioned in section 3.1.2.2 must be able to

integrate with the simulation environment.

3.3.2.3 Other Pre-test Preparations
The dummy data as per requirement of the detailed test must be

available.
For OBA01TC01-OBA01TC06, the road profile is needed. For this OBA

system, we classified the road into 5 different item which are :
i. Flat Road
ii. Uphill Road
iii. Downhill Road
iv. Funny Road
v. Bumpy Road
3.3.2.3.1 Qualification Methods
The following qualification methods will be used in the detail test plan
of Chapter 4 to support the clarity of the test cases.
Qualification methods used are as following:
Table 3.2: Qualification Methods
No. Level Abbreviation Description
1. Demonstration D The operation of the CSCI OBA or some

part of the CSCI that relies on observable
functional operation.
2. Analysis A The processing of accumulated data

obtained from other qualification
methods.
A Real time requirement.
3. Inspection I The visual examination of CSCI OBA

source code and documentation.

3.3.2.3.2 Qualification Levels
The following qualification levels will be used in the detail test plan of
Chapter 4 to support the clarity of the test cases.
Qualification levels used are as following:
Table 3.3: Qualification Levels
No. Level Abbreviation Description
1. Configuration 1 The item is configured and traced to

Item completion.
2. System 2 Components required for integration.

Integration
3. System 3 System components.
4. System 4 Components required for installation.

Installation

4 FORMAL QUALIFICATION TEST DESCRIPTIONS
4.1 Test Case Specification: OBA01TC0A Setup\Installation
The following test case is designed for the OBA application

setup\installation.
4.1.1 Test case name : TC0A Setup\Installation
4.1.1.1 Requirements traceability
None
4.1.1.2 Initialization
Workstation must be properly working.
4.1.1.3 Test input
The hardware is an LINUX equipped operating platform consisting of C

programming language.
4.1.1.4 Expected test result
The test result is shown as in Table 4.1.
4.1.1.5 Criteria for evaluating results
For the criteria in evaluating the test conditions, the Table 4.1 is
validated as follows.
For every row indicated for the expected result must match the actual
result to consider this test as pass otherwise the test is considered fail.

4.1.1.6 Test procedure
4.1.1.6.1 Basic Flow - Installation procedure
4.1.1.6.1.1 Test Case to verify the installation process:
Table 4.1: Description of Test Case TC0A
Test id Test Description Expected Method(s) Level

TC0A-01 Create a folder named OBA OBA folder is created D 1
under user account name.
TC0A–02 Copy the following All components are D 1
components from copied.
mpt0508/home/OBA to OBA
folder:
• Cruise.exe
• OBA.exe
4.1.1.7 Assumptions and constraints
None

4.2 Test Case Specification: OBA01TC0B Launch Bench
The following test case is designed to launch the OBA test bench.
4.2.1 Test Case Name: TC0B Launch Bench
4.2.1.1 Requirements traceability
None
4.2.1.3 Test input
Main components of OBA application are loaded on the workstation,
which are :
i. OBA.exe
ii. Cruise.exe
Expected result is shown in Table 4.2.
For the criteria in evaluating the test conditions, Table 4.2 is validated
as follows. For every row indicated for the expected result must match
the actual result to consider this test as pass otherwise the test is
considered fail.
4.2.1.6.1 Launch Bench
To test the ‘Launch Bench’ functions.

4.2.1.6.1.1 Test Case to verify the launch bench
Table 4.2: Description of test case TC0B

TC0B-01 1. Enter . envi.sh Test Bench Screen is D 1
command. displayed.
2. Enter ./runOTB. Refer to Figure 4.1.
TC0B-02 From the “Choose a car The Automobile D 1
cruise simulation.exe file” Driving Controls,
section press “Browse” and Automobile Dashboard
select Cruise.exe file. and OBA Panel will be
loaded and ready to
Press “Get the Car”. run.
From the “Choose the

OBA.exe file” section press
“Browse” and select OBA.exe
file.
Press “Run the OBA”.


fidelity.
control
The constraints considered during testing are:

i. Test conducted that neither modifies nor corrupts the
software

4.3 Test Case Specification: OBA01TC01 – Initialize OBA
The following test case is designed for the Initialize OBA component.
4.3.1 Test case name: TC01 Initialize OBA
4.3.1.1 Requirements traceability (STD_REQ_100)
The requirement traceability is as identified in the Software

Requirement Specification. Please refer Appendix for the Traceability
Matrix Table.
4.3.1.3 Test input
Main components of OBA application are loaded on the workstation,
which are :
i. OBA.exe
ii. Cruise.exe
Expected result is shown in Table 4.3
For the criteria in evaluating the test conditions, Table 4.3 is validated
as follows. For every row indicated for the expected result must match
the actual result to consider this test as pass otherwise the test is
considered fail.

4.3.1.6.1 Initialize OBA

To initialize the OBA.
4.3.1.6.1.1 Test Case to verify the OBA Initialization
Table 4.3: OBA Initialization Test Cases

TC01-01 From the Automobile Driving A continuous “Engine D 1
Controls Panel, press “Go Running” message will
Cruising” button. And, next be displayed on the
press the “Ignition” button. Automobile Dashboard
Panel.

fidelity.
control
The constraints considered during testing are:

i. Test conducted that neither modifies nor corrupts the
software

4.4 Test Case Specification: OBA01TC02 –Control Cruise Speed
This test case is to test the Control Cruise Speed component.
4.4.1 Test case name: TC02 Control Cruise Speed

Requirement Specification. Please refer Appendix for the Traceability
Matrix Table
i. The OBA is initialized via TC01.
ii. Simulator is on the highest transmission gear , gear 5
iii. Minimum speed is 75km/h
iv. Brake Pedal is released
v. Clutch Pedal is released
4.4.1.3 Test input
The “Activation” is pressed.
validated as follows. For every row indicated for the expected result
must match the actual result to consider this test as pass otherwise
the test is considered fail.

4.4.1.6.1 Control Cruise Speed
This functionality shall be able to maintain the cruise speed in its valid
range at various tested conditions.
4.4.1.6.2 Basic Flow of Events
4.4.1.6.2.1 Test Case to verify the control cruise Speed
Table 4.4: Control Cruise Speed Test Cases

TC02-01 From the OBA Panel, press System displays the
the “Activation” button. current speed as the
(SRS_REQ_207) cruise speed.
(SRS_REQ_208 & 210)
The activation LED

highlights ON.
(SRS_REQ_209)
TC02-02 The system maintains System keeps the
constant cruise speed by speed at + or – 1
regulating voltage to the km/h in relation to the
throttle. (SRS_REQ_236) & selected speed.
(SRS_REQ_239) (Normal Grade)
(SRS_REQ_236) &
(SRS_REQ_239)
TC02-03 During normal cruising, speed Speed will be A, D, I 1
is 1 km/h above normal decreased to cruise
cruise speed. speed. (Downgrade)
(SRS_REQ_240) (SRS_REQ_240)
TC02-04 During normal cruising, speed Speed will be A, D, I 1
is 1 Km/h below normal increased to cruise
cruise speed. speed. (Upgrade)
TC02-05 The acceleration reaches Speed will be A, D, I 1
1.2km/h/sec value while decreasing due to
cruising. (SRS_REQ_237) closed throttle.
(SRS_REQ_237)
Decrease +/- 1 to
cruise speed??
TC02-06 The acceleration reaches Speed will be A, D, I 1
0.8km/h/sec value while increasing due to
cruising. (SRS_REQ_238) opened throttle.
Increase +/- 1 to
cruise speed??
(SRS_REQ_238)
Table 4.4: Control Cruise Speed Test Cases (cont.)


TC02-07 Cruise speed reaches ≥ The “Care to Speed” A, D, I 1
110km/h while cruising. LED is highlighted.
And, system shall

display “Over
Speeding” message at
display panel.
(SRS_REQ_235)
TC02-08 Cruise speed reaches ≥ The “Hazard Bolting” A, D, I 1
130km/h while cruising. LED is highlighted.
And, system shall

display “Over
Speeding” message at
display panel.
(SRS_REQ_235)

4.4.1.6.2.2 Test Case to verify the accelerating cruise speed functionality

via “Start Acceleration” button (TC02-A)
Table 4.5: Test Condition and Criteria for Cruise Speed Acceleration via
“Start Acceleration” Button
Test Criteria Test Condition Test Condition

1 Start Acceleration: 1 = ON 0 = OFF
Speed: 1 = >= 80 Km/h < 130 0 = > 130 Km/h
2 Km/h
3 Stop Acceleration: 1 = ON 0 = OFF
Table 4.6 : Cruise Speed Acceleration via “Start Acceleration” Button Test
Cases
Criteria
Test Id Expected Result Method(s) Level
1 2 3
TC02-A- 0 0 0
Hazard bolting LED
01 A, D, I 1
is highlighted.
TC02-A- 0 0 1
Hazard bolting LED
02 A, D, I 1
is highlighted.
TC02-A- 0 1 0 If speed reaches
=> 110km/h, “Care
03
to Speed” LED is
A, D, I 1
highlighted.
TC02-A- 0 1 1 If speed reaches
=> 110km/h, “Care
04
to Speed” LED is
A, D, I 1
highlighted.
TC02-A- 1 0 0 Hazard bolting LED
05 is highlighted. A, D, I 1
TC02-A- 1 1 0 “Acceleration”
06 message is
displayed on the
display panel.
(SRS_REQ_213) A, D, I 1

Table 4.6 : Cruise Speed Acceleration via “Start Acceleration” Button Test
Cases(cont.)
Criteria
Test Id Expected Result Method(s) Level
1 2 3
TC02-A- Speed is
increasing.
07 A, D, I 1
1 1 0 (SRS_REQ_214)
TC02-A- The new cruise
speed is set to
08
current speed.
A, D, I 1
1 1 1 (SRS_REQ_215)
4.4.1.6.2.2.1 Test Case to verify the accelerating cruise speed

functionality via “Start Acceleration” button Response Time
Table 4.7: Cruise Speed Acceleration via “Start Acceleration” button

Response Time Test Cases

TC02-B- Response time for this Within 0.5 second A, D, I 1
01 function to be activated.

4.4.1.6.2.3 Test Case to verify the accelerating cruise speed functionality

via “Accelerator Pedal”
Table 4.8: Cruise Speed Acceleration via “Accelerator Pedal” and Activation
Button

1 Auto cruise 1 = Active mode 0 = Suspend mode
2 Activation 1 = ON 0 = OFF
Table 4.9 : Cruise Speed Acceleration via “Accelerator Pedal” and Activation
Button Test Cases
Criteria
1 2
TC02-C- 1 0 1. Press accelerator Speed A, D, I 1
pedal. increasing.
01
2. Release accelerator Cruise speed is

pedal. set to previous
(SRS_REQ_218) speed.
(SRS_REQ_218)
TC02-C- 1 1 1. Press accelerator Speed A, D, I 1
02 pedal. increasing.
Cruise speed is
set to current
speed.
(SRS_REQ_218)
TC02-C- 0 0 1. Press accelerator Not in cruise
03 pedal. mode and
(SRS_REQ_216) manual driving
speed is
increasing.

Table 4.9 : Cruise Speed Acceleration via “Accelerator Pedal” and Activation
Button Test Cases(cont.)
Criteria
1 2
TC02-C- 0 1 1. Press accelerator If current speed
04 pedal. => 75km/h,
(SRS_REQ_216) auto cruise
mode is Active,
and cruise
speed = current
speed.

4.4.1.6.2.3.1 Test Case to verify the accelerating cruise speed

functionality via “Accelerator Pedal” Response time.
Table 4.10: Cruise Speed Acceleration via “Accelerator Pedal” and Activation
Button Response Time Test Case
Test id Test Description Expected Method (s) Level

TC02-D- Response time for this function to be Within 0.5 A, D, I 1
01 activated. second
4.4.1.6.2.4 Test Case to verify the auto cruise suspension via “Brake
Pedal”
4.4.1.6.2.4.1 With Deactivation
Table 4.11: Test Condition and Criteria for Auto-Cruise Suspension via
“Brake Pedal” With Deactivation

1 Brake: 1 = pressed 0 = released
2 Speed: 1 = > 80 Km/h < 130 Km/h 0 = < 80 Km/h
3 Deactivation: 1 = ON 0 = OFF
Table 4.12: Auto-Cruise Suspension via “Brake Pedal” With Deactivation

Test Cases
Test Criteria
Expected Result Method(s) Level
Id 1 2 3
TC02-E-
D 1
01 0 0 0 Not applicable
TC02-E-
D 1
TC02-E-
D 1

Table 4.12: Description of test case TC02-E(cont)
Test
Id Criteria
TC02-E-
D 1
TC02-E- 1 0 0 The activation LED D 1

highlights ON.
05
System displays
“SUSPEND”
message.
Cruise speed
decreasing.
TC02-E- The activation LED

D 1
06 1 0 1 highlights OFF.
TC02-E- 1 1 0 The activation LED D 1
07 highlights ON.
System displays
“SUSPEND”
message.
Cruise speed
decreasing.
TC02-E- The activation LED

D 1
08 1 1 1 highlights OFF.

4.4.1.6.2.4.2 With Resume
Table 4.13: Test Condition and criteria for Auto-Cruise Suspension via
“Brake Pedal” With Resume

1 Brake : 1 = pressed 0 = released
2 Speed: 1 = > 80 Km/h < 170 Km/h 0 = < 80 Km/h
3 Resume: 1 = ON 0 = OFF
Table 4.14: Auto-Cruise Suspension via “Brake Pedal” With Resume Test
Cases
Test Criteria
Id 1 2 3
TC02-F-
0 0 0 D 1
01 Not applicable
TC02-F-
0 0 1 D 1
02 Not applicable
TC02-F-
0 1 0 D 1
03 Not applicable
TC02-F- Cruise speed is set

04 to previous cruise
0 1 1 D 1
speed.
(SRS_REQ_225)
TC02-F- Speed decreasing D 1
05 continuously.
1 0 0 System displays
“SUSPEND”
message.

Table 4.14: Auto-Cruise Suspension via “Brake Pedal” With Resume Test
Cases (cont.)
Test
Id Criteria
TC02-F- Resume failed.

07 Speed decreasing.
1 1 0 System displays D 1
“SUSPEND”
message.
TC02-F- Resume failed.

08 Speed decreasing.
1 1 1 System displays D 1
“SUSPEND”
message.

4.4.1.6.2.4.3 Test Case to verify the brake function’s response time.
Table 4.15: Auto-Cruise Suspension via “Brake Pedal” With Resume

Response Time Test Case

TC02-G- Response time for this function to be Within 0.5 A, D, I 1
01 activated. second
4.4.1.7 Assumptions and Constraints
None

4.5 Test Case Specification: OBA01TC03– Calculate Average Speed
The following test case is for the Calculate Average Speed component
testing.
4.5.1 Test case name: TC05Calculate Average Speed

Requirement Specification. Further traceability related to this
component may be found in the Test Procedure section.
The complete traceability is available in Appendix A: Traceability

Matrix.
The engine should be started and running. The ‘Begin trip’ button is
pressed at least once.
4.5.1.3 Test input
Prior to the testing of this component, the average speed button is

available.
For the criteria in evaluating the test conditions, the Table 4.16 and
table 4.17. For every row indicated for the expected result must
match the actual result to consider this test as pass otherwise the test
is considered fail.

4.5.1.6.1 Calculate Average Speed
To test average speed functions.
4.5.1.6.3 Test Case to verify the Calculate Average Speed functionality
Table 4.16: Test Condition and Criteria for Calculate Average Speed

1 ‘Average speed’ button 1 = Pressed 0 = Released
2 ‘Begin trip’ button 1 = Pressed 0 = Released
Table 4.17 : Description for of test case TC03
Criteria
Test id 1 2 Test Description Expected Method(s) Level
TC03-01 0 0 No change A, D, I 1
TC03-02 0 1 Distance is updated A, D, I 1
with latest trip
information.
TC03-03 1 0 The average speed A, D, I 1
value will be
displayed on the
screen.
TC03-04 1 1 STEP 1: Initially the average A, D, I 1
‘Average speed’ speed value will be
button is pressed. displayed on the
screen.
Step 2: Distance is updated
‘Begin trip’ button is with latest trip
pressed. information.

4.5.1.6.4 Test Case to verify stopping time
Table 4.18: Trip Stopping Times Test Cases

TC03-A- Vehicle is stopped for a while Average speed A, D, I 1
01 during a trip. computation should
not include vehicle-
stopping time.
4.5.1.6.5 Test Case to verify calculates average speed function’s

response time
Table 4.19: Average Speed Calculation Response Time Test Cases

TC03-B- Response time for this Within 1.0 second A, D, I 1
01 computation to be completed.
4.5.1.7 Assumption and Constraints
Average speed calculation should be tested on different road profile.

4.6 Test Case Specification: OBA01TC04 – Monitor Maintenance

Schedule
The following test case is for the Monitor Maintenance Schedule

component testing.
4.6.1 Test case name: TC04 Monitor Maintenance Schedule


Matrix.
For this test component the application must be installed and

connected with simulated external environments of the OBA system
(Refer TC0A and TC0B). The engine is running to engaging in testing
for the TC04 Monitor Maintenance Schedule component.
4.6.1.3 Test input
The maintenance milestone is reached.
For the criteria in evaluating the test conditions, the table in the Test
Procedure section is validated as follows. For every row indicated for
the expected result must match the actual result to consider this test
as pass otherwise the test is considered fail.

4.6.1.6.1 Monitor Maintenance Schedule
To display maintenance message once the milestone is reached.
This flow begins when the maintenance milestone is reached.

(SRS_REQ_401)
4.6.1.6.2.1 Test Case to verify the monitor maintenance schedule
Table 4.20: Monitor Maintenance Schedule Test Cases

TC04-01 400 Km before reaching “Oil and Filter Change” A, D, I 1
8,000 Km. (SRS_REQ_405) message is displayed
intermittently in 5
seconds every 10
minutes.
(SRS_REQ_405)
TC04-02 80 Km before reaching “Oil and Filter Change” A, D, I 1
8,000 Km. (SRS_REQ_405) message is displayed
continuously.
(SRS_REQ_405)
TC04-03 400 Km before reaching “Air Filter Change” A, D, I 1
15,000 Km. message is displayed
(SRS_REQ_406) intermittently in 5
seconds every 10
minutes.
(SRS_REQ_406)

Table 4.20: Monitor Maintenance Schedule Test Cases (cont.)

TC04-04 80 Km before reaching “Air Filter Change” A, D, I 1
(SRS_REQ_406) continuously.
(SRS_REQ_406)
TC04-05 400 Km before reaching “General Maintenance” A, D, I 1
(SRS_REQ_407) intermittently in 5
seconds every 10
minutes.
(SRS_REQ_407)
TC04-06 80 Km before reaching “General Maintenance” A, D, I 1
(SRS_REQ_407) continuously.
(SRS_REQ_407)
TC04-07 Press ‘Service completed’ Maintenance message A, D, I 1
button. (SRS_REQ_402) will be cleared.
(SRS_REQ_403)
4.6.1.6.2.2 Test Case to verify respective message response time.
Table 4.21: Respective Message Response Time Test Cases

TC06-A- Response time for respective messages Within 10
08 to be displayed. (SRS_REQ_404) second
None.

4.7 Test Case Specification: OBA01TC05 – Monitor Fuel

Consumption
The following test case is designed for the Calculate Average Fuel
Consumption component.
4.7.1 Test case name: TC05 Monitor Fuel Consumption


Matrix.

(Refer TC0A and TC0B). The engine should be started and running.
4.7.1.3 Test input
The tank is filled full at least once prior to the testing of this
component and the average fuel consumption button is available. The
“New” button under Trip label should be pressed.(SRS_REQ_501)
validated as follows. For every row indicated for the expected result
must match the actual result to consider this test as pass otherwise
the test is considered fail.

4.7.1.6.1 Monitor Fuel Consumption
To test average fuel consumption function.
4.7.1.6.3 Test Case to verify the monitor fuel consumption during a trip.
This flow begins when a driver wants to calculate average fuel

consumption during a trip.
Table 4.22: Fuel Consumption Monitoring during Trip Test Cases

TC05-01 A driver presses the ‘Average fuel The average fuel A, D, I 1
consumption’ button while consumption on
cruising.(SRS_REQ_502) the trip up to the
next filling value
will be displayed.
(SRS_REQ_503)
&
(SRS_REQ_504)

4.7.1.6.3.1 Test Case to verify the monitor fuel consumption function

between two fillings
This flow begins when a driver wants to calculate average fuel

consumption between two fillings.
Table 4.23 : Fuel Consumption between Two Filings Test Cases

TC05-A- Press the “Amount of Fuel” button The average fuel A, D, I 1
01 after filling. (SRS_REQ_505) consumption
between the last
Enters the amount of fuel in liters two fillings will
via keypad. (SRS_REQ_506) be displayed.
Maximum fuel tank is 35 liter. (SRS_REQ_508)
(SRS_REQ_509)
Press “Valid” key once filling

completed. (SRS_REQ_507)
4.7.1.6.3.2 Test Case to verify calculates average fuel consumption

function’s response time.
Table 4.24: Average Fuel Consumption Calculation Response Time Test

Cases

TC05-B- Response time for this computation Within 0.5 A, D, I 1
01 to be completed. second.
(SRS_REQ_510)
None

4.8 Test Case Specification: OBA01TC06 – Calibrate Pulses
The following test case is test on the calibrate speed and distance
functionality.
4.8.1 Test case name: TC06 Calibrate Pulses


Matrix.

(Refer TC0A and TC0B). The engine is started and running. Auto cruise
is in deactivation mode. (SRS_REQ_601)
4.8.1.3 Test input
Previous reference value for the speed measurement or the default

value exists and the ‘Start calibration’ and the ‘Stop calibration’ button
are available.
For the criteria in evaluating the test conditions, the Table 4.25 and
Table 4.26 is validated as follows. For every row indicated for the
expected result must match the actual result to consider this test as
pass otherwise the test is considered fail.

4.8.1.6.1 Calibrate Pulses
To test calculate calibrate pulses functions.
4.8.1.6.2.1 Test Case to verify the calibrate pulses function.
Table 4.25: Test Condition and Criteria for Calibrate Pulses

1 Cruise Control 1 = ON 0 = OFF
2 ‘Start calibration’ button 1 = Pressed 0 = Released
3 ‘Stop calibration’ button 1 = Pressed 0 = Released
Table 4.26 : Calibrate Pulses Test Cases
Test id Criteria Test Description Expected Method(s) Level

1 2 3
TC06-01 0 0 0 No change A, D, I 1
TC06-02 0 0 1 No change A, D, I 1
TC06-03 0 1 0 C2-Press the Message A, D, I 1
“Start Calibration” ‘Calibrating’
button is displayed.
(SRS_REQ_602)
C2 not followed by Nothing
C3. happened,
the number
of pulses is
not updated
default value
will be used.

Table 4.26 : Calibrate Pulses Test Cases(cont.)

1 2 3
TC06-04 0 1 1 C2, then drives for Message A, D, I 1
at least 1 Km ‘Calibration
(SRS_REQ_603), Complete’
followed by C3. displayed and
C2, then a driver the new
drives between 0.8 reference
Km and 1.2 Km, value of the
followed by C3. number of
pulses has
been stored.
C2, then a driver Message
drives < 0.8 Km ‘Calibration
followed by C3. Incomplete’
C2, then a driver displayed and
drives > 1.2 Km the number
followed by C3. of pulses is
not updated,
default value
will be used.
TC06-05 1 0 0 If cruise control is No change A, D, I 1
ON, calibration is
not allowed.
ON, calibration is
not allowed.
ON, calibration is
not allowed.

Table 4.26 : Calibrate Pulses Test Cases(cont.)

ON, calibration is
not allowed.
Calibration gives impact on average speed calculation and the testing

should be done in separate machine.

5 NOTES
Abbreviations used:-
CASE - Centre for Advance Software Engineering
CDRL - Contractual Document Requirement List
CSCI - Computer Software Configuration Item
CSC - Computer Software Configuration
CSU - Computer Software Unit
DAS - Driving Assistance System
DoD - Department of Defence
IRS - Interface Requirement Specification
MIL - Military
OBA - On Board Automobile
SDP - Software Development Plan
SRS - Software Requirement Specification
SSR - Software Specification Review
SDD - Software Design Document
Std - Standard
UC - Use Case
UML - Unified Modeling Language
UR - User Requirement
UTM - Universiti Teknologi Malaysia
TC - Test Case
TRR - Test Readiness Review

STD Oba PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

STD Oba PDF

Загружено:

Авторское право:

Доступные форматы

Ilimitado Dominio Inc. Software Test Description 05-01-049-0.

Ilimitado Dominio Inc.

SOFTWARE TEST DESCRIPTION (STD)

CDRL Sequence No:

CENTRE FOR ADVANCED SOFTWARE ENGINEERING

STD Version 0.1 14-May-12

REVISION NAME DATE

Authenticated By: Mr. Mohd. Nazri bin

Mr. Mohd Naz’ri bin

Software : Microsoft Word 2000

STD Version 0.1 Page i of viii 14-May-12

First draft before TRR

Written by Fitra Darina

Verified by Mohd Ariffin

Authenticated En. Mohd

Approved by En. Naz’ri

STD Version 0.1 Page ii of viii 14-May-12

LIST OF EFFECTIVE PAGES

PAGES REVISION PAGES REVISION

STD Version 0.1 Page iii of viii 14-May-12

STD Version 0.1 Page iv of viii 14-May-12

4.3.1.2 Initialization .................................................................. 16

STD Version 0.1 Page v of viii 14-May-12

4.7.1.1 Requirements traceability (STD_REQ_500) ....................... 36

STD Version 0.1 Page vi of viii 14-May-12

Table 3.2: Qualification Methods ........................................................................ 9

Table 3.3: Qualification Levels ......................................................................... 10

Table 4.1: Description of Test Case TC0A .......................................................... 12

Table 4.2: Description of test case TC0B ........................................................... 14

Table 4.3: OBA Initialization Test Cases ............................................................ 17

Table 4.4: Control Cruise Speed Test Cases ....................................................... 19

Table 4.18: Trip Stopping Times Test Cases ...................................................... 32

Table 4.20: Monitor Maintenance Schedule Test Cases ........................................ 34

Table 4.21: Respective Message Response Time Test Cases ................................ 35

STD Version 0.1 Page vii of viii 14-May-12

Table 4.26 : Calibrate Pulses Test Cases ........................................................... 40

STD Version 0.1 Page viii of viii 14-May-12

The scope of this software test description document is to document

System Number : 100

CSCI Identification Number : OBA100

1.2 Overview of the System

Purpose of the DAS System:

STD Version 0.1 Page 1 of 43 14-May-12

Purpose of the CSCI OBA:

1.3 Overview of the Document

The test cases are design according to the Software Requirement

We elaborate the test cases into 6 test plan which are :

ii. Control Cruise Speed (TC02)

iii. Calculate Average Consumption (TC03)

iv. Monitor Maintenance Schedule (TC04)

v. Monitor Fuel Consumption (TC05)

vi. Calibrate Pulses (TC06)

The following paragraph summarizes the contents of this document:

Chapter 1: Describes the identification, system overview and

STD Version 0.1 Page 2 of 43 14-May-12

Copies of specifications, standards, drawings and publications

2.1 Government documents

2.2 Non- Government documents

STD Version 0.1 Page 3 of 43 14-May-12

[13] Guideline UML-1 The Unified Modelling Language

2.3 Contractual documents

2.4 Non-Contractual documents

STD Version 0.1 Page 4 of 43 14-May-12