Ambulance Dispatch System
Preliminary Project Plan
Brandon Bass (SID: 10201589; email: )
Sonali Jejurkar
Vidya Perumal
Sirisha Koneru
Ali Hashi
Faisal Azizullah
Shveta Mupparapu
Ananthapriya Mummineni
http://ace6354.com/adv_soft_engg.aspx
Submitted for:
CS 6354.581
Phase 0
1. Introduction
1.1 Project overview
This is a project plan to be used for the implementation of the ambulance dispatch system. The project includes creating an ambulance dispatch system whereby the information regarding an emergency can be recorded, ambulances can be dispatched to the scene of an emergency within a three-minute deadline, and ambulances can be tracked during their transit through the use of a GPS system.
The system as a whole will have three main components. There will be a dispatcher interface, an incident processing system, and an external database. The dispatcher interface will allow the ambulance dispatcher to enter the information they receive from the caller about an incident (address of the incident, number of injured people, etc) so that it can be processed by the incident processing system. The incident processing system will interact with an external database that holds the information about each incident as well as the current ambulance location data. The system will check if each newly submitted form might be a duplicate and will bring this information to the attention of the ambulance dispatcher. The system will locate a suitable ambulance and mobilize it within three minutes. If no ambulance is available within an eleven-minute window the incident processing system will raise an exception message on the dispatcher interface and the location of the nearest three ambulances will be displayed.
1.2 Project deliverables
The following are the deliverables for this project:
a) Preliminary Project Plan ------Deliverable 0
b) Requirements Elicitation –------Deliverable 1
c) Requirements Analysis ------Deliverable 2
d) Architectural Design ------Deliverable 3
e) Object/Component Design ------Deliverable 4
f) Coding ------Deliverable 5
g) Testing ------Deliverable 6
1.3 Evolution of this document
This is a preliminary document with the scope of the project.
1.4 References
1.5 Definitions, acronyms, and abbreviations
· Operator: A person that initially receives the phone call to 911 and directs calls requiring an ambulance to the ambulance dispatcher.
· Dispatcher: A person that receives 911 phone calls requiring an ambulance and enters the caller’s information in to the ambulance dispatcher program.
2. Project organization
2.1 Process model
Our design process will be based heavily on the creation of UML diagrams for the project. With good UML diagrams, we will have a basis for the system, a basis for group programming, and a graphical representation of the system for use in this document. We will be using Waterfall model for our project development with few exchanges between intermediate phases.
2.2 Organizational structure
The members involved in developing this project are:
· Sonali Jejurkar
· Brandon Bass
· Vidya Perumal
· Sirisha Koneru
· Ali Hashi
· Faisal Azizullah
· Shveta Mupparapu
· Ananthapriya Mummineni
For the first deliverable Brandon Bass will be the Team Leader for the project.
2.3 Organizational boundaries and interfaces
2.4 Project responsibilities
All the team members will be involved in all phases of the project life cycle.
3. Managerial process
3.1 Management objectives and priorities
The main objective of the management position is to organize the meetings for discussions, check the status of the project, and submit the project on time.
3.2 Assumptions, dependencies, and constraints
3.3 Risk management
3.4 Monitoring and controlling mechanisms
4. Technical process
4.1 Methods, tools, and techniques
Rational Rose tool will be used to do the UML modeling. The system will be implemented in Java. The reason for this is two-fold: our programmers are more familiar with Java than other languages and Java offers easy, effective interfaces will be very useful in this project. Our project team is using GoogleGroups for easy team member communication. All project documents will be posted on our team website at http://ace6354.com/adv_soft_engg.aspx.
4.2 Software documentation
4.3 Project support functions
5. Work elements, schedule, and budget
This project is scheduled to be completed by July 11th 2007 for the final demo. Here is the outline of the timeline of the deliverables:
Deliverable 1 due by 06/13/2007
Deliverable 2 due by 06/20/2007
Deliverable 3 due by 07/02/2007
Deliverable 4 due by 07/11/2007
Deliverable 5 & 6 due by 07/18/2007 – 07/23/2007