Main Index

Download as pdf or txt
Download as pdf or txt
You are on page 1of 8

Acknowledgement

First and foremost, we would like to thank our Mentor, Ms. BANKHELE P.K. for
his guidance and support. We will forever remain grateful for the constant support and
guidance extended by Mentor, in making this report. Through our many discussions, he
helped us to form and solidify ideas. The invaluable discussions we had with him, the
penetrating question he has put us and the constant motivation, has all led to the
development of this project.
We wish to express our sincere thanks to our Principal Mr. POKHARKAR S. R.,
Head of Department Mr. V. V. JADHAV, Project Coordinator Mr. V. V. JADHAV
and also grateful thanks to our departmental staff members for their support.
We would also like to thank to our friends for listening to our ideas, asking questions
and providing feedback and suggestions for improving our ideas.

Lohote Sahil Shankar


Dawkhar Amey Chetan
Thorve Avishkar Shrikrushna
Padwal Siddharth Ashok

I
Abstract

In existing system patient/user have to call the manually by getting contact from local
people but in case of emergency if patient did not get ambulance at time, then patient
life can be in danger. The best way to save life is to have an ambulance hiring
application which is effective and reachable to patient with third party helper’s help by
using this application.
In this application is for a medical emergency to call the ambulance. The patient
can book an ambulance any time. There is a login portal for patients and ambulances.
where in ambulance registration drivers have to enter driver’s information and submit
particular details similarly in patient registration the patient has to submit the patient's
details. While in an emergency case the patient can also go to the emergency portal and
have to select a book option then automatically the patient location will be confirmed
from the patient by the google map API. Then the patient has to put the patient situation,
problem then this information will be provided to the ambulance driver then the driver
will pick up from the requested location.

Keywords: Emergency, API, Patient, Ambulance, Maps, Location.

II
Content Page

Title Page No

I
Acknowledgement
II
Abstract
Contents III

VI
List of Figures
VIII
List of Tables

1. Introduction 1-2
1.1 Background And Basics….………………………………….... 1
1.2 Goals and Objectives…………………………………………. 2

2. Literature Survey 3-5


2.1 Literature Survey ………….………………………………... 3-4

2.2 Problem Definition ………….……………………………… 5

3. Scope of Project 6
3.1 Scope Statement …………...…...………...…………………... 6
3.2 Software Requirement Specification...……...……………....... 6
3.2.1 User interfaces 6
3.2.2 Hardware Interfaces 6
3.2.3 Software Interfaces 6 3.2.4 System Features 6

4. Methodology 7-9
4.1 Algorithm…………………………………………………. 7
4.2 System Architecture / Block Diagram……………………. 8

III
4.3 Detail Working………………………………….................. 8-9

5. Details of Project Design, Working & Processes 10-27


5.1 Project Design ………………....…………………………… 10-17
5.1.1 E-R Diagram……………………………………… 10
5.1.2 Data Flow Diagram………………………………. 11
5.1.3 Use Case Diagram………………………………… 12
5.1.4 Activity Diagram…………………………………. 13
5.1.5 Sequence Diagram………………………………… 16
5.2 Project Planning……………………………………………… 18-21
5.2.1 Efforts……………………………………………. 18
5.2.2 Time Estimation…………………………………... 18
5.2.3 Cost Estimation…………………………………… 19
5.3 Project Schedule……………………………………………... 22-27
5.3.1 Project Work Break Down Structure……………... 22
5.3.2 Team Structure……………………………………. 24
5.3.3 Tasks and Milestones ……….…………………… 24
5.3.4 Timeline Chart……………………………………. 26

6. Result and Applications 28-45


6.1 Result………………………………………………………… 28

6.2 Project Implementation & Testing………………………....... 28-33


6.2.1 Test Cases for Emergency Patient Portal………… 28
6.2.2 Test Cases for Patient Portal. …..……..…….……. 29
6.2.3 Test Cases for Forgot Password for patient………. 30
6.2.4 Test Cases for Ambulance Portal. …………..…... 31

6.2.5 Test Cases for Forgot Password for Ambulance…. 33

6.3 GUI Implementation……………………………………... 34

6.4 Applications………………………………………………. 45

IV
7. Conclusion & Future Scope 46
Appendix 47-48
References & Bibliography 49

List of Figures
Fig.
Figure Name Page No.
No.
4.2.1 System Architecture and Block Diagram 8

V
5.1.1.1 E-R Diagram 10

5.1.2.1 DFD Level 0 11

5.1.2.2 DFD Level 1 12

5.1.3.1 Use Case Diagram 13

5.1.4.1 Activity Diagram (Patient) 14

5.1.4.2 Activity Diagram (Ambulance) 15

5.1.4.3 Activity Diagram (Admin) 15

5.1.5 Sequence Diagram 17

5.3.1 Project Work Break Down Structure 22


5.3.2 Team Structure 24
6.3.1 Emergency1 34
6.3.2 Emergency2 34
6.3.3 Emergency3 35
6.3.4 Emergency SMS 35
6.3.5 Patient Registration 36
6.3.6 Patient Registration2 36
6.3.7 Patient Login 37
6.3.8 Patient Booking 37
6.3.9 Ambulance Registration 38
6.3.10 Ambulance Registration2 38
6.3.11 Ambulance Login 39
6.3.12 Ambulance Main 39
6.3.13 Emergency Patients 40
6.3.14 Confirm Patient 40
6.3.15 Emergency Patient Location 41
6.3.16 While Active 41
6.3.17 Active Schedule Patients 42
6.3.18 Call or Pick up 42
6.3.19 After Pickup SMS 43
6.3.20 Active Patient Call 43

VI
6.3.21 Enter Email Id 44
6.3.22 Email for password change 44
6.3.23 Set new password 45

List of Tables

Table No. Table Name Page No.


5.1 Time Estimation 18
5.2 Cost Estimation 20
5.3.4.1 Timeline Chart 1 26
5.3.4.2 Timeline Chart 2 27
6.2.1 Test Cases for Emergency Patient Portal………… 29

6.2.2 Test Cases for Patient Portal. …..……..…….……. 30


6.2.3 Test Cases for Forgot Password for patient………. 30
VII
6.2.4 Test Cases for Ambulance Portal. …………..…... 33
6.2.5 Test Cases for Forgot Password for Ambulance…. 33

VIII

You might also like