SOFTWARE TEST DESCRIPTION (STD) FOR ON BOARD AUTOMOBILE SYSTEM (OBA) OF DRIVING ASSISTANCE SYSTEM (DAS)

(1)

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:

(2)

DOCUMENT APPROVAL

REVISION NAME DATE

Verified By:

_______________

PROJECT LEADER

Mohd. Ariffin Nizar

Authenticated By:

_______________

PROJECT MANAGER

Mr. Mohd. Nazri bin

Kama

Approved By:

_______________

CLIENT

Mr. Mohd Naz’ri bin

Mahrin

Software : Microsoft Word 2000

Archiving Place : \IlimitadoDominio\SoftwareDocument\STD\ID-05-01-049-0.1 Copies Available : DOC

(3)

REVISION HISTORY

REVISION DESCRIPTION

A

First draft before TRR

B . C D E Ind.+ Date A 08 March 2005 B C D E

Written by Fitra Darina

Abu Bakar

Verified by Mohd Ariffin

bin Nizar Authenticated by En. Mohd Nazri bin Kama

Approved by En. Naz’ri

(4)

LIST OF EFFECTIVE PAGES

(5)

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.3 Test input ... 13

4.3 Test Case Specification: OBA01TC01 – Initialize OBA ... 16

4.3.1 Test case name: TC01 Initialize OBA ... 16

(6)

4.3.1.3 Test input ... 16

4.4 Test Case Specification: OBA01TC02 –Control Cruise Speed ... 18

4.4.1 Test case name: TC02 Control Cruise Speed ... 18

4.4.1.1 Requirements traceability (STD_REQ_200) ... 18

4.4.1.3 Test input ... 18

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.3 Test input ... 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.3 Test input ... 33

4.7 Test Case Specification: OBA01TC05 – Monitor Fuel Consumption ... 36

(7)

4.7.1.3 Test input ... 36

4.8 Test Case Specification: OBA01TC06 – Calibrate Pulses ... 39

4.8.1 Test case name: TC06 Calibrate Pulses ... 39

4.8.1.3 Test input ... 39

5 NOTES ... 43

(8)

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

(9)

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

(10)

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.

(11)

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.

(12)

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

(13)

[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

(14)

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

(15)

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

(16)

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

The schedule is stated below: i. Location : CASE Lab 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

(17)

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

The schedule is stated below: i. Location : CASE Lab 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.

(18)

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.

(19)

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 Item

1 The item is configured and traced to completion.

2. System Integration

2 Components required for integration.

3. System 3 System components.

4. System Installation

(20)

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.

(21)

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 under user account name.

OBA folder is created D 1

TC0A–02 Copy the following components from

mpt0508/home/OBA to OBA folder:

• Cruise.exe • OBA.exe

All components are copied.

D 1

4.1.1.7 Assumptions and constraints

(22)

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

(23)

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 command. 2. Enter ./runOTB.

Test Bench Screen is displayed.

Refer to Figure 4.1.

D 1

TC0B-02 From the “Choose a car cruise simulation.exe file” section press “Browse” and select Cruise.exe file.

Press “Get the Car”.

From the “Choose the OBA.exe file” section press “Browse” and select OBA.exe file.

Press “Run the OBA”.

The Automobile Driving Controls, Automobile Dashboard and OBA Panel will be loaded and ready to run.

(24)

The constraints considered during testing are:

i. Test conducted that neither modifies nor corrupts the software

(25)

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.

(26)

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 Controls Panel, press “Go Cruising” button. And, next press the “Ignition” button.

A continuous “Engine Running” message will be displayed on the Automobile Dashboard Panel.

D 1

The constraints considered during testing are:

i. Test conducted that neither modifies nor corrupts the software

(27)

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

The requirement traceability is as identified in the Software

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.

For the criteria in evaluating the test conditions, the Table 4.4 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.

(28)

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 the “Activation” button. (SRS_REQ_207)

System displays the current speed as the cruise speed.

(SRS_REQ_208 & 210) The activation LED highlights ON. (SRS_REQ_209) TC02-02 The system maintains

constant cruise speed by regulating voltage to the throttle. (SRS_REQ_236) & (SRS_REQ_239)

System keeps the speed at + or – 1 km/h in relation to the selected speed. (Normal Grade) (SRS_REQ_236) & (SRS_REQ_239) TC02-03 During normal cruising, speed

is 1 km/h above normal cruise speed. (SRS_REQ_240) Speed will be decreased to cruise speed. (Downgrade) (SRS_REQ_240) A, D, I 1

TC02-04 During normal cruising, speed is 1 Km/h below normal cruise speed. (SRS_REQ_241) Speed will be increased to cruise speed. (Upgrade) (SRS_REQ_241) A, D, I 1

TC02-05 The acceleration reaches 1.2km/h/sec value while cruising. (SRS_REQ_237) Speed will be decreasing due to closed throttle. (SRS_REQ_237) Decrease +/- 1 to cruise speed?? A, D, I 1

TC02-06 The acceleration reaches 0.8km/h/sec value while cruising. (SRS_REQ_238) Speed will be increasing due to opened throttle. Increase +/- 1 to cruise speed?? (SRS_REQ_238) A, D, I 1

(29)

TC02-07 Cruise speed reaches ≥ 110km/h while cruising. (SRS_REQ_234)

The “Care to Speed” LED is highlighted. (SRS_REQ_234) And, system shall display “Over

Speeding” message at display panel.

(SRS_REQ_235)

A, D, I 1

TC02-08 Cruise speed reaches ≥ 130km/h while cruising. (SRS_REQ_234)

The “Hazard Bolting” LED is highlighted. (SRS_REQ_234) And, system shall display “Over

Speeding” message at display panel.

(SRS_REQ_235)

(30)

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

2

Speed: 1 = >= 80 Km/h < 130

Km/h

0 = > 130 Km/h

3 Stop Acceleration: 1 = ON 0 = OFF

Table 4.6 : Cruise Speed Acceleration via “Start Acceleration” Button Test Cases

Test Id Criteria Expected Result Method(s) Level

1 2 3

TC02-A-01

0 0 0

Hazard bolting LED

is highlighted. A, D, I 1

TC02-A-02

0 0 1

Hazard bolting LED

is highlighted. A, D, I 1 TC02-A-03 0 1 0 If speed reaches => 110km/h, “Care to Speed” LED is highlighted. A, D, I 1 TC02-A-04 0 1 1 If speed reaches => 110km/h, “Care to Speed” LED is highlighted. A, D, I 1 TC02-A-05

1 0 0 Hazard bolting LED

is highlighted. A, D, I ₁ TC02-A-06 1 1 0 “Acceleration” message is displayed on the display panel. (SRS_REQ_213) A, D, I ₁

(31)

Table 4.6 : Cruise Speed Acceleration via “Start Acceleration” Button Test Cases(cont.)

Test Id Criteria Expected Result Method(s) Level

1 2 3 TC02-A-07 1 1 0 Speed is increasing. (SRS_REQ_214) A, D, I 1 TC02-A-08 1 1 1

The new cruise speed is set to current speed.

(SRS_REQ_215) A, D, I 1

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-01

Response time for this function to be activated.

(32)

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

Test id Criteria Test Description Expected Method(s) Level

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

(33)

Table 4.9 : Cruise Speed Acceleration via “Accelerator Pedal” and Activation Button Test Cases(cont.)

1 2 TC02-C-04 0 1 1. Press accelerator pedal. (SRS_REQ_216) If current speed => 75km/h, auto cruise mode is Active, and cruise speed = current speed.

(34)

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-01

Within 0.5 second

A, D, I 1

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 Id

Criteria

Expected Result Method(s) Level

1 2 3 TC02-E-01 0 0 0 Not applicable D 1 TC02-E-02 0 0 1 Not applicable D 1 TC02-E-03 0 1 0 Not applicable D 1

(35)

Table 4.12: Description of test case TC02-E(cont) Test

Id Criteria Expected Result Method(s) Level

TC02-E-04 0 1 1 Not applicable D 1

TC02-E-05

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

The activation LED highlights OFF.

D 1

TC02-E-07

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

The activation LED highlights OFF.

(36)

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 Id

Criteria

Expected Result Method(s) Level

1 2 3 TC02-F-01 0 0 0 Not applicable D 1 TC02-F-02 0 0 1 Not applicable D 1 TC02-F-03 0 1 0 Not applicable D 1 TC02-F-04 0 1 1

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

(37)

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

Test

Id Criteria Expected Result Method(s) Level

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

(38)

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-01

Within 0.5 second

A, D, I 1

4.4.1.7 Assumptions and Constraints

(39)

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

The requirement traceability is as identified in the Software 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.

(40)

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

Test id Criteria ₁ ₂ Test Description Expected Method(s) Level

TC03-01 0 0 No change A, D, I 1

TC03-02 0 1 Distance is updated

with latest trip information.

A, D, I 1

TC03-03 1 0 The average speed

value will be displayed on the screen. A, D, I 1 TC03-04 1 1 STEP 1: ‘Average speed’ button is pressed.

Initially the average speed value will be displayed on the screen.

A, D, I 1

Step 2:

‘Begin trip’ button is pressed.

Distance is updated with latest trip information.

(41)

4.5.1.6.4 Test Case to verify stopping time

Table 4.18: Trip Stopping Times Test Cases

TC03-A-01

Vehicle is stopped for a while during a trip.

Average speed computation should not include vehicle-stopping time.

A, D, I 1

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-01

Response time for this

computation to be completed.

Within 1.0 second A, D, I 1

4.5.1.7 Assumption and Constraints

(42)

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

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.

(43)

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 8,000 Km. (SRS_REQ_405)

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

“Oil and Filter Change” message is displayed continuously. (SRS_REQ_405) A, D, I 1 TC04-03 400 Km before reaching 15,000 Km. (SRS_REQ_406)

“Air Filter Change” message is displayed intermittently in 5 seconds every 10 minutes. (SRS_REQ_406) A, D, I 1

(44)

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

TC04-04 80 Km before reaching 15,000 Km.

(SRS_REQ_406)

“Air Filter Change” message is displayed continuously. (SRS_REQ_406) A, D, I 1 TC04-05 400 Km before reaching 25,000 Km. (SRS_REQ_407) “General Maintenance” message is displayed intermittently in 5 seconds every 10 minutes. (SRS_REQ_407) A, D, I 1 TC04-06 80 Km before reaching 25,000 Km. (SRS_REQ_407) “General Maintenance” message is displayed continuously. (SRS_REQ_407) A, D, I 1

TC04-07 Press ‘Service completed’ button. (SRS_REQ_402)

Maintenance message will be cleared.

(SRS_REQ_403)

A, D, I 1

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-08

Response time for respective messages to be displayed. (SRS_REQ_404)

Within 10 second

(45)

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

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 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)

For the criteria in evaluating the test conditions, the Table 4.23 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.

(46)

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 consumption’ button while

cruising.(SRS_REQ_502)

The average fuel consumption on the trip up to the next filling value will be displayed. (SRS_REQ_503) &

(SRS_REQ_504)

(47)

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-01

Press the “Amount of Fuel” button after filling. (SRS_REQ_505)

Enters the amount of fuel in liters via keypad. (SRS_REQ_506) Maximum fuel tank is 35 liter. (SRS_REQ_509)

Press “Valid” key once filling completed. (SRS_REQ_507)

The average fuel consumption between the last two fillings will be displayed. (SRS_REQ_508)

A, D, I 1

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-01

Response time for this computation to be completed.

Within 0.5 second.

(SRS_REQ_510)

A, D, I 1

(48)

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

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 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.

(49)

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

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 “Start Calibration” button (SRS_REQ_602) Message ‘Calibrating’ is displayed. A, D, I 1 C2 not followed by C3. Nothing happened, the number of pulses is not updated default value will be used.

(50)

Table 4.26 : Calibrate Pulses Test Cases(cont.)

1 2 3

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

(51)

Table 4.26 : Calibrate Pulses Test Cases(cont.)

TC06-08 1 1 1 If cruise control is ON, calibration is not allowed.

No change A, D, I 1

Calibration gives impact on average speed calculation and the testing should be done in separate machine.

(52)

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