Final Project Report

AMBULANCE BOOKING SYSTEM

Project Supervisor
Asif Hussain

Submitted By

S240262570

Muhammad Bilal Yousaf

BC200405410

Software Projects & Research Section,

Department of Computer Sciences,
Virtual University of Pakistan
 CERTIFICATE
This is to certify that Muhammad Bilal Yousaf (BC200405410) have
worked on and completed their Software Project at Software &
Research Projects Section, Department of Computer Sciences, Virtual
University of Pakistan in partial fulfillment of the requirement for the
degree of BS in Computer Sciences under my guidance and
supervision.

In our opinion, it is satisfactory and up to the mark and therefore

fulfills the requirements of BS in Computer Sciences.

Supervisor / Internal Examiner

Asif Hussain
Supervisor,
Software Projects & Research Section,
Department of Computer Sciences
Virtual University of Pakistan

___________________
(Signature)

External Examiner/Subject Specialist

<<External Supervisor Name>>

___________________
(Signature)

Accepted By:

_____________
(For office use)
 EXORDIUM

In the name of Allah, the Compassionate,

the Merciful.

Praise be to Allah, Lord of Creation,

The Compassionate, the Merciful,
King of Judgment-day!

You alone we worship, and to You alone

we pray for help,
Guide us to the straight path

The path of those who You have favored,

Not of those who have incurred Your

wrath,
Nor of those who have gone astray.
 DEDICATION

IN THE NAME OF ALLAH THE MOST BENIFICIENT THE

MERCIFUL

I dedicate this Project to my beloved

Father & Teachers

And

To the Loving memory of my Mother

And also

To my brothers & sisters.

You have successfully made me the person I am becoming

You will always be remembered.

 ACKNOWLEDGEMENT

Foremost, I am highly grateful to Allah for His blessing that continue to

flow into my life, and because of You, I made this through against all
odds.

With a great pleasure I would like to acknowledge the support,

assistances and contribution made by individuals from the beginning of
the Project, providing me access, data and information, to the writing
process until the completion of this project.

First of all, I want to give thanks to our project supervisors Asif Hussain
for the access and assistance in order to make my project possible.

Second I would like to thank all the Mater program staff, thank you all
for the assistance and constructive discussions we had during the entire
courses
 PREFACE

This project report has been prepared in fulfillment of the requirements

for the BS in Computer Science in the academic year 2023-2024.

For preparing of the project report, I have closely studied the School
Automation System of certain compounds to get the knowledge of the
data requirements that will be used successfully to protect any entrance
breaches.

I have also studied the software that was required for this project coding
like, PHP and databases.

This project started with to final coding I which have given me the ability
to understand the concept of programming and move me forward
smoothly.

I am very thankful to my supervisors who have helped me to complete

this project and I really appreciate all his efforts and support.

I am also very thankful to Virtual University, Pakistan and all the staff.
 TABLE OF CONTENTS

CHAPTER NO. 1
GATHERING & ANALYZING INFO............................................9

1.1 INTRODUCTION:..........................................................................10

1.2 PURPOSE:..................................................................................10

1.3 SCOPE OF PROJECT:....................................................................10

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS.................................11

1.5 PROJECT REQUIREMENTS..............................................................11

1.5.1 Functional Requirements:.................................................11

1.5.2 Non-Functional Requirements:.........................................11

1.6 USE CASES AND USAGE SCENARIOS:..............................................14

1.6.1 Use Case Diagram:...........................................................14

1.6.2 Usage Scenarios:..............................................................15

1.7 DEVELOPMENT METHODOLOGY:.....................................................18

1.7.1 Chosen Methodology:.......................................................18

1.7.2 Reasons for Chosen Methodology:...................................18

1.7.3 Work Plan (Gantt Chart):..................................................21

1.7.4 Project Schedule (Submission Calendar):.........................22

CHAPTER NO. 2
DESIGNING THE PROJECT....................................................23

2.1 INTRODUCTION:..........................................................................24

2.2 PURPOSE:..................................................................................24
 2.3 SCOPE:.....................................................................................24

2.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS:................................24

2.5 ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)............24

2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS:........................................26

2.7 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM:..........................31

2.8 DATABASE MODEL (DATABASE DIAGRAM):......................................31

2.9 GRAPHICAL USER INTERFACES:......................................................32

CHAPTER 3
DEVELOPMENT...................................................................35

3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)...............................36

 Chapter 1
Gathering & Analyzing Info
1.1 Introduction:
My project is “Ambulance Booking System”.
Medical emergencies often require immediate action, and
timely transportation to a hospital can mean the difference between
life and death. The Abundance Booking System (ABS) is a web-
based application designed to streamline the process of booking
ambulances during critical situations. By enabling users to register
and quickly access services, ABS ensures that patients are
transported efficiently to nearby hospitals, even during challenging
times such as peak traffic hours or late at night.
This system integrates key features such as personalized
recommendations based on the patient’s condition, a list of nearby
hospitals and specialists, and the ability to manage transportation
details. It also allows administrators to monitor operations, generate
detailed reports, and enhance service efficiency. With ABS, both
users and service providers can benefit from a more organized and
responsive approach to emergency healthcare logistics.

1.2 Purpose:
The purpose of the project is to provide an intuitive platform
where users can register, log in, and book ambulances efficiently. The
system ensures seamless integration of user data, ambulance details,
and hospital information while offering personalized
recommendations based on patient conditions. It also enables admins
to manage operations and generate reports for better decision-
making. information.

1.3 Scope of Project:

Ambulance Booking System (ABS) is designed to significantly
enhance emergency medical transport services by streamlining the
booking process for ambulances. The basic scope of ABS includes
several basic functions aimed at ensuring rapid and efficient patient
transport in critical situations. Users will have the ability to register
on the platform, creating a secure personal profile that they can
update as needed. This registration and profile management system
ensures that user data is current and easily accessible.
ABS has a robust login system for both users and administrators,
protecting personal and sensitive information. Once logged in, users
can book ambulance services by specifying pickup location,
destination hospital, date and time. During the booking process, the
system will present a list of the nearest hospitals, allowing users to
make informed decisions based on proximity and the patient's
medical needs. This functionality is especially important during peak
hours and at night when emergency response can be more difficult.
Additionally, the system allows users to update transportation details
as per any changes in the emergency situation. Users can also enter
a patient's condition, including the type of injury or illness, enabling
ABS to recommend the most appropriate hospital based on the
patient's condition. It ensures that patients receive timely and
specialized medical care.
ABS also includes comprehensive data management features, storing
detailed information about ambulances, including their size, number,
and availability, as well as driver data. This helps in effective delivery
and allocation of resources. Additionally, the system maintains a
directory of specialist doctors, detailing their locations and duty
hours, so that patients can be routed to appropriate medical
specialists.
Administrators benefit from the ability to generate various reports,
such as weekly, monthly, and regional transportation statistics. These
reports provide valuable insights for system performance analysis
and resource management, with the ultimate goal of improving the
overall efficiency of emergency medical services and ensuring that
patients receive the best possible care in the shortest time.

1.4 Definitions, Acronyms and Abbreviations

Terms Definition
Web
Ambulance Booking System
Programming/System
ABS Ambulance Booking System
SRS Software Requirement Specifications
VU Virtual University of Pakistan
These are the documents prepared during
Deliverables
development life cycle of the SW project
GUI Graphical User Interface
DMC Detailed Marks Certificate
mySql A type of database management system
PW Password
SW Software

1.5 Project Requirements

1.5.1 Functional Requirements:

The Abundance Booking System (ABS) aims to streamline the

process of booking ambulances during emergencies. The following
are detailed functional requirements for the system:

1. User Registration:
 Users must be able to register themselves by providing
necessary personal details such as name, contact
information, and address.
 2. Profile Management:
 Users should be able to edit and update their profiles,
ensuring their information is accurate and up-to-date.

3. Secure Login:
 There must be a secure login process for users and
administrators to access the application, ensuring data
security and privacy.

4. Ambulance Booking:
 Users must be able to book an ambulance by providing
details such as the pick-up point, destination (hospital
name), date, and time.
 While booking, users should be provided with a list of the
nearest hospitals to choose from.

5. Edit/Update Transportation Details:

 Users should be able to edit and update their transportation
details, such as changing the pick-up point or destination.

6. Patient Status Input:

 Users should be able to specify the patient’s status, including
type of injury or disease.
 The system should recommend the nearest hospital based on
the patient’s condition, ensuring appropriate medical care.

7. Specialist Doctors Information:

 The system should maintain a list of specialist doctors,
including their locations and availability (duty times).
 This information helps in directing patients to the right medical
experts promptly.

8. Administrative Reporting:
 Administrators should be able to generate various reports, such
as weekly transportation reports, monthly transportation
reports, and area-wise transportation reports.
 These reports aid in analyzing system performance and
resource management.

9. Ambulance and Driver Data Management:

 The system should store detailed information about
ambulances, including their size, number, and availability.
 It should also maintain data about ambulance drivers, ensuring
efficient dispatch and management of resources.

1.5.2 Non-Functional Requirements:

A Non-Functional Requirement (NFR) defines the quality
attribute of a software system. They judge the software system
based on Performance, Usability, Maintainability, Portability and
 other non-functional standards that are critical to the success of
the software system. These are also called quality attributes.

 Performance:
Performance requirements concern the speed of operation of a
system. The non-functional requirements should identify those
software functions that have constraint on their performance.
 Maintainability:
Maintainability requirements may cover diverse levels of
documentation, such as system documentation, as well as test
documentation, e.g. which test cases and test plans will
accompany the system.
 Usability:
It is an easy way for a user to learn to operate. It is well-formed
GUI.
 Portability:
Portability specifies the ease with which the software can be
installed on all necessary platforms, and the platforms on which it
is expected to run.
 Reliability:
Reliability is the ability of a system to perform its required
functions under specific period of time.
 Time:
The project speed is very high. Every task takes low time for
completion.
 User-Friendly Interfaces:
All interfaces should have intuitive design and easy navigation,
ensuring accessibility for all users (teacher/Staff, student and
parent).
 Validation Checks:
Implement validation checks across all entry, update, delete,
and search interfaces to ensure data integrity and accuracy.
1.6 Use Cases and Usage Scenarios:
1.6.1 Use Case Diagram:
A Use Case Diagram visually represents the interactions
between users (actors) and a system, highlighting the system's
functionalities (use cases) within its defined boundaries. It shows
how actors interact with specific use cases through associations
and may include relationships like "include" for mandatory actions
and "extend" for optional behaviors. This diagram is used to
capture system requirements, communicate functionality to
stakeholders, and guide the system's design by focusing on what
the system should do, not how it does it.

Figure 1 (Use Case)

1.6.2 Usage Scenarios:
Usage scenarios outline how a product, service, or technology
is applied to meet specific needs or solve problems in real-world
contexts. They highlight key users, their goals, and the solution’s
impact.
Use Case
User Registration
Title:
Use Case ID UC-01
Actions Enter personal details - Submit form
Users register by providing name, contact
Description
information, and address.
Alternative
None
Paths
Pre-
User has not registered previously.
Conditions
Post-
User account created and user is logged in.
Conditions
Author BC200405410
Exceptions -User already registered - Missing required details

Use Case Secure Login

Title:
Use Case ID UC-03
Actions Enter username and password - Authenticate
Description Users and admins securely log into the system.
Alternative
Paths Forgot password process
Pre-
Conditions User is registered.
Post-
Conditions User or admin is logged in.
Author BC200405410
Exceptions Incorrect credentials - Account locked

Use Case
Ambulance Booking
Title:
Use Case ID UC-04
Enter pick-up point, destination, date, and time -
Actions Select hospital - Confirm booking
Users book an ambulance specifying all
Description necessary details.
Alternative - Hospital not available - Retry booking with
Paths different hospital
Pre-
Conditions User is logged in.
Post-
Conditions Booking confirmed and details saved.
Author BC200405410
Exceptions No hospitals available - Missing booking details
Use Case ID UC-04
Use Case
Edit/Update Transportation Details
Title:
Use Case ID UC-05
- Select booking- Edit pick-up point or destination-
Actions
Save changes
Users modify transportation details of an existing
Description
booking.
Alternative
None
Paths
Pre-
User has a confirmed booking.
Conditions
Post-
Transportation details updated.
Conditions
Author BC200405410
Exceptions Booking not found - Unauthorized access

Use Case
Patient Status Input
Title:
Use Case ID UC-07
Actions - Search for specialists - View details
Users and admins access information about
Description
specialist doctors.
Alternative
None
Paths
Pre-
System has specialist data.
Conditions
Post-
Specialist information displayed.
Conditions
Author BC200405410
Exceptions No specialists available

Use Case
Specialist Doctor Information
Title:
Use Case ID UC-07
Actions - Search for specialists - View details
Users and admins access information about
Description
specialist doctors.
Alternative
None
Paths
Pre-
System has specialist data.
Conditions
Post- Specialist information displayed.
Conditions
Author BC200405410
Exceptions No specialists available

Use Case
Administrative Reporting
Title:
Use Case ID UC-08
Actions -Select report type - Generate report
Description Admins create transportation reports.
Alternative
Paths None
Pre-
Conditions Admin is logged in.
Post-
Conditions Report generated and displayed.
Author BC200405410
No data available for report - Unauthorized
Exceptions access

Use Case
Ambulance and Driver Data Management
Title:
Use Case ID UC-09
Add or update ambulance details - Add or update
Actions driver details
Admins manage ambulance and driver
Description information.
Alternative
Paths None
Pre-
Conditions Admin is logged in.
Post-
Conditions Ambulance and driver details updated.
Author BC200405410
Exceptions Missing details - Unauthorized access
1.7 Development Methodology:
1.7.1 Chosen Methodology:
Water Fall Model and Spiral Model are two models which are
combined to each other and make VU Process Model. It is also called
hybrid approach of system development. This Process model takes
advantages and minimizes the drawbacks of both approaches. This is
a linear model to solve many problems.

1.7.2 Reasons for Chosen Methodology:

Following are the basic reasons for choosing VU Process Model for our
project.

 Testing is inherent to every phase

 It is an enforced disciplined approach because to having stage
development cycle and every phase has defined start and end
date.
 It is documentation driven which means documentation is
produced at every stage.
 Emphasis on requirement and design before writing code
ensure minimal wastage of time and efforts.
 Our project is divided into different phases which we have to
complete in sequence and submit to our supervisor.
 If some mistakes are found than he suggests us to correct
those mistakes and improve our project.
 This process will be adopted due to its spiral nature.
VU Process Model:
VU PROCESS MODEL The adopted methodology is VU
Process Model which is a combination of Waterfall and Spiral Model.
 Figure 2 (VU Process Model)
STRUCTURE OF VU PROCESS MODEL:
It has four phases and which are Gathering and analyzing
requirement, planning, analysis and design, development and final
report

 Gathering & Analyzing Requirement:

In this phase we gathered information regarding functional and
non- functional requirements of our Project and also prepared Use
case diagrams to understand Actors and Uses cases of project
and develop usages scenario diagrams to understand all those
situations which will come across while using this application.
 Planning Phase:
In this phase we adopted methodology to complete the project
different Phase also prepared the Schedule using Gant chart to
know which phase will be completed in how many days.
 Analysis and Design Phase:
In this phase consist of two design documents. In Design
document 1, we will develop the Activity Diagram, Sequence
diagrams, Collaboration Diagram, Architecture Design Diagram
and DFD diagram. And Design document II we develop the Object
model, Class diagram, interface design, database design, test
cases, Deployment diagram and Component diagram.

 Development & Final Project Report:

In this phase we will write necessary code for implementation
of our application. Coding will be completed in iterations.

Spiral Model:
The spiral model is a risk-driven process model generator for
software projects. Based on the unique risk patterns of a given
project, the spiral model guides a team to adopt elements of one or
more process models, such as waterfall. It combines the idea of
iterative development with the systematic, controlled aspects of the
waterfall model. It is a combination of iterative development process
model and sequential linear development model i.e. the waterfall
model with a very high emphasis on risk analysis. It allows
incremental releases of the product or incremental refinement
through each iteration around the spiral

Diagram of Spiral Model:

Figure 3 (Spiral Model)

Waterfall Model:
The Waterfall Model was the first Process Model to be introduced. It is
also referred to as a linear-sequential life cycle model. It illustrates
the software development process in a linear sequential flow. It is
very simple to understand and use. In a waterfall model, each phase
must be completed before the next phase can begin and there is no
overlapping in the phases. The Waterfall model is the earliest SDLC
approach that was used for software development.
 This means that any phase in the development process begins only if
the previous phase is complete. In this waterfall model, the phases
do not overlap.

The waterfall model is a sequential (non-iterative) design process,

used in software development processes, in which progress is seen
as flowing steadily downwards (like a waterfall) through the phases of
conception, initiation, analysis, design,
construction, testing, production/implementation and maintenance.
Despite the development of new software development process
models, the Waterfall method is still the dominant process model
with over a third of software developers still using it.

This model is depicted in the following diagram.

Requirement Analysis
and Definition

System and Software

Design

Implementation and
Unit Testing

Integration and system

testing

Operation and
Maintenance
Figure 4 (Waterfall Model)

1.7.3 Work Plan (Gantt Chart):

The work plan is a document that consulting firms use to
organize a project. It outlines the plan by which the company plans to
complete a quality project within a given amount of time and in
compliance with a set budget.

Gantt charts are useful tools for planning and scheduling

projects. They allow you to assess how long a project should take,
determine the resources needed and layout the order in which tasks
need to be carried out. They are useful in managing the
dependencies between tasks.
 Figure 5 (Gantt Chart)

1.7.4 Project Schedule (Submission Calendar):

Figure 6 (Submission Calendar)

 2 Chapter 2
2.Designing the project

2.1 Introduction:
The document provides documentation which will be used to aid in
system development. The document provides the details of how the
software should be built. The design document includes Entity
Relationship Diagram (ERD), Sequence Diagrams, Architecture
Design Diagrams, Class Diagram, Database Design, Interface design
and Test Cases and other supporting requirement information.

2.2 Purpose:
The purpose of software design document is to provide a description
of design of system fully enough to allow for software development to
proceed with an understanding of what is to be built and how it is
expected to build. The software design document provides
information necessary to provide description of the details for the
software and system to be built.

2.3 Scope:
The analysis and design phase in software development process is
very important as it provide better management and understanding
of the requirements. Additionally, system scope, verification and
validation are done in analysis and design. Software quality
assurance related planning is done in this phase of project.

2.4 Definitions, Acronyms and Abbreviations:

Terms Definition
Web
Ambulance Booking System
Programming/System
ABS Ambulance Booking System
SRS Software Requirement Specifications
VU Virtual University of Pakistan
These are the documents prepared
Deliverables during development life cycle of the SW
project
GUI Graphical User Interface
mySql A type of database management system
PW Password
SW Software

2.5 Architectural Representation (Architecture

Diagram)
An architecture diagram is a visual representation of the
components, relationships, and responsibilities within a software
system. It shows the big picture of a software project and outlines the
architecture that has been chosen.
Figure 1 (Architecture Diagram)
2.6 Dynamic Model: Sequence Diagrams:
Sequence diagrams are interaction diagrams that show what
messages are sent and when between objects in a system. They are
organized by time from top to bottom and by objects from left to
right. They are used to represent all the possible interactions in a
single-use case. They help to understand how a system achieves a
specific goal or function.

Figure 2 (Secure Login)

Figure 3 (User Registration)

Figure 4 (Manage Profile)

 Figure 5 (Ambulance Booking)

Figure 6 (Edit/Update Transportation)

 Figure 7 (Patient Status)

Figure 8 (Specialist Doctors Information)

Figure 9 (Administration Reporting)

Figure 10 (Manage Ambulance and Driver Data)
2.7 Object Model/Logical Model: Class Diagram:
A class diagram is a visual representation of the objects,
attributes, and methods in a system. To create a class diagram, you
need to identify the classes and their relationships, and use symbols
and lines to show them.

Figure 11 (Class Diagram)

2.8 Database Model (Database Diagram):

In a database model, you define the structure of your database,
including tables, columns, relationships, and constraints.

Figure 12 (Database Model Diagram)

2.9 Graphical User Interfaces:

Figure 13

Figure 14
Figure 15

Figure 16
Figure 17

Figure 18
 3 Chapter 3
Development

3.1 Development plan (Architecture Diagram)

Figure 1 (Architecture Diagram)

REFERENCES
References
In order to develop our system, we have referenced a number of
different systems. We have taken help from these systems for
removing confusions and to make our system more useful. However,
the major sources were:
 Software Engineering, I and II (by Fakhar Lodhi)
This book is studied for different types of testing techniques
and design models and Software Engineering Handouts Virtual
University of Pakistan.
 W3 School (https://www.w3schools.com)
This website help me in learning HTML, CSS, PHP, JQUERY,
BOOTSTRAP.
 Modern Database Management (by Jeffrey A Hoffer)
To understand the different quarries of SQL server for using in
our project.
 Principles of Distributed Database System (by M. Tamer
Ozsu and Patric alduriez )
We learn different database techniques making database tables
and arranging them, form this book.
 Modern Database Systems (By Date C.J)
To understand database concepts and managing it using
different techniques.

APPENDIX
Section 1 Gathering & Analyzing Info

Section 2 Designing the Project

Section 3 Development