online ambulance service project presentation slides. emergency ambulance service for final year project document presentation.

1. SEMESTER PROJECT
PRESENTATION
SOFTWARE ENGINEERING
TOPIC : Emergency Ambulance System
Group Members.
Anwar Hussain(31579)
Amina khalid(31028)
Instructor :Sir Muhamad Khateeb khan

2. Introduction:- Why Does Desperately
Need an Ambulance App?
 While the technology is in favour of patients who might need these emergency medical
services at any point in time, unfortunately, the circumstances are not!
. The Emergency Ambulance is one of the vital modes of transport in the world. These days we
see ambulances for long and short distance travel, which provides a health care services save
lives. The management of the Emergency Ambulance database also has a vital role in the smooth
running of this system.

3. PURPOSE
By developing this software, we can sort our life and have the following benefits.
• Main goal is to help the patient to get fast help online portal.
• Get fast help
 correct destination Because we have map tracker in this app.
 Make Ambulances Available for Emergency
 Choose Ambulance near to you
 Hospital information
 Time in and opportunity

4. FUNCTIONAL AND NON –FUNCTIONAL REQ
 Receiving Incident information from the caller.
 Locating nearest ambulance..
 Allocating the ambulance to the incident.
 Logging and Reporting of incidents
 Finding the route to the incident .
External Systems:
GPS System

5. Non –Functional:
Performance Requirements:
The performance of the System depends Upon the Availability of a fast and Steady Internet Connection with least speed of
128 Kbps.
Safety Requirements
 Security
Security requirements are particularly significant in defense systems and database systems. They place restrictions on the use of certain
commands, control access to Computer Engineering.
 Fault Tolerance
Data should not become corrupted in case of system crash or power failure.
 Security Requirements
The files and databases in which the information regarding Users and Transactions should be secured against malicious deformations. The system use
SSL (secured socket layer) in all transactions that include any confidential customer information. The system must automatically log out all customers after
a period of inactivity. The system should not leave any cookies on the customer’s computer containing the user’s password.

6.  Reliability
The reliability of the overall project depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the
database which is continuously maintained and updated to reflect the most
recent changes. Also the system will be functioning inside a container. Thus the
overall stability of the system depends on the stability of container and its
underlying operating system.
 Availability
The system should be available at all times, meaning the user can access it using
a web browser, only restricted by the down time of the server on which the
system runs. A customer friendly system which is in access of people around the
world should work 24 hours. In case of a of a hardware failure or database
corruption, a replacement page will be shown.
 Maintainability
A commercial database is used for maintaining the database and the application
server takes care of the site. In case of a failure, a re-initialization of the project
will be done. Also the software design is being done with modularity in mind so
that maintainability can be done efficiently.

7. STAKE HOLDERS
Analysis
 Internal stake holder requirements are on priority based.
 The application have five groups into three broad categories of
stakeholders: customers, actors, and owners. 'Customers' in this context are
patients, families and carers. 'Actors' are paramedics and volunteer
ambulance officers, and ambulance service executives.

8. CONSTRAINTS
 Software engineering with proper documentation of a project
 Use HTML CSS JS AND php with sql for secure website
 For app use java for android and swift for iOS
 Development team having expertise in all these areas
 Agile process model .

9. Software

10. Thank you