The Fantastic 9 CS 6354 Summer 2007 ADS An Ambulance Dispatch System Test Plan CS 6354 Advanced Software Engineering Section 581 Summer 2007 The Fantastic 9 Arturo Saracho Denis Stetsenko Sarthak Dudhara Abdullah Azzouni Russell Smith Anitha John Abhishek Goyal Nate Gardner Sheetal Umeshkumar axs067000 utdallas edu dxs067000 utdallas edu 11120701 skd051000 utdallas edu 11138921 ama063100 utdallas edu rss061000 utdallas edu akj041000 utdallas edu axg056100 utdallas edu 11152135 njg011100 utdallas edu sxu054000 utdallas edu 1 10829000 11126187 10480080 11139363 10080880 11108292 The Fantastic 9 CS 6354 Summer 2007 ADS An Ambulance Dispatch System Table of Contents 2 AUDIENCE 3 3 INTRODUCTION 3 4 RELATIONSHIP TO OTHER DOCUMENTS 3 5 SYSTEM OVERVIEW 4 6 FEATURES TO BE TESTED NOT TO BE TESTED 4 7 PASS FAIL CRITERIA 4 8 APPROACH 4 9 SUSPENSION AND RESUMPTION 5 10 TESTING MATERIALS HARDWARE SOFTWARE REQUIREMENTS 5 10 1 HARDWARE 5 10 2 SOFTWARE 5 10 3 AUTOMATION TOOLS 6 11 TEST CASES 6 11 1 LOGON 6 11 2 EXTRACT LOGS 8 11 3 DISPLAYREPORTS 10 11 4 LOCATENEARESTAVAILABLEHOSPITAL 11 11 5 PLACEPHONECALL 13 11 6 TRACEBYADDRESS 14 11 7 TRACEBYAREA 16 11 8 GATHERINFORMATION 18 11 9 OPENCASE 19 11 10 LOCATECASESITE 21 11 11 MODIFYCASE 22 11 12 TRACKCASE 24 11 13 PICKUPCASE 25 11 14 DELIVERCASE 27 11 15 CLOSECASE 29 11 16 CREATEUSER 30 11 17 MODIFYUSER 31 11 18 DELETEUSER 33 11 19 CREATEAMBULANCE 34 11 20 DISPATCHNEARESTAMBULANCE 36 11 21 MODIFYAMBULANCE 38 11 22 TRACKAMBULANCE 40 11 23 DELETEAMBULANCE 41 12 TESTING SCHEDULE 43 12 1 STAFFING AND TRAINING NEEDS 43 12 2 SCHEDULE 43 12 3 Testing Risk and Contingency Plan 43 2 The Fantastic 9 1 CS 6354 Summer 2007 ADS An Ambulance Dispatch System Purpose This test plan document describes the objectives scope approach and focus of the testing of the ADS system This document begins with an overview of the Ambulance Dispatcher System It then lists the high level features to be tested as part of the testing cycle The document also lists the application features that will not be tested It further delves into the details of the hardware software and environmental needs for carrying out an efficient and smooth testing It then discusses the high level testing schedule and the resource responsible for testing each of the features It then briefly describes the pass fail criteria and risks associated with the testing The document ends with a detailed description of the test case that will be executed as part of the testing 2 Audience This test plan document has been written for the following audience 3 1 Project Manager 2 Test Manager 3 Business Analyst 4 Development Team 5 Test Team 6 Onsite coordinators Introduction The software will be tested and determined to be ready for delivery and of accepted quality based on the results of the functional testing In brief the tests have to satisfy all of the customer s and internal requirements by successfully passing all test cases The functional testing verifies conformance to the customer requirements and it verifies as well that not unexpected behavior outside the requirements is present 4 Relationship to other documents The requirements specification presents the requirements from the customer as well as internal requirements The requirements are numbered to provide for an easy way to trace the test cases to each requirement Each of the requirements corresponds to one or more use cases in the analysis documentation RAD As well the object design document and the design document provide more information about how the implementation of the functionality is done which serves to better understand how to perform the white box testing 3 The Fantastic 9 5 CS 6354 Summer 2007 ADS An Ambulance Dispatch System System overview The system is composed of several independent components that execute some of the functionality and together form a 911 emergency dispatch system The sequence of events is as follows 6 A person will call 911 and the operator dispatcher that answers the call gets the details about location from the person Dispatcher also needs to ask how many people are injured in case many ambulances are needed The dispatcher enters the location information on the system A Timer is started counting down from 11 minutes The system locates the nearest three ambulances and their availability if no ambulance is available it will locate the next three nearest from the initial three and check availability this will be repeated until one that is available is found When an available ambulance is found location details will be sent to the unit and will be instructed to go to location for pickup The system will monitor ambulance s and person s locations for tracking purposes When the ambulance reaches the destination the system will wait for confirmation from the ambulance that the objective has been reached If Timer reaches zero and no ambulance was found available an exception message will be generated and given to the dispatcher Features to be tested not to be tested Testing will be done to the system in order to satisfy all requirements this means all functionality as specified in the class diagrams and sequence diagrams has to be verified Verification of this will assure that the design is working as expected by the developers and will verify as well that the requirements have been satisfied 7 Pass Fail criteria A test case will be determined to have been successfully executed and passed if and only if all conditions stated are satisfied All inputs have to be exercised environment has to be setup and outputs must be read and verified as having the expected values Else the test case is declared failed 8 Approach The functional testing will be done by unit testing the independent modules making sure the test case is passed and all corresponding requirements are satisfied After completion of the unit tests and making sure all successfully pass integration will be done and validation of the integrated code will take place this will be done by considering the whole software as one unit with several inputs and outputs 4 The Fantastic 9 9 CS 6354 Summer 2007 ADS An Ambulance Dispatch System Suspension and resumption Unit testing can be suspended if necessary by making sure all corresponding test cases that have been initiated are finished and a pass fail result is given All remaining not initiated test cases will then be executed when testing is resumed Testing can be suspended in the event of the need to make a modification to a