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

Transcription

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: CENTRE FOR ADVANCED SOFTWARE ENGINEERING

2 DOCUMENT APPROVAL REVISION NAME DATE Verified By: Mohd. Ariffin Nizar PROJECT LEADER Authenticated By: Mr. Mohd. Nazri bin Kama PROJECT MANAGER Approved By: Mr. Mohd Naz ri bin Mahrin CLIENT Software : Microsoft Word 2000 Archiving Place : \IlimitadoDominio\SoftwareDocument\STD\ID Copies Available : DOC Page i of viii

3 REVISION HISTORY REVISION A B First draft before TRR DESCRIPTION. 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. Nazri Kama Mohd bin Approved by En. Naz ri Mahrin Page ii of viii

4 LIST OF EFFECTIVE PAGES PAGES REVISION PAGES REVISION Page iii of viii

5 TABLE OF CONTENTS 1 SCOPE Identification Overview of the System Overview of the Document APPLICABLE DOCUMENTS Government documents Non- Government documents Contractual documents Non-Contractual documents OBA01TC0A - Setup\Installation OBA01TC0B - Launch Bench FORMAL QUALIFICATION TEST DESCRIPTIONS Test Case Specification: OBA01TC0A Setup\Installation Test case name : TC0A Setup\Installation Requirements traceability Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and constraints Test Case Specification: OBA01TC0B Launch Bench Test Case Name: TC0B Launch Bench Requirements traceability Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and constraints Test Case Specification: OBA01TC01 Initialize OBA Test case name: TC01 Initialize OBA Requirements traceability (STD_REQ_100) Page iv of viii

6 Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and constraints Test Case Specification: OBA01TC02 Control Cruise Speed Test case name: TC02 Control Cruise Speed Requirements traceability (STD_REQ_200) Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and Constraints Test Case Specification: OBA01TC03 Calculate Average Speed Test case name: TC03Calculate Average Speed Requirements traceability (STD_REQ_300) Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumption and Constraints Test Case Specification: OBA01TC04 Monitor Maintenance Schedule Test case name: TC04 Monitor Maintenance Schedule Requirements traceability (STD_REQ_400) Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and Constraints Test Case Specification: OBA01TC05 Monitor Fuel Consumption Test case name: TC05 Monitor Fuel Consumption Page v of viii

7 Requirements traceability (STD_REQ_500) Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and Constraints Test Case Specification: OBA01TC06 Calibrate Pulses Test case name: TC06 Calibrate Pulses Requirements traceability (STD_REQ_600) Initialization Test input Expected test result Criteria for evaluating results Test procedure Assumptions and Constraints NOTES APPENDIX. 44 Page vi of viii

8 LIST OF TABLES Table 3.2: Qualification Methods... 9 Table 3.3: Qualification Levels Table 4.1: Description of Test Case TC0A Table 4.2: Description of test case TC0B Table 4.3: OBA Initialization Test Cases Table 4.4: Control Cruise Speed Test Cases Table 4.5: Test Condition and Criteria for Cruise Speed Acceleration via Start Acceleration Button Table 4.6 : Cruise Speed Acceleration via Start Acceleration Button Test Cases Table 4.7: Cruise Speed Acceleration via Start Acceleration button Response Time Test Cases 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 Table 4.11: Test Condition and Criteria for Auto-Cruise Suspension via Brake Pedal With Deactivation Table 4.12: Auto-Cruise Suspension via Brake Pedal With Deactivation Test Cases Table 4.13: Test Condition and criteria for Auto-Cruise Suspension via Brake Pedal With Resume Table 4.14: Auto-Cruise Suspension via Brake Pedal With Resume Test Cases Table 4.15: Auto-Cruise Suspension via Brake Pedal With Resume Response Time Test Case Table 4.16: Test Condition and Criteria for Calculate Average Speed Table 4.18: Trip Stopping Times Test Cases Table 4.19: Average Speed Calculation Response Time Test Cases Table 4.20: Monitor Maintenance Schedule Test Cases Table 4.21: Respective Message Response Time Test Cases Table 4.22: Fuel Consumption Monitoring during Trip Test Cases Table 4.23 : Fuel Consumption between Two Filings Test Cases Page vii of viii

9 Table 4.24: Average Fuel Consumption Calculation Response Time Test Cases Table 4.25: Test Condition and Criteria for Calibrate Pulses Table 4.26 : Calibrate Pulses Test Cases Page viii of viii

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. Page 1 of 43

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. iii. iv. Maintenance scheduling Average speed calculation 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. iii. iv. Control Cruise Speed (TC02) Calculate Average Consumption (TC03) 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. Page 2 of 43

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 Requirements Specification Page 3 of 43

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 Page 4 of 43

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 Schedule The schedule is stated below: i. Location : CASE Lab ii. Date : 20/03/2005 iii. Time : am The testing will be conducted by : QM Manager Pre-test Procedures 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. Page 5 of 43

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 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. iii. The storage medium for the items shall be on the LINUX platform. The following software modules must be loaded: i. Simulator ii. iii. Test Bench OBA application component iv. The minimum requirements to install the OBA application are listed below: i. Operating System: LINUX ii. Programming Language: C++ Language Page 6 of 43

16 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 Schedule The schedule is stated below: i. Location : CASE Lab ii. Date : 17/03/2005 iii. Time : 09.00pm The testing will be conducted by : QM Manager Pre-test Procedures Hardware Preparation The hardware that is mentioned in section must be available and functioning Software Preparation The software that is mentioned in section must be able to integrate with the simulation environment Other Pre-test Preparations None. Page 7 of 43

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. iii. iv. Control Cruise Speed (TC02) Calculate Average Consumption (TC03) 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 Schedule The schedule is stated below: i. Location : CASE Lab ii. Date : 20/03/2005 iii. Time : am The testing will be conducted by : QM Manager Pre-test procedures Hardware Preparation The hardware that is mentioned in section must be available and functioning Software Preparation The software that is mentioned in section must be able to integrate with the simulation environment. Page 8 of 43

18 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. iii. iv. Uphill Road Downhill Road Funny Road v. Bumpy Road 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. Page 9 of 43

19 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 2. System Integration 1 The item is configured and traced to completion. 2 Components required for integration. 3. System 3 System components. 4. System Installation 4 Components required for installation. Page 10 of 43

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 Test case name : TC0A Setup\Installation Requirements traceability None Initialization Workstation must be properly working Test input The hardware is an LINUX equipped operating platform consisting of C programming language Expected test result The test result is shown as in Table 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. Page 11 of 43

21 Test procedure Basic Flow - Installation procedure 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 components from mpt0508/home/oba to OBA folder: All components are copied. D 1 Cruise.exe OBA.exe Assumptions and constraints None Page 12 of 43

22 4.2 Test Case Specification: OBA01TC0B Launch Bench The following test case is designed to launch the OBA test bench Test Case Name: TC0B Launch Bench Requirements traceability None Initialization Workstation must be properly working Test input Main components of OBA application are loaded on the workstation, which are : i. OBA.exe ii. Cruise.exe Expected test result Expected result is shown in Table Criteria for evaluating results 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 Test procedure Launch Bench To test the Launch Bench functions. Page 13 of 43

23 Test Case to verify the launch bench Table 4.2: Description of test case TC0B Test id Test Description Expected Method(s) Level TC0B Enter. envi.sh Test Bench Screen is D 1 command. 2. Enter./runOTB. displayed. Refer to Figure 4.1. TC0B-02 From the Choose a car cruise simulation.exe file section press Browse and select Cruise.exe file. The Automobile Driving Controls, Automobile Dashboard and OBA Panel will be loaded and ready to D 1 Press Get the Car. run. From the Choose the OBA.exe file section press Browse and select OBA.exe file. Press Run the OBA. Page 14 of 43

24 Assumptions and constraints 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 The constraints considered during testing are: i. Test conducted that neither modifies nor corrupts the software Page 15 of 43

25 4.3 Test Case Specification: OBA01TC01 Initialize OBA The following test case is designed for the Initialize OBA component Test case name: TC01 Initialize OBA Requirements traceability (STD_REQ_100) The requirement traceability is as identified in the Software Requirement Specification. Please refer Appendix for the Traceability Matrix Table Initialization Workstation must be properly working Test input Main components of OBA application are loaded on the workstation, which are : i. OBA.exe ii. Cruise.exe Expected test result Expected result is shown in Table Criteria for evaluating results 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. Page 16 of 43

26 Test procedure Initialize OBA To initialize the OBA Test Case to verify the OBA Initialization Table 4.3: OBA Initialization Test Cases Test id Test Description Expected Method(s) Level 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 Assumptions and constraints 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 The constraints considered during testing are: i. Test conducted that neither modifies nor corrupts the software Page 17 of 43

27 4.4 Test Case Specification: OBA01TC02 Control Cruise Speed This test case is to test the Control Cruise Speed component Test case name: TC02 Control Cruise Speed Requirements traceability (STD_REQ_200) The requirement traceability is as identified in the Software Requirement Specification. Please refer Appendix for the Traceability Matrix Table Initialization i. The OBA is initialized via TC01. ii. Simulator is on the highest transmission gear, gear 5 iii. iv. Minimum speed is 75km/h Brake Pedal is released v. Clutch Pedal is released Test input The Activation is pressed Expected test result Expected result is shown in Table Criteria for evaluating results 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. Page 18 of 43

28 Test procedure Control Cruise Speed This functionality shall be able to maintain the cruise speed in its valid range at various tested conditions Basic Flow of Events Test Case to verify the control cruise Speed Table 4.4: Control Cruise Speed Test Cases Test id Test Description Expected Method(s) Level 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) TC02-02 TC02-03 TC02-04 TC02-05 TC02-06 The system maintains constant cruise speed by regulating voltage to the throttle. (SRS_REQ_236) & (SRS_REQ_239) During normal cruising, speed is 1 km/h above normal cruise speed. (SRS_REQ_240) During normal cruising, speed is 1 Km/h below normal cruise speed. (SRS_REQ_241) The acceleration reaches 1.2km/h/sec value while cruising. (SRS_REQ_237) The acceleration reaches 0.8km/h/sec value while cruising. (SRS_REQ_238) The activation LED highlights ON. (SRS_REQ_209) System keeps the speed at + or 1 km/h in relation to the selected speed. (Normal Grade) (SRS_REQ_236) & (SRS_REQ_239) Speed will be decreased to cruise speed. (Downgrade) (SRS_REQ_240) Speed will be increased to cruise speed. (Upgrade) (SRS_REQ_241) Speed will be decreasing due to closed throttle. (SRS_REQ_237) Decrease +/- 1 to cruise speed?? Speed will be increasing due to opened throttle. Increase +/- 1 to cruise speed?? (SRS_REQ_238) Table 4.4: Control Cruise Speed Test Cases (cont.) Page 19 of 43

29 Test id Test Description Expected Method(s) Level TC02-07 Cruise speed reaches 110km/h while cruising. (SRS_REQ_234) The Care to Speed LED is highlighted. (SRS_REQ_234) TC02-08 Cruise speed reaches 130km/h while cruising. (SRS_REQ_234) And, system shall display Over Speeding message at display panel. (SRS_REQ_235) The Hazard Bolting LED is highlighted. (SRS_REQ_234) And, system shall display Over Speeding message at display panel. (SRS_REQ_235) Page 20 of 43

30 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 TC02-A- 01 TC02-A- 02 TC02-A- 03 TC02-A- 04 TC02-A- 05 TC02-A Hazard bolting LED is highlighted. Hazard bolting LED is highlighted If speed reaches => 110km/h, Care to Speed LED is highlighted If speed reaches => 110km/h, Care to Speed LED is highlighted Hazard bolting LED is highlighted Acceleration message is displayed on the display panel. (SRS_REQ_213) Page 21 of 43

31 Table 4.6 : Cruise Speed Acceleration via Start Acceleration Button Test Cases(cont.) Test Id Criteria Expected Result Method(s) Level TC02-A Speed is increasing. (SRS_REQ_214) TC02-A The new cruise speed is set to current speed. (SRS_REQ_215) 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 Test id Test Description Expected Method(s) Level TC02-B- Response time for this Within 0.5 second 01 function to be activated. Page 22 of 43

32 Test Case to verify the accelerating cruise speed functionality via Accelerator Pedal Table 4.8: Cruise Speed Acceleration via Accelerator Pedal and Activation Button Test Criteria Test Condition Test Condition 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 TC02-C- 01 Criteria 1 2 Test Description Expected Method(s) Level Press accelerator pedal. (SRS_REQ_216) Speed increasing. (SRS_REQ_217) 2. Release accelerator Cruise speed is pedal. set to previous (SRS_REQ_218) speed. (SRS_REQ_218) TC02-C Press accelerator Speed 02 pedal. increasing. (SRS_REQ_216) (SRS_REQ_217) Cruise speed is set to current speed. (SRS_REQ_218) TC02-C Press accelerator pedal. (SRS_REQ_216) Not in cruise mode and manual driving speed is increasing. Page 23 of 43

33 Table 4.9 : Cruise Speed Acceleration via Accelerator Pedal and Activation Button Test Cases(cont.) Test id TC02-C- 04 Criteria 1 2 Test Description Expected Method(s) Level Press accelerator pedal. (SRS_REQ_216) If current speed => 75km/h, auto cruise mode is Active, and cruise speed = current speed. Page 24 of 43

34 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 activated. second Test Case to verify the auto cruise suspension via Brake Pedal With Deactivation Table 4.11: Test Condition and Criteria for Auto-Cruise Suspension via Brake Pedal With Deactivation Test Criteria Test Condition Test Condition 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 TC02-E Not applicable TC02-E Not applicable TC02-E Not applicable D 1 D 1 D 1 Page 25 of 43

35 Table 4.12: Description of test case TC02-E(cont) Test Id Criteria Expected Result Method(s) Level Not applicable D The activation LED highlights ON. System displays SUSPEND message. Cruise speed decreasing. D The activation LED highlights OFF. D The activation LED highlights ON. System displays SUSPEND message. Cruise speed decreasing. D 1 TC02-E- TC02-E- TC02-E- TC02-E- TC02-E The activation LED highlights OFF. D 1 Page 26 of 43

36 With Resume Table 4.13: Test Condition and criteria for Auto-Cruise Suspension via Brake Pedal With Resume Test Criteria Test Condition Test Condition 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 TC02-F Not applicable D 1 TC02-F Not applicable D 1 TC02-F Not applicable D 1 TC02-F- Cruise speed is set to previous cruise speed. D 1 (SRS_REQ_225) TC02-F- Speed decreasing D 1 05 continuously System displays SUSPEND message. Page 27 of 43

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 TC02-F Resume failed. Speed decreasing. System displays SUSPEND message. Resume failed. Speed decreasing. System displays SUSPEND message. D 1 D 1 Page 28 of 43

38 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 Test id Test Description Expected Method(s) Level TC02-G- 01 Response time for this function to be activated. Within 0.5 second Assumptions and Constraints None Page 29 of 43

39 4.5 Test Case Specification: OBA01TC03 Calculate Average Speed The following test case is for the Calculate Average Speed component testing Test case name: TC05Calculate Average Speed Requirements traceability (STD_REQ_300) 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 Initialization The engine should be started and running. The Begin trip button is pressed at least once Test input Prior to the testing of this component, the average speed button is available Expected test result Expected result is shown in Table Criteria for evaluating results For the criteria in evaluating the test conditions, the Table 4.16 and table 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 Test procedure Page 30 of 43

40 Calculate Average Speed To test average speed functions Basic Flow of Events Test Case to verify the Calculate Average Speed functionality Table 4.16: Test Condition and Criteria for Calculate Average Speed Test Criteria Test Condition Test Condition 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 TC No change TC Distance is updated with latest trip information. TC The average speed value will be displayed on the screen. TC STEP 1: Initially the average Average speed button is pressed. speed value will be displayed on the screen. Step 2: Begin trip button is pressed. Distance is updated with latest trip information. Page 31 of 43

41 Test Case to verify stopping time Table 4.18: Trip Stopping Times Test Cases Test id Test Description Expected Method(s) Level TC03-A- Vehicle is stopped for a while Average speed 01 during a trip. computation should not include vehiclestopping time Test Case to verify calculates average speed function s response time Table 4.19: Average Speed Calculation Response Time Test Cases Test id Test Description Expected Method(s) Level TC03-B- 01 Response time for this computation to be completed. Within 1.0 second Assumption and Constraints Average speed calculation should be tested on different road profile. Page 32 of 43

42 4.6 Test Case Specification: OBA01TC04 Monitor Maintenance Schedule The following test case is for the Monitor Maintenance Schedule component testing Test case name: TC04 Monitor Maintenance Schedule Requirements traceability (STD_REQ_400) 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 Initialization 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 Test input The maintenance milestone is reached Expected test result Expected result is shown in Table Criteria for evaluating results 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. Page 33 of 43

43 Test procedure Monitor Maintenance Schedule To display maintenance message once the milestone is reached Basic Flow of Events This flow begins when the maintenance milestone is reached. (SRS_REQ_401) Test Case to verify the monitor maintenance schedule Table 4.20: Monitor Maintenance Schedule Test Cases Test id Test Description Expected Method(s) Level TC Km before reaching 8,000 Km. (SRS_REQ_405) TC Km before reaching 8,000 Km. (SRS_REQ_405) TC Km before reaching 15,000 Km. (SRS_REQ_406) Oil and Filter Change message is displayed intermittently in 5 seconds every 10 minutes. (SRS_REQ_405) Oil and Filter Change message is displayed continuously. (SRS_REQ_405) Air Filter Change message is displayed intermittently in 5 seconds every 10 minutes. (SRS_REQ_406) Page 34 of 43

44 Table 4.20: Monitor Maintenance Schedule Test Cases (cont.) Test id Test Description Expected Method(s) Level TC Km before reaching 15,000 Km. (SRS_REQ_406) TC Km before reaching 25,000 Km. (SRS_REQ_407) TC Km before reaching 25,000 Km. (SRS_REQ_407) TC04-07 Press Service completed button. (SRS_REQ_402) Air Filter Change message is displayed continuously. (SRS_REQ_406) General Maintenance message is displayed intermittently in 5 seconds every 10 minutes. (SRS_REQ_407) General Maintenance message is displayed continuously. (SRS_REQ_407) Maintenance message will be cleared. (SRS_REQ_403) Test Case to verify respective message response time. Table 4.21: Respective Message Response Time Test Cases Test id Test Description Expected Method(s) Level TC06-A- 08 Response time for respective messages to be displayed. (SRS_REQ_404) Within 10 second Assumptions and Constraints None. Page 35 of 43

45 4.7 Test Case Specification: OBA01TC05 Monitor Fuel Consumption The following test case is designed for the Calculate Average Fuel Consumption component Test case name: TC05 Monitor Fuel Consumption Requirements traceability (STD_REQ_500) 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 Initialization 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 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) Expected test result Expected result is shown in Table Criteria for evaluating results 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. Page 36 of 43

46 Test procedure Monitor Fuel Consumption To test average fuel consumption function Basic Flow of Events 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 Test id Test Description Expected Method(s) Level 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) Page 37 of 43

47 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 Test id Test Description Expected Method(s) Level TC05-A- Press the Amount of Fuel button The average fuel 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) Test Case to verify calculates average fuel consumption function s response time. Table 4.24: Average Fuel Consumption Calculation Response Time Test Cases Test id Test Description Expected Method(s) Level TC05-B- Response time for this computation Within to be completed. second. (SRS_REQ_510) Assumptions and Constraints None Page 38 of 43

48 4.8 Test Case Specification: OBA01TC06 Calibrate Pulses The following test case is test on the calibrate speed and distance functionality Test case name: TC06 Calibrate Pulses Requirements traceability (STD_REQ_600) 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 Initialization 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) 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 Expected test result Expected result is shown in Table Criteria for evaluating results 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. Page 39 of 43

49 Test procedure Calibrate Pulses To test calculate calibrate pulses functions Basic Flow of Events Test Case to verify the calibrate pulses function. Table 4.25: Test Condition and Criteria for Calibrate Pulses Test Criteria Test Condition Test Condition 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 TC No change TC No change TC C2-Press the Start Calibration button (SRS_REQ_602) C2 not followed by C3. Message Calibrating is displayed. Nothing happened, the number of pulses is not updated default value will be used. Page 40 of 43

50 Table 4.26 : Calibrate Pulses Test Cases(cont.) Test id Criteria Test Description Expected Method(s) Level TC C2, then drives for at least 1 Km (SRS_REQ_603), followed by C3. 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. C2, then a driver drives > 1.2 Km followed by C3. TC If cruise control is ON, calibration is not allowed. TC If cruise control is ON, calibration is not allowed. TC If cruise control is ON, calibration is not allowed. Message Calibration Complete displayed and the new reference value of the number of pulses has been stored. Message Calibration Incomplete displayed and the number of pulses is not updated, default value will be used. No change No change No change Page 41 of 43

51 Table 4.26 : Calibrate Pulses Test Cases(cont.) Test id Criteria Test Description Expected Method(s) Level TC If cruise control is ON, calibration is not allowed. No change Assumptions and Constraints Calibration gives impact on average speed calculation and the testing should be done in separate machine. Page 42 of 43

52 5 NOTES Abbreviations used:- CASE - CDRL - CSCI - Centre for Advance Software Engineering Contractual Document Requirement List 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 Page 43 of 43