Smart Ambulance

Chapter 2: Software Requirement Specification

(For Object Oriented Approach)

© Faculty of Computing & IT, University of Gujrat 1

Smart Ambulance

2.1 Introduction:
We are going to develop an emergency system for ambulances. Our application will
provide peoples quick services in emergency. In case of accidents or sudden disease
attack (Heart Attack ,Brain Stroke .etc ) our application will provide Rapid emergency
service on just a single button click. Our application will provide rescue services the
accident location on a web interface. Application will provide nearest hospitals locations -
shortest paths and clear roads to ambulances so that they can arrive at their location on
time and save peoples life. Application will also provide video calling from Ambulance
to doctor so in case the ambulance is coming from a far location and the patient condition
is very critical doctor can guide who to treat him in ambulance via video call. Our
Application will provide reporting facility (patient reports) directly from ambulance to
hospital. Our Application will provide a feature to common peoples so that they can deal
with emergency situations.
Existing System
In existing system people have to call rescue service provider . In existing system peoples
are facing many problems . peoples don’t know what to do in case of emergency. There
is a shortage of hospital in villages. Ambulances do not get direction or shortest path to
nearby hospitals. Many people’s dies due to late emergency services.
Organizational Chart

Scope of the System

Smart Ambulance emergency system is based on a mobile application in android and web
application in asp.net. Smart ambulance has divided in different parts according to its
functionality.
1. Rapid Emergency Service

© Faculty of Computing & IT, University of Gujrat 2

Smart Ambulance

2. Rapid Emergency Solutions

3. Nearest Hospital location
4. Shortest path
5. Assistance through video call
6. Reporting
Near about 1.2 billion peoples died in accidents and disease attacks due to late emergency
services. There are many factors behind this problem. We are going to develop an
emergency system so that we can save peoples life by providing them rapid emergency
services. We are going to build an application that is based on a mobile application in
android and web application in asp.net. Our application will provide
8. Rapid Emergency Service on a single button click
9. Near By Hospital locations
10. Near By Hospitals Distance and information
11. Shortest Path to nearby hospital
12. Assistant through video call in emergency
13. Reporting Directly from ambulance to hospital
14. Emergency Solutions for common peoples
Our application smart ambulance is a full solution that will provide rapid emergency
services to the peoples so that we can save people’s lives .Smart ambulance is the need of
the era. Because there are many problems that peoples are facing
6. Don’t know what to do in case of sudden accidents
7. Shortest path to nearby hospitals with their information
8. Assistance in emergency through video call
9. Ambulance to Hospital Reporting
10. Disease (Extreme + Normal) Recovery methods for common peoples
Peoples are facing such problems and smart ambulance is a complete solution for these
problems

Summary of Requirements: (Initial Requirements)

The purposed system must fulfill following requirements as follow:
1. Registration and logins
Smart Ambulance provides registration and login to end users. For using smart
ambulance they have to register them in smart ambulance and then login. Smart
ambulance emergency system provider’s logins and registration functionality to all its end
users

2. Rapid Emergency Service

Our application will provide rapid emergency service on a single button click. For
using this feature the patient have to register him/her self in smart ambulance mobile
application patient/informer module and login .

3. Emergency Solutions
Our application will provide rapid emergency solution to the patients . In rapid
emergency solution there are solutions that how to deal emergency situations in case
of accidents of sudden disease attacks.

© Faculty of Computing & IT, University of Gujrat 3

Smart Ambulance

4. Nearest Hospital Location

Our application will provide nearest hospital location with its information. The
information is provided in Ambulance assistance module of mobile application. User has
to click on nearest hospital location and they get the hospital locations with their
information’s

5. Shortest Path
Our application will provide shortest path to nearest hospital .User has to simply clicks
on shortest path button and he/she will get the shortest path to nearest hospital

6. Assistance through video call

Our application will provide video call functionality .with this doctor can guide patients
directly from hospital to ambulance.

7. Reporting
Our application will provide reporting functionality. With this functionality you can send
patient reports from ambulance to hospital.

2.1.2. Identifying External Entities

 Patient
 Rescue Service provider
 Hospital
 Doctor
 Assistant
 Gps
 Maps

b. Perform Refinement:

 Patient
 Rescue Service provider
 Hospital
 Doctor
 Assistant
 Gps
 Maps

© Faculty of Computing & IT, University of Gujrat 4

Smart Ambulance

2.1.3. Context Level Data Flow Diagram:

© Faculty of Computing & IT, University of Gujrat 5

 Smart Ambulance

2.1.4. Capture "shall" Statements:

Para Initial Requirements

#
1.0 User (patient) shall register himself to the system.
1.0 User (patient) shall login himself to the system.
1.0 User (patient) shall see his information.
1.0 User (patient) shall change his password.

1.0 User (patient) shall create rapid emergency request .

1.0 User (patient) shall see rapid emergency solutions.
1.0 User (patient) shall logout himself to the system.

2.0 User (Rescue service provider) shall register himself to the system.
2.0 User (Rescue Service provider) shall login himself to the system.
2.0 User (Rescue Service provider ) shall see his information.
2.0 User (Rescue Service provider) shall change his password.
2.0 User (Rescue Service provider) shall get rapid emergency request from patient on
web interface on maps.
2.0 User (Rescue Service provider) shall share location with ambulance.
2.0 User (Rescue service provider) shall provider hospital information’s to ambulance if
required.
2.0 User (Rescue service provider) shall provide doctors information in the specific
hospital if required.
2.0 User (Rescue service provider) shall logout himself to the system.

3.0 User (Assistant) shall register himself to the system.

3.0 User (Assistant) shall login himself to the system.

3.0 User (Assistant ) shall see his information.

3.0 User(Assistant) Shall change his password

3.0 User (Assistant ) shall get emergency location from rescue service provider.

3.0 User (Assistant ) shall get nearby hospital location and information

3.0 User (Assistant) shall get shortest path.

3.0 User (Assistant) shall video call to doctor directly from the ambulance.

3.0 User(Assistant) shall send patient reports to doctor .

3.0 User (Assistant) shall logout himself to the system.

4.0 User (Doctor) shall register himself to the system.

© Faculty of Computing & IT, University of Gujrat 6

 Smart Ambulance

4.0 User (Doctor) shall login himself to the system.

4.0 User (Doctor) shall see his information.

4.0 User (Doctor) shall change his password.

4.0 User (Doctor) shall get video call from the ambulance assistant.

4.0 User (Doctor) shall logout himself to the system.

5.0 User (hospital) shall register himself to the system.

5.0 User (hospital) shall login himself to the system..

5.0 User (hospital) shall see his information.

5.0 User (hospital) shall change his password.

5.0 User (hospital shall get patient reports send by ambulance assistant)

5.0 User (hospital )shall print reports

5.0 User (hospital) shall logout himself to the system.

2.1.5. Allocate Requirements:

Para # Initial Requirements Use Case Name
1.0 User (patient) will register himself to the UC_Patient_Registration
system.
1.0 User (patient) will login himself to the UC_Patient_Login
system.
1.0 User (patient) will see his information. UC-Patient_information

1.0 User (patient) will change his password. UC_Patient_Change_Password

1.0 User (patient) will create rapid emergency UC_Rapid_Emergency_Service
request .
1.0 User (patient) will see rapid emergency UC_Emergency_Solutions
solutions.
1.0 User (patient) will logout himself to the UC_Patient_logout
system.
2.0 User (Rescue service provider) will register UC_RSP_Registration
himself to the system.
2.0 User (Rescue Service provider) will login UC_RSP_Login
himself to the system.

2.0 User (Rescue Service provider ) will see his UC_RSP_Informaiton

information.

© Faculty of Computing & IT, University of Gujrat 7

Smart Ambulance

2.0 User (Rescue Service provider) will change UC_RSP_Change_Password

his password.
2.0 User (Rescue Service provider) will get UC_Current_Accident_Locatio
rapid emergency request from patient on n
web interface on maps.
2.0 User (Rescue Service provider) will share UC_Share_Location_With
location with ambulance. _Ambulance
2.0 User (Rescue service provider) will provider UC_Hospital Information
hospital information’s to ambulance if
required.
2.0 User (Rescue service provider) will provide UC_Doctors_Information
doctors information in the specific hospital if
required.
2.0 User (Rescue service provider) will logout UC_RSP_Logout
himself to the system.
2.0 User (Assistant) will register himself to the
UC_Ambulance_Assistant_Regi
system. stration
3.0 User (Assistant) will login himself to the
UC_Ambulance_Assistant_Logi
system. n
3.0 UC_Ambulance_Assistant_Info
User (Assistant ) will see his information.
rmation
3.0 User(Assistant )will change his password UC_Assistant_Change_Passwor
d
3.0 User (Assistant ) will get emergency UC_Current_Emergency_Locati
location from rescue service provider. on

3.0 User (Assistant ) will get nearby hospital UC_Nearest_Hospital_Location

location and information
3.0 User (Assistant) will get shortest path. UC_Shortest_Path

3.0 User (Assistant) will video call to doctor UC_Video_Call_Doctor

directly from the ambulance.
3.0 User(Assistant) shall send patient reports to UC_Send_Patient_Reports
doctor .
3.0 User (Assistant) will logout himself to the UC_Assistant_Logout
system.
4.0 User (Doctor) will register himself to the UC_Doctor_Registration
system.
4.0 User (Doctor) will login himself to the UC_Doctor_Login
system.
4.0 User (Doctor) will see his information. UC_Doctor_Information
4.0 User (Doctor) will change his password. UC_Doctor_ChangePassword
4.0 User (Doctor) will get video call from the UC_Video_Call_Patient

© Faculty of Computing & IT, University of Gujrat 8

Smart Ambulance

ambulance assistant.
4.0 User (Doctor) will logout himself to the UC_Doctor_Logout
system.
5.0 User (hospital) will register himself to the UC_Hospital_Administration_R
system. egistration

5.0 User (hospital) will login himself to the UC_Hospital_Login

system..
5.0 User (hospital) will see his information. UC_Hospital
_Administration_Information
5.0 User (hospital) will change his password. UC_Hospital_Administration_C
hange_Password
5.0 User (hospital) will get patient reports send UC_Get_Reports
by ambulance assistant.
5.0 User (hospital ) will print reports UC_Print_Reports
5.0 User (hospital) will logout himself to the UC_Hospital_Administration_L
system. ogout

2.1.6. Prioritize Requirements:

Para Rank Initial Use Use Case Name
# Requirements Case
ID
1.0 Highest User (patient) UC_1 UC_Rapid_Emergency_Service
will create rapid
emergency
request .
2.0 Highest User (Rescue UC_2 UC_Share_Location_With
Service provider) _Ambulance
will share
location with
ambulance.
3.0 Highest User (Assistant ) UC_3 UC_Nearest_Hospital_Locatio
will get nearby n
hospital location
and information
3.0 Highest User (Assistant) UC_4 UC_Shortest_Path
will get shortest
path.
3.0 Highest User(Assistant) UC-5 UC_Send_Patient_Reports
shall send patient
reports to doctor .

© Faculty of Computing & IT, University of Gujrat 9

Smart Ambulance

1.0 Highest User (patient) UC-6 UC_Patient_Registration

will register
himself to the
system.
1.0 Highest User (patient) UC-7 UC_Patient_Login
will login himself
to the system.
2.0 Highest User (Rescue UC-8 UC_RSP_Registration
service provider)
will register
himself to the
system.
2.0 Highest User (Rescue UC-9 UC_RSP_Login
Service provider)
will login himself
to the system.
3.0 Highest User (Assistant) UC-10 UC_Ambulance_Assistant_Reg
will register istration
himself to the
system.
3.0 Highest User (Assistant) UC-11 UC_Ambulance_Assistant_Log
will login himself in
to the system.
4.0 Highest User (Doctor) UC-12 UC_Doctor_Registration
will register
himself to the
system.
4.0 Highest User (Doctor) UC-13 UC_Doctor_Login
will login himself
to the system.
5.0 Highest User (hospital) UC-14 UC_Hospital_Administration_
will register Registration
himself to the
system.
5.0 Highest User (hospital) UC-15 UC_Hospital_Login
will login himself
to the system..
1.0 Medium User (patient) UC-16 UC-Patient_information
will see his
information.
1.0 Medium User (patient) UC-17 UC_Patient_Change_Password
will change his
password.
2.0 Medium User (Rescue UC-18 UC_RSP_Informaiton
Service provider
) will see his

© Faculty of Computing & IT, University of Gujrat 10

Smart Ambulance

information.
2.0 Medium User (Rescue UC-19 UC_RSP_Change_Password
Service provider)
will change his
password.
3.0 Medium User (Assistant ) UC-20 UC_Ambulance_Assistant_Info
will see his rmation
information.
3.0 Medium User(Assistant UC-21 UC_Assistant_Change_Passwo
)will change his rd
password
4.0 Medium User (Doctor) UC-22 UC_Doctor_Information
will see his
information.
4.0 Medium User (Doctor) UC-23 UC_Doctor_ChangePassword
will change his
password.
5.0 Medium User (hospital) UC-24 UC_Hospital
will see his _Administration_Information
information.
5.0 Medium User (hospital) UC-25 UC_Hospital_Administration_
will change his Change_Password
password.
5.0 Medium User (hospital ) UC-26 UC_Print_Reports
will print reports
1.0 Medium User (patient) UC-27 UC_Emergency_Solutions
will see rapid
emergency
solutions.
4.0 Medium User (Doctor) UC-28 UC_Video_Call_Patient
will get video
call from the
ambulance
assistant.
5.0 Medium User (hospital ) UC-29 UC_Print_Reports
will print reports
1.0 Lowest User (patient) UC-30 UC_Patient_logout
will logout
himself to the
system.
2.0 Lowest User (Rescue UC-31 UC_RSP_Logout
service provider)
will logout
himself to the
system.
3.0 Lowest User (Assistant) UC-32 UC_Assistant_Logout

© Faculty of Computing & IT, University of Gujrat 11

Smart Ambulance

will logout
himself to the
system.
4.0 Lowest User (Doctor) UC-33 UC_Doctor_Logout
will logout
himself to the
system.
5.0 Lowest User (hospital) UC-34 UC_Hospital_Administration_
will logout Logout
himself to the
system.

2.1.7. Requirements Trace-ability Matrix:

Sr# Para System Build Use Case Name Category
# Specification Text
1 1.0 User (patient) will B1 UC_Patient_Registration Business
register himself to
the system.
2 1.0 User (patient) will B1 UC_Patient_Login Business
login himself to the
system.
3 2.0 User (Rescue B1 UC_RSP_Registration Business
service provider)
will register himself
to the system.
5 2.0 User (Rescue B1 UC_RSP_Login Business
Service provider)
will login himself to
the system.
6 3.0 User (Assistant) B1 UC_Ambulance_Assistant_Reg Business
will register himself istration
to the system.
7 3.0 User (Assistant) B1 UC_Ambulance_Assistant_Log Business
will login himself to in
the system.
8 4.0 User (Doctor) will B1 UC_Doctor_Registration Business
register himself to
the system.
9 4.0 User (Doctor) will B1 UC_Doctor_Login Business
login himself to the
system.
10 5.0 User (hospital) will B1 UC_Hospital_Administration_ Business
register himself to Registration
the system.
11 5.0 User (hospital) will B1 UC_Hospital_Login Business
login himself to the

© Faculty of Computing & IT, University of Gujrat 12

Smart Ambulance

system..
12 1.0 User (patient) will B1 UC_Rapid_Emergency_Service
create rapid
emergency request .
13 2.0 User (Rescue B1 UC_Current_Accident_Locatio
Service provider) n
will get rapid
emergency request
from patient on web
interface on maps.
14 2.0 User (Rescue B1 UC_Share_Location_With
Service provider) _Ambulance
will share location
with ambulance.
15 3.0 User (Assistant ) B1 UC_Current_Emergency_Locat
will get emergency ion
location from
rescue service
provider.
16 3.0 User (Assistant ) B1 UC_Nearest_Hospital_Locatio
will get nearby n
hospital location
and information
17 3.0 User (Assistant) B1 UC_Shortest_Path
will get shortest
path.
19 3.0 User (Assistant) B1 UC_Video_Call_Doctor
will video call to
doctor directly from
the ambulance.
20 3.0 User(Assistant) B1 UC_Send_Patient_Reports
shall send patient
reports to doctor .
21 4.0 User (Doctor) will B1 UC_Video_Call_Patient
get video call from
the ambulance
assistant.
22 5.0 User (hospital) will B1 UC_Get_Reports
get patient reports
send by ambulance
assistant.
23 5.0 User (hospital ) will B1 UC_Print_Reports
print reports
24 1.0 User (patient) will B1 UC_Emergency_Solutions
see rapid
emergency

© Faculty of Computing & IT, University of Gujrat 13

Smart Ambulance

solutions.
25 1.0 User (patient) will B1 UC-Patient_information
see his information.
26 1.0 User (patient) will B1 UC_Patient_Change_Password
change his
password.
27 1.0 User (patient) will B1 UC_Patient_logout
logout himself to
the system.
28 2.0 User (Rescue B1 UC_RSP_Informaiton
Service provider )
will see his
information.
29 2.0 User (Rescue B1 UC_RSP_Change_Password
Service provider)
will change his
password.
30 2.0 User (Rescue B1 UC_RSP_Logout
service provider)
will logout himself
to the system.
31 3.0 User (Assistant ) B1 UC_Ambulance_Assistant_Info
will see his rmation
information.
32 3.0 User(Assistant )will B1 UC_Assistant_Change_Passwo
change his rd
password
33 3.0 User (Assistant) B1 UC_Assistant_Logout
will logout himself
to the system.
34 4.0 User (Doctor) will B1 UC_Doctor_Information
see his information.
35 4.0 User (Doctor) will B1 UC_Doctor_ChangePassword
change his
password.
36 5.0 User (hospital) will B1 UC_Hospital
see his information. _Administration_Information
37 5.0 User (hospital) will B1 UC_Hospital_Administration_
change his Change_Password
password.
38 5.0 User (hospital) will B1 UC_Hospital_Administration_
logout himself to Logout
the system.

© Faculty of Computing & IT, University of Gujrat 14

Smart Ambulance

2.1.8. High Level Usecase Diagram:

© Faculty of Computing & IT, University of Gujrat 15

Smart Ambulance

2.1.9. Analysis Level Usecase Diagram:

1.Patient/Informer Usecase Diagram

© Faculty of Computing & IT, University of Gujrat 16

Smart Ambulance

2. Rescue Service Provider Usecase Diagram

© Faculty of Computing & IT, University of Gujrat 17

Smart Ambulance

3. Ambulance Driver/Assistant Usecase Diagram

© Faculty of Computing & IT, University of Gujrat 18

Smart Ambulance

4. Doctor Usecase Diagram

© Faculty of Computing & IT, University of Gujrat 19

Smart Ambulance

5. Hospital Administration Usecase Diagram

© Faculty of Computing & IT, University of Gujrat 20

Smart Ambulance

2.1.10 Usecase Description

Patient/Informer Usecase Description

Brief Description This is patient/informer use case

description. Patient is one of the end user
of smart ambulance emergency system.
There are different functions and features
for patient.
Patient can register himself .Patient can
login. Patient can see his information.
Patient can change his password .Patient
can create rapid emergency request on just
a single button click that will inform
rescue service provider about the current
emergency location .Patient can also use
emergency solutions. Patient can logout.

Preconditions Patient/Informer should download and

install application and register himself to
the application and login.

Basic Flow Patient Registration, Patient login Rapid

Emergency service, Emergency solutions
,Patient Information, Patient Logout

Alternative Flows Patient Registration, Patient Information,

Rapid Emergency Solutions, Rapid
Emergency service, change password,
Patient Logout

Post Conditions Rapid Emergency Request has been

sended, Rapid Emergency
Solutions,Password changed, Logout,

© Faculty of Computing & IT, University of Gujrat 21

Smart Ambulance

Rescue Service Provider Usecase Description

Brief Description This Rescue Service provider use case

description. Rescue Service Provider is of
the end user of smart ambulance
emergency system. There are different
functions and features for Rescue service
provider. Rescue Service Provider can
register himself . Rescue Service Provider
can login. Rescue Service Provider can see
his information. Patient can change his
password .Rescue Service provider get
current accident location that is send by
rapid emergency service to the system.
Rescue service provider share the current
emergency location with ambulance.
Rescue service provider can also share
hospital information to ambulance assistant
(if required ).Rescue Service provider can
also share doctor information to ambulance
assistant (if required).
Preconditions Rescue Service provider should register
him self on smart ambulance web
application. And login.
Basic Flow Rescue Service Provider Registration,
Rescue Service Provider Login, Get Rapid
Emergency request from the patient, Share
emergency location with the ambulance,
Rescue Service Provider Information,
Logout
Alternative Flows Rescue Service Provider Registration,
Rescue Service Provider Login,
Get Rapid Emergency request from the
patient, Share emergency location with the
ambulance, change password
RescueServiceProviderInformation, Logout
Post Conditions Location has been shared with ambulance
,Password changed, Logout

Ambulance Driver/Assistant Usecase Description

Brief Description This is Ambulance Driver/Assistant use

© Faculty of Computing & IT, University of Gujrat 40

Smart Ambulance

case description. Assistant is one of the end

user of smart ambulance emergency
system. There are different functions and
features for Assistant.
Assistant can register himself .Patient can
login. Assistant can see his information.
Patient can change his password. Assistant
get current accident location that is send
Rescue service provider to system.
Assistant can get nearest hospital location
with their information. Assistant can get
shortest path to nearest hospital. Assistant
can get doctor guidelines for patient with
video call. Assistant can send patient
reports directly from ambulance to
hospital.
Preconditions Assistant/Driver should register himself in
the system and login.
Basic Flow Ambulance Assistant Registration,
Ambulance Assistant Login,
Get Rapid Emergency request from
Rescue Service Provider ,Nearest Hospital
location, shortest path , video call doctor,
send patient reports,
Ambulance Assistant Information, Logout
Alternative Flows Ambulance Assistant Registration,
Ambulance Assistant Login,
Get Rapid Emergency request from
Rescue Service Provider ,Nearest Hospital
location, shortest path , video call doctor,
send patient reports, Change Password
Ambulance Assistant Information, Logout
Post Conditions Nearest Hospital location, Shortest path
,Video call with doctor ,Patient reports
send from ambulance to hospital.

Doctor Usecase Diagram

Brief Description This is Doctor use case Description.

Doctor is one of the end user of the smart
ambulance emergency system. There are
different functions and features for doctors.
Doctor can register himself .Doctor can

© Faculty of Computing & IT, University of Gujrat 41

Smart Ambulance

login. Doctor can see his information.

Doctor can change his password. Doctor
can talk to patient on video call and see his
condition and give advise.
Preconditions Doctor should download and install
application and register himself to the
application and login.
Basic Flow Doctor Registration, Doctor Login, Video
Call with patient, Doctor information,
Alternative Flows Doctor Registration, Doctor Login, See his
information, Change Password, Video call
with patient, Logout
Post Conditions Video call with patient,

Hospital Administration Usecase Diagram

Brief Description This is Hospital Administration use case

description. Hospital Administration is one
of the end user of the smart ambulance
system. There are different functions and
features for hospital administration
.Hospital Administration can see his
information, Hospital Administration can
change his password. Hospital can get
patient reports send by Ambulance
Assistant. Hospital Administration can
print reports.
Preconditions Hospital Administration should download
and install application and register himself
to the application and login.
Basic Flow Hospital Administration Registration,
Hospital Administration Login, get patient
reports, Print reports .Logout.
Alternative Flows Hospital Administration Registration,
Hospital Administration Login,See hospital
Administration information ,change
password ,get patient reports, Print reports
.Logout.
Post Conditions Receive Patient Reports send by
ambulance assistant ,Print out Reports

© Faculty of Computing & IT, University of Gujrat 42

Smart Ambulance

Chapter 3: Design Document (For Object Oriented Approach)

© Faculty of Computing & IT, University of Gujrat 43

Smart Ambulance

3.1. Introduction:
Smart Ambulance is an emergency system that will provide rapid emergency solution to
peoples for saving their lives. In this phase we are going toward design of our system
smart ambulance. In this part we will draw different diagram of our system .We are using
object oriented approach. Following are the artifacts that we are going to draw for our
system.
1. Domain Model
2. System Sequence Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. Operation Contracts
6. Design Class Diagram
7. State Transition Diagram
8. Data Model

3.2. Domain Model

© Faculty of Computing & IT, University of Gujrat 44

Smart Ambulance

3.3. System Sequence Diagram

© Faculty of Computing & IT, University of Gujrat 45

Smart Ambulance

© Faculty of Computing & IT, University of Gujrat 46

Smart Ambulance

Sequence Diagrams by Actors

1. Patient Sequence Diagram

© Faculty of Computing & IT, University of Gujrat 47

Smart Ambulance

2. Ambulance Assistant/Driver Sequence Diagram

3. Doctor Sequence Diagram

4. Rescue Service Provide Sequence Diagram

© Faculty of Computing & IT, University of Gujrat 48

Smart Ambulance

5. Hospital Administration Sequence Diagram

© Faculty of Computing & IT, University of Gujrat 49

Smart Ambulance

3.5. Collaboration Diagram

3.6. Operation Contracts

1. Operation Contract
Name: Registration/Login
Responsibilities: Registration for using app and login for security and user account
Cross Reference: use cases (Patient Registration, Patient Login )
Precondition: Download /Install and run application

© Faculty of Computing & IT, University of Gujrat 50

Smart Ambulance

Post conditions: user home screen

2. Operation Contract
Name: Rapid Emergency Service
Responsibilities: Share Smart Phone location with rescue service provider
Cross Reference: use cases (rapid emergency service)
Precondition: Register/login yourself in patient/informer account
Post condition: Current location of smart phone is shared with rescue service provider

3. Operation Contract
Name: Nearby hospital location and information
Responsibilities: nearest hospital location using gps and maps
Cross Reference: using smart phone gps(Global Positioning System), and maps
Precondition: get the accident location from rescue service provider
Post condition: Nearest Hospital location with their information

4. Operation Contract
Name: Shortest Path
Responsibilities: Shortest path to nearby hospital
Cross Reference: use case (shortest path)
Precondition: Get the accident location from rescue service provider
Post condition: Show the shortest path to nearby hospital

5. Operation Contract
Name: Assistance through video call
Responsibilities: Video call to doctor to take advice for the patient
Cross Reference: use case (video call doctor)
Precondition: get the accident location from rescue service provider
Post condition: Video calling with doctor

6. Operation Contract
Name: Reporting
Responsibilities: Create reports about patient conditions and send them directly from
ambulance to hospital.
Cross Reference: use case(send patient reports)
Precondition: get the accident location from rescue service provider.
Post condition: show reports , print reports

© Faculty of Computing & IT, University of Gujrat 51

Smart Ambulance

3.7. Design Class Diagram

© Faculty of Computing & IT, University of Gujrat 52

Smart Ambulance

3.8. State chart diagram

© Faculty of Computing & IT, University of Gujrat 53

Smart Ambulance

3.9. Data Model

© Faculty of Computing & IT, University of Gujrat 54

Smart Ambulance

© Faculty of Computing & IT, University of Gujrat 55