The number. Req. 7 If successful, the driver

The Ambulance tracking System supportsthe following users: the admin and the ambulance driver. The admin tasksconsist of logging into the system, emergency data entry, monitoring theprogress of the system, and logging out of the system. The ambulance driver isthe key person to respond to the status queries.

This setup leads to thefollowing functional requirements:  1.1.1          Logging InReq.

1 The userwill log into the system by entering his/her dispatcher identification numberand password.Req. 2 The useridentification number will be a 5 digit decimal number. Req. 3 Afterlogging in, the user will be taken to the user home screen.

1.1.2          Data EntryReq. 4 After answering a call, the admin will gatherand enter the information into the system.  1.

Best services for writing your paper according to Trustpilot

Premium Partner
From $18.00 per page
4,8 / 5
4,80
Writers Experience
4,80
Delivery
4,90
Support
4,70
Price
Recommended Service
From $13.90 per page
4,6 / 5
4,70
Writers Experience
4,70
Delivery
4,60
Support
4,60
Price
From $20.00 per page
4,5 / 5
4,80
Writers Experience
4,50
Delivery
4,40
Support
4,10
Price
* All Partners were chosen among 50+ writing services by our Customer Satisfaction Team

1.3          Data EntryCorrections/SuggestionsReq. 5 Thesystem will correct formatting errors and offer suggestions (i.e. allow addressand emergency abbreviations) to the dispatcher during the data entry process.1.1.4          Caller AddressLocationReq.

6 As soon as thecall is received, the system will automatically start the address locationprocedures based on the caller’s phone number.Req. 7 If successful, thedriver will verify the address with the caller.Req.

8 If not, the driverwill ask the caller about his/her location. 1.1.5          Duplicate CallsDetectionReq.

9 The system will detect potential duplicate calls (calls from 2 or morepeople describing the same emergency) by performing a quick comparison of thelocations and emergency descriptions of all incoming calls and notifyingresponsible dispatchers if a similar emergency is already in the system.     1.1.6           AmbulanceLocationReq. 10 Thesystem will locate the 3 available ambulances that are closest to the emergencylocation and present them to the dispatcher in a graphical format, i.e. bydisplaying a map and marking locations of the emergency and the ambulances.Req.

11 Afterthe admin chooses one of them the system should transmit the emergencyinformation to the ambulance’s mobile receiving unit and start the status monitoringprocess.1.1.7          No AvailableAmbulancesReq. 12In case the system cannot find any available ambulances in the area, the systemwill query the status of the ambulances currently allocated to otheremergencies, select 3 that are soon-to-be-available, and present them to thedispatcher. He/she should make the final decision.

1.1.8          Exception MessageReq.

13 An exceptionmessage will be generated for the admin if no ambulance is allocated within 11minutes of the admin’s data entry.Req. 14 Thisexception message will read: “ERROR: NO AMBULANCES HAVE BEENALLOCATED”.

Req. 15 Uponreceiving this message, the user will be required to manually select anambulance by entering the ambulance’s identification number. Req. 16 Ambulanceidentification numbers will be 3 hexadecimal digits.  1.1.

9          Communication withthe AmbulanceReq. 17 The system willhave an interface to communicate with the ambulance driver.Req.

18 The system willallow sending the emergency information to the ambulance as well as queryingthe ambulance about the status of the emergency.1.1.10      Hospital AvailabilityReq.19 As soon as the user allocates anambulance to the emergency, the system should present him/her with 3 hospitalsclosest to the emergency location.1.

1.11      MonitoringPerformance and PositionReq. 20 The system willtrack the ambulance’s performance and position.Req. 21 The ambulance’sperformance will be based on the time it takes to arrive at the scene onceallocated and the time to get the patient to the hospital.

Req. 22 The ambulance’sposition will be displayed on the map for the user to monitor.  1.1.12      Monitor DisplayReq. 23 The user monitor will display thefollowing data after s/he has completed the data entry:  ·        Location of the emergency ·        Location of theambulance(s) in route to the emergency.

·        Location of the nearest 3ambulances to the emergency location. ·        Location of the nearest 3hospitals to the emergency location.   1.1.13      Monitoring CompleteReq.

24 The user willclose out the monitoring of an emergency once the allocated ambulance(s)has/have arrived at a hospital.Req. 25 The driver willclick “Emergency Resolved” to close out the monitoring phase of thesystem.Req. 26 The driver willbe returned to the driver home screen when clicking “EmergencyResolved”.Req.

27 The driver can also go to an open emergency request to seeits status. 1.1.14      Information LoggingReq. 28 The system will log all calls and therelated emergency information for future review and statistical purposes.  1.

1.15      EmergencyTransfer/SharingReq. 29 The driver willbe able to transfer the emergency to another driver in case s/he has to log outof the system.Req. 30 The driver willalso be able to share the emergency information with other driver in casehe/she needs help.

1.1.16      Logging OutReq.

31 The driver willlog out of the system by clicking “Log Out”.Req. 32The driver willnot be allowed to log out while currently monitoring an ongoing emergencyunless s/he transferred or shared the emergency with at least one other driver.

 1.2           Non-Functional Requirements 1.2.

1          Usability·        Simple to Operate: The software shouldbe easy to learn and operate; the user should not require special skills ortraining to operate the system.·        Simple design: The user interfaceshould be kept as simple as possible so as not to make the application tooconfusing for the user to understand i.e., user friendly interface.

·        User awareness: User manual andin-build help file will be provided for the user. Tool tip text will also beprovided for quick help.   1.2.

2          Reliability·        The system should be up andrunning 24 X 7 X 365 and should be crash safe during 95% of its runtime. ·        Mean time between failures(MTBF): The MTBF (if any) should not be less than 6 months.·        Mean time to repair (MTTR):In case of a failure that leads to a system outage, the MTTR should not be morethan 2 hours. 1.2.3          Performance·        Short response time: Any page of theapplication should not take more than 4 seconds to load. The load time of theapplication should not be more than 4 seconds.

·        Population Support: The applicationshould be able to support 250 concurrent users without any performancedegradation. 1.2.4          Supportability·        Advanced technologies: As technologyis changing so fast, the system should be able to support new technologies fortracking which will be faster and reliable than the ones present now.

·        GPS: The system should be able tosupport GPS tracking in the future.·        Address location using phonecoordinates: The system should support locating the address, using phonecoordinates of the person making the call. 1.2.5          Implementation·        Programming language: Java and alliedtechnologies should be used for development of the application. ·        Apache’s Tomcat Web-Server should beused to deploy the application.·        MySQL should be used as the database.Business Objects will be used for reports.

                            1.2.6          Packaging The software will also be available online, and anybody authorized by the system administrator can access the system.

 1.2.7          Legal Data from the user should adhere to the rights of data privacy of the user. All the content must be procured through legal channels and there should be no copyright violations.     1.2.

8          Security As the system will be dealing with delicate data, the system should be secure. The data should be stored in a highly secure manner and should be immune from any hacking attempts. 1.2.

9          Scalability The system designed will be optimum for the 250 users. The system should be able to scale up to 500 concurrent users (if there is a need in the future) by installing additional hardware components with no degradation in the performance of the system. 1.2.10       Schedule Constraints The entire system should be up and running in the user’s production environment by 30th June.

 1.2.11       Standards Constraints·        All the documents delivered shouldadhere to the IEEE standards for software engineering

x

Hi!
I'm Dora!

Would you like to get a custom essay? How about receiving a customized one?

Click here