Download Requirements Specification for Ambulance Management System and more Study Guides, Projects, Research Software Development Methodologies in PDF only on Docsity!
➢Introduction:
This document describes the requirements specification for ambulance Management system.
This document includes functional requirements, non-functional requirements and use cases of the system.
➢Purpose of the system:
The purpose of this System is to cause the entire process to be more efficient, fast, accurate and more effective, the net result of which is to save lives. The purpose also includes the enhancement of the capabilities of ambulance dispatchers in the timely displacement of ambulances to injury scenes in an efficient manner.
➢Scope of the system:
The scope of the AMS starts at when the dispatcher gathers information from the caller. The system would show the location of each patient and the nearest three ambulances. It ends at the patient’s arrival to a hospital.
For What The Online Ambulance Management System Is An android application That Provide convenient, rapid and accurate services.
➢ Overview:
Our Team’s Goal is to build an Ambulance Management System that will greatly enhance the innovative ideas of public safety dispatchers by sending immediate response to resolve an emergency situation. The ambulance Management system should also satisfy the timing requirements given as a part of project scope.
➢Communication description:
1: Hardware:
Sever Side : Cloud with basic configuration for running application such as firebase is necessary for
deploying and testing the system.
Client side : Smartphone with application
2: Software:
Server side:
Database: SQlite
Language: java
Server: firebase
Client side:
Operational system: Android operating system
Software: operating system with java
➢Functional Requirements:
This section describes the functional Requirements of the Ambulance Management System.
1. Receiving Incident information from the caller.
When the request for ambulance comes to the operator, he takes information about the incident from the caller. This information is entered into the ambulance dispatch system. This information includes caller phone number, address (any combination of street name, zip code), description/nature of the incident, number of people involved in the incident. If the caller does not know the exact address of the patient, it is found using an external information a new incident is created in the ambulance dispatch system with all the details. The information added to this incident is called “incident information system.
This external system determines the incident address depending on the caller’s phone number.
With this”.
2. Locating nearest ambulance.
Depending on the location of the incident, this function will determine the nearest 3 available ambulances.
3. Allocating the ambulance to the incident.
Depending on the number of people involved in the incident, dispatcher will allocate the ambulance/s to the incident and add the ambulance details to the system. One ambulance is assigned to each person injured.
4. Dispatch of ambulance and resource.
9. Manage Users
This functionality allows supervisors to maintain the system and add/remove/update new users for the system. Each user (Dispatcher) will have username and password assigned to him.
GPS:
GPS system will be used to get the route details and directions to the incident location.
These details will be used by ambulance personnel to reach the incident location.
The GPS system also gives information about the nearest hospital to the incident location.
Assumptions:
The operator and the dispatcher are assumed to be the same person in this system.
Creating an exception will solve the problem, when an ambulance cannot be found. It will be diverted to the third party who will take care of the situation.
➢ Non-Functional Requirement:
1. Usability
Ambulance Dispatch System shall provide mouse and keyboard navigation.
Ambulance Dispatch System shall be easy to navigate by using clear words, menus and drop-down lists.
Ambulance Dispatch System shall be accompanied with a user manual.
2. Reliability
Ambulance Dispatch System shall be available 24 hours a day for application users.
3. Performance
Ambulance Dispatch System shall not take longer than 15 seconds to respond to a page request for members; when using an internet connection that is 56k or higher
4. Supportability
The ambulance dispatch system application should be supportable in current equipment such as computers, monitors, printers etc.
5. Implementation
The software implementation will be performed on Friday evening to minimize impact. The implementation will be performed all on one day rather than in phases.
6. Interface
Ambulance Dispatch System shall be accessible through a web browser such as Internet Explorer 5 or higher and Netscape Navigator 4.7 or higher
Ambulance Dispatch System shall provide printer friendly outputs of reports so that users can have easy to read print outs of the reports.
7. Packaging
The application is internal department use only and will not be packaged and sold as a retail product.
➢ Use-cases:
1. Login
This use case describes how a user logs into the ambulance dispatch system.
