Ambulance Dispatch System CAD System Test Plan Document Faisal Azizullah Team Lead for del 5 Brandon Bass Team Lead for del 1 5 Ali Hashi Team Lead for del 1 Sonali Jejurkar Team Lead for del 3 6 Sirisha Koneru Team Lead for del 5 Ananthapriya Mummineni Team Lead for del 2 Shveta Mupparapu Team Lead for del 1 Vidya Perumal Team Lead for del 4 Group URL http www ace6354 com adv soft engg aspx Revision History Version 1 0 1 1 Revision Date 07 19 2007 07 21 2007 1 2 07 23 2007 Description Author Initial Draft with test cases Added approach and testing schedule sections Added remaining sections Sonali Jejurkar Sonali Jejurkar Sonali Jejurkar 1 Introduction This is the Master Test Plan for the Ambulance Dispatch System CAD system The document will only address to test following functionalities in the CAD application 1 User Login 2 Retrieve Forgot Password 3 Display of the incident form 4 Admin The primary focus of this plan is to ensure that the new Ambulance Dispatch System provides the desired level of information and details to meet patient s needs while allowing for improvements to dispatch ambulances within the time constraints The testing phase will have 3 levels of testing Unit System Integration and Acceptance The details for each level are addressed in the approach section and will be further defined in the level specific plans The estimated time line for this project is very aggressive eight 8 weeks as such and delays in the development process or in the installation and verification of the application could have significant effects on the test plan The acceptance testing is expected to take 2 days from the date of application delivery from system test and is to be done in parallel with the current application process 2 Relationship to other documents 1 Connection with Requirements Analysis Document RAD We defined the accurate problem statement and agreed on the solution domain for the Computer Aided Dispatch CAD system in this phase We produced use cases realized them by sequence diagrams and Analysis level class diagrams 2 Connection with System Design Document SDD In this phase of the project we decomposed the system into subcomponents and defined how the subcomponents will interact with each other We decided that we would use 3tier client server architecture for the proposed system 3 Connection with Object Design Document ODD From the components that were in the design phase we came up with package diagram in this phase Then we refined the class diagram from RAD phase In this phase we added visibility signature pre post conditions and associations between the classes to the class diagram The final class diagram was mapped to code 3 System overview Computer Aided Dispatch CAD system s goal is to provide fastest ambulance service to the victims of any emergency incidents To achieve this goal the system is decomposed into User Login Interface Location Tracking System LTS Interface Incident form and Admin The CAD system assumes the input from Dispatcher Interface processes it sends the caller s phone number to LTS Interface and receives the location details from LTS The Dispatcher Interface is used by a 911 ambulance dispatcher that stores all the information provided by the caller This information includes address of the incident number of people injured number of ambulances required and type of emergency After processing this information an appropriate incident report is created by this system and sent to the Dispatcher system as an input The CAD system under consideration is built assuming validated report of an incident exists and is provided to CAD as an input The CAD system is designed to locate the available ambulances near the incident location and dispatch them as per the requirement with the help of LTS We assume that LTS provides incident location and this will be used by CAD to derive driving directions LTS is a highly sophisticated navigation system that provides location details by accepting caller s phone number as an input All interfaces are closely interlinked and with validated inputs to the system interfaces an attempt is made to dispatch the ambulance within 3 minutes range 4 Features to be tested not to be tested 4 Features to be tested The following are the major functionalities of the application that need to be tested in the testing process a User Login screen b Admin c Incident information d Location tracker 5 Features not to be tested In RAD document we had defined the scope of the system as follows Phase 1 When the dispatcher receives an emergency call from the caller he she communicates with the Ambulance system checks for the availability of ambulances and allocates an ambulance with the help of the CAD system within the 3 minutes time constraint Phase 2 Based on the preference of the patient the CAD system finds the nearest hospital However due to time constraint we have only implemented the functionalities listed in the section 4 1 Features to be tested Therefore all other functional requirements and non functional requirements should not be tested 5 Pass Fail criteria The final test process will be completed once the Computer Aided Dispatch System CAD application receives a phone call from 911 services efficiently records the details of an emergency incident including location finds the next available ambulance and dispatches the ambulance within 3 minutes When the operations staff is satisfied that the data is correct and appropriate services are provided to incident victims then the system will be considered live At this point with the current development stage we will check if all the interfaces including location tracker user login and admin and incident info are functioning properly Later as we progress with development and add more functionality to the application we will grow the scope of test plan as well 6 Approach Testing Levels As shown in the above class diagram we have implemented 3 main functionalities of the CAD system and they are as follows 1 User Login 2 Retrieve Forgot Password 3 Display of the Incident Form The testing for the CAD system will consist of Unit System Integration combined and Acceptance test levels We will have one full time person for system integration testing UNIT testing will be done by the developers and will be approved by the entire team Proof of unit testing test case list sample output defect information is provided to the team before unit testing will be accepted and passed on for the final