TABLE OF CONTENT

1. Project Definition (Overview, Purpose, Scope)

2. Functional and Non-Functional Requirements
3 Use case diagram
4 Activity diagram

 Introduction:
 Project Overview:
The Ambulance Service Management System (ASMS) is a web and
mobile-based platform that helps people quickly call an ambulance in case of
emergency. The system connects customers, drivers, and administrators at
one place. Customers can call and track ambulance, drivers can update their
availability and accept request, and administrators can manage all the
operations like assigning ambulances, monitoring drivers, and maintaining
records.
 Project Purpose:
The Ambulance Service Management System provides a fast and
reliable way for customers to call ambulance during an emergency, track
them in real time, and help administrators and drivers manage services
efficiently.
 Project Scope:
The purpose of ASMS is to provide fast, reliable, and organized
ambulance services during emergencies by reducing response time,
improving communication, and ensuring effective management of resources.

 System Specific Requirement:

2.1. Functional Requirement: -
Functional requirements define the Fundamental action that the
system must perform.
Module 1 : User Management

FR1 The system shall allow Customers and Drivers Registration, Profile
to register a new account and update their
profile information.

FR2 The system shall allow all users to log in using Login, Password Recovery
username and password, recover forgotten
passwords, and change existing passwords.

Module 2 : Admin Management

FRN DESCRIPTION Page

The admin shall be able to view details of Admin Dashboard

FR1 Ambulances, Drivers, and Customers with
filter and search options.

The admin shall be able to manage Driver

FR2 availability and operational status. Driver Management

The admin shall be able to add, update, and Ambulance Management

FR3 manage ambulance details and types.

The admin shall able to view records of View Records

FR4 trips, drivers.
Module 3 : Customer Services

FRN DESCRIPTION Page

The Customer shall be able to book an Book Ambulance

FR1 ambulance and select the type of
ambulance required.

The Customer shall be able to confirm a

FR2 booking after viewing ETA, ambulance Booking Confirmation
details, and estimated cost.

The system shall automatically share the

FR3 Customer’s location with nearby Drivers Location Sharing
during booking.
The Customer shall be able to track the live
FR4 location of the ambulance until it arrives. Live Tracking

The Customer shall be able to provide

FR5 feedback and rating after service Feedback/Rating
completion.
Module 4 : Driver Services

FRN DESCRIPTION Page

The Driver shall be able to toggle their Driver Availability

FR1 availability status (Available/Unavailable).

The Driver shall be able to receive

FR2 ambulance booking requests with trip Booking Requests
details.

The Driver shall be able to update trip status

FR3 (Accepted, On-Trip, Completed). Trip Status

The Driver shall be able to report vehicle

FR4 breakdowns or issues directly to Admin. Breakdown Report

Module 5: System Features

FRN DESCRIPTION Page

The system shall stop sharing the Customer’s Location Privacy

FR1 location once the trip starts to ensure privacy.

The system shall update the live location of the

FR2 ambulance during active trips. Live Location

The system shall store only essential trip and

FR3 contact details, ensuring no sensitive medical Data Privacy
data is saved.
 Non-Functional Requirement:

NFRN DESCRIPTION Category

The system shall process ambulance Performance

NFR1 booking requests and respond within 5
seconds under normal load.

The system shall support at least 1000

NFR2 concurrent users (customers, drivers, and Scalability
admins) without performance
degradation.
The system shall be available 24/7 with at
NFR3 least 99% uptime, ensuring emergency Availability
access at all times.
The system shall ensure successful
NFR4 ambulance assignment in at least 95% of Reliability
requests, with fallback mechanisms when
drivers are unavailable.
All sensitive data (passwords, personal
NFR5 info, trip details) shall be stored securely Security
using encryption (e.g., AES/SSL), and
access shall be role-based (Admin, Driver,
Customer).
The system shall provide a simple and
NFR6 intuitive user interface on both web and Usability
mobile platforms, accessible to users with
minimal training.
The system shall be designed with
NFR7 modular architecture, enabling easy Maintainability
updates and bug fixes without affecting
other modules.
The system shall store only essential trip
NFR8 and contact details (no medical records), Data Privacy
and location sharing shall stop once the
trip starts.
 Push notifications and SMS alerts shall be
NFR9 delivered to Customers and Drivers within Notification Delivery
10 seconds of event triggers (booking,
acceptance, arrival).

Use case: -
Activity diagram: -

1. User login:
2. User Registration: -
3. Profile Update Activity Diagram: -
4. Ambulance Booking & Confirmation -Customer (ASMS)
5. Admin Management: -
6. Driver Handling: -
7. Feedback & Rating
8. System-Level Management: -
  Database dictionary: -

1. Table Name: Users

Sr. No Field Name Data Type Size Constraints Description

1 INT - Primary Key Unique ID for

each user
User id

2 Name VARCHAR 100 Not Null

Full name of
the user

3 Email VARCHAR 100 Unique, Not User email

Null (used for
login)

4 Password VARCHAR 255 Not Null Encrypted

password

5 Role ENUM - Not Null Defines type

(Admin,
Customer,
Driver)

6 Contact No VARCHAR 15 - User’s mobile

number

7 Address VARCHAR 255 - User’s

address

8 Created At DATETIME - Not Null

Account
creation date
 2. Table Name: Ambulances

Sr. No Field Name Data Type Size Constraints Description

1 INT - Primary Key Unique ID for

each
ambulance
AmbulanceId

2 VehicleNumber VARCHAR 50 Unique

Vehicle
registration
number

3 Type ENUM - Not Null Type of

ambulance
(Basic, ICU,
Cardiac)

4 Status ENUM - Not Null Current status

(Available,
OnTrip,
Maintenance)

5 LocationLat DECIMAL (10,6) - Current

latitude

6 LocationLong DECIMAL (10,6) - Current

longitude
 3. Table Name: Drivers

Sr. No Field Name Data Type Size Constraints Description

1 INT -

DriverID Primary Key Unique ID for driver

2 UserID INT - Foreign key

References
Users(Userid)

3 LicenseNumber VARCHAR 50 Unique

Driver’s license
number

4 AvailabilityStatus ENUM -

Not Null Availability

(Available/Unavailable)
 4. Table Name: Bookings

Sr. Field Name Data Type Size Constraints Description

No

1 BokingID INT - Primary Unique booking ID

Key

2 CustomerID INT - Foreign Key References

Users(UserID)

3 AmbulanceID INT - Foreign Key References

Ambulances(AmbulanceID)

4 DriverID INT Foreign Key References

Drivers(Driverid)

5 PickupLocation VARCHAR 255 Not Null Pickup

address/location

6 DropLocation VARCHAR 255 - Drop

address/location

7 ETA VARCHAR 50 - Estimated arrival

time

8 PriceEstimate DECIMAL (10,2) - Estimated trip cost

9 Status ENUM - Not Null Booking status

(Pending,
Confirmed,
Completed,
Cancelled)
10 CreatedAt DATETIME - Not Null Booking date/time

5. Table Name: Feedback

Sr. No Field Name Data Type Size Constraints Description

1 FeedbackID INT - Primary Key Unique feedback

ID

2 BookingID INT - Foreign Key References

Bookings(BookingID)

3 CustomerID INT - Foreign Key References

Users(UserID)

4 Rating INT 1 Not Null Customer rating

(1–5)

5 Comments VARCHAR 255 - Customer

feedback text

6 Date DATETIME - Not Null Feedback date