Professional Documents
Culture Documents
Introduction
1
The advent of smart phones in the recent times has revolutionalized the way
people use technology. Smart phones because of their powerful features and ease of use
have emerged as the next-generation mobiles. The use of smart phones for availing
Health Care services such as doctor appointments, blood bank search, and emergency
message and so on would simplify the process for people unlike the conventional way.
This project is a Health Care Access application using android which provides efficient
and time saving approach to access health care services.
1.1 Purpose:
Health Care Access System is an android based application intended to help
people to book an appointment with a doctor and helps doctors to manage their
appointments, search for blood banks in which blood of the required group is available
using location based services notify the emergency number corresponding to our
location in situations where one is in need of emergency help at an unknown place or is
travelling and is not aware of the emergency number of that location ,search for nearest
hospitals based on our location and handy tips for general health problems and first-aid
tips in emergency.
1.2 Scope
Developing an application for smart phones using the open source android SDK
gives an opportunity to solve problems around us by making use of this technology.
Health Care Access System presents a solution to the common problems faced by people
in availing health care services .It simplifies the process of appointment booking making
this application useful to both a person who uses it for booking appointments and a
person who is responsible for managing them. Searching for a required blood group
based on location is desirable because it would save precious time. Handy first-aid tips
would be useful in unanticipated situations. Finding nearest hospitals based on our
current location is always convenient. Location based emergency number message is
particularly useful for people who are travelling
Blood Bank Search: In order to find blood of a required group one has to enquire
several blood banks through telephonic calls which is a time consuming process
1.4.1Appointment
Person chooses a specialty, selects the doctor whom he/she wishes to consult, the
doctor’s schedule is displayed from which the patient selects a slot to book an
appointment. A doctor or doctor’s personal assistant can view his/her schedules and
manage it. The person who books an appointment gets a reminder of appointment.
Also if a scheduled appointment is cancelled by a doctor due to some reason the
person gets a notification to reschedule.This overcomes the tiresome process of
interacting with an Invoice Response System
Search for the availability of blood of the required group in the blood banks nearest to
us. This helps to provide timely and accurate information that saves precious time to
search blood for a patient who is in urgent need of blood.The search functionality of
our system also provides the user with a routemap guiding the user towards
thedestination
1.4.3Hospital Search
1.4.4Emergency Message
3
2.Requirements
4
2.1 Functional Requirements
This application has the following functionalities:
2.1.2Scheduling of appointments
A Doctor is selected based on the requirements. then day and time are selected, slots
are obtained .appointment is booked based on the availability of the doctor. later a user can
view , cancel or reschedule the appointments .Doctor manages his/her schedule.
This gives users quick access to local medical assistance, based on the current location
and sends a predefined message to the emergency services with the details of the location of
the emergency case.
5
2.2 Non-functional Requirements:
Those requirements which are not the functionalities of a system but are the
characteristics of a system are called the non-functionalities. Every software system has some
non-functionalities. Just fulfilling the requirements of the user is not a good task, keeping the
system accurate, easy to maintain, reliable and secure is also a basic part of software
engineering. Health Care Access System must have the following non-functional requirements.
This system must be fit according to the performance wise. It should use
less memory and will be easily accessible by the user. Memory management should be
done wisely so that none of the memory part goes wasted.
.
2.2.2 Safety Requirements:
The software used is open source software and thus all licenses are free.
Android applications run in a sandbox, an isolated area of the system that does not have
access to the rest of the system's resources, unless access permissions are explicitly
granted by the user when the application is installed. The sandboxing and permissions
system lessens the impact of vulnerabilities and bugs in applications.
Quality is the degree of excellence. For a customer it is the fitness for use
HealthCare Access System should possess the following quality attributes.
Reliability
Measure if product is reliable enough to sustain in any condition. Should give
consistently correct results. Product reliability is measured in terms of working of
project under different working environment and different conditions.
Maintainability
Different versions of the product should be easy to maintain. For development its
should be easy to add code to existing system, should be easy to upgrade for new
features and new technologies time to time.
Usability
This can be measured in terms of ease of use. Application should be user friendly.
Should be easy to learn. Navigation should be simple.
The system must be easy to use for input preparation, operation, and interpretation of
output,provide consistent user interface standards or conventions with our other
frequently used systems and be easy for new or infrequent users to learn to use the
system.
6
Portability
This can be measured in terms of Costing issues related to porting, Technical issues
related to porting, Behavioral issues related to porting.
Correctness
Application should be correct in terms of its functionality, calculations used internally
and the navigation should be correct. This means application should adhere to
functional requirements.
Efficiency
To Major system quality attribute. Measured in terms of time required to complete any
task given to the system. For example system should utilize processor capacity, disk
space and memory efficiently. If system is using all the available resources then user
will get degraded performance failing the system for efficiency. If system is not
efficient then it cannot be used in real time applications.
Testability
System should be easy to test and find defects. If required should be easy to divide in
different modules for testing.
Flexibility
Should be flexible enough to modify. Adaptable to other products with which it needs
interaction. Should be easy to interface with other standard 3rd party components.
Reusability
Software reuse is a good cost efficient and time saving development way. Different
code libraries classes should be generic enough to use easily in different application
modules. Dividing application into different modules so that modules can be reused
across the application.
Interoperability
Interoperability of one system to another should be easy for product to exchange data or
services with other systems. Different system modules should work on different
operating system platforms, different databases and protocols conditions
7
2.3 Life cycle
The life cycle model used for our project is the Prototyping Model. In the prototyping model of
software development a prototype is made first and based on it final product is developed. A prototype
is a model or a program which is not based on strict planning, but is an early approximation of the final
product or software system. A prototype acts as a sample to test the process. From this sample we learn
and try to build a better final product.
Advantages
When prototype is shown to the user, he gets a proper clarity and 'feel' of the functionality of
the software and he can suggest changes and modifications.
When client is not confident about the developer's capabilities, he asks for a small prototype to
be built. Based on this model, he judges capabilities of developer.
It reduces risk of failure, as potential risks can be identified early and mitigation steps can be
taken.
Iteration between development team and client provides a very good and conductive
environment during project.
Time required to complete the project after getting final the SRS reduces, since the developer
has a better idea about how he should approach the project.
8
2.4 Computational resource requirements
Processor : Pentium 4
RAM : 512MB
Hard Disk : 40GB
Android phone : Version 2.3 or higher
9
3.Architecture
10
3.1 Software Architecture
Android Client
-General User
-Doctor
The Android SDK includes a mobile device emulator, a virtual mobile device that runs on your
computer. The emulator lets you develop and test Android applications without using a physical
device.
11
3.2 Technical Architecture
APPOINTMENT SCHEDULING
12
EMERGENCY
HOSPITAL SEARCH
13
4. Design
4.1 Objective
A software design document details how the software requirements should be implemented
as well as giving the programmers a blueprint to follow. Once the software design document is
approved by the appropriate parties, it becomes a baseline for limiting changes in the scope of
the project.
4.2 Modules
4.2.1Profile management:
This module takes the information of clinical details of a patient and his family
members also. The patient or a doctor can retrieve the information whenever necessary.
Functionalities:
User registers giving all his details.
User can login with his username and password.
User can change his password.
User can register his family members
4.2.2Appointment:
User can book an appointment with the doctor.
Functionalities:
o User can select a hospital and fix an appointment with the doctor in the
available slots.
o Doctor can login with his username and password and view his
appointments.
o Doctor can also cancel, re-schedule his appointments.
o Doctor can also view the clinical details of the patient with whom his
appointment is booked.
14
4.2.3Blood bank Search:
Searches blood banks for the availability of blood of a required group.
Functionalities
Displays blood banks on Google Maps
Checks for blood group availability
Get directions
4.2.4Emergency Message:
This module sends a predefined message to the emergency services with the
details of the location of the emergency case.
Functionality:
A predefined message showing the exact user location ongoogle maps is sent to the
emergency number
15
Use Case diagram for Whole System
A use case illustrates a unit of functionality provided by the system. The main purpose of the use
case diagram is to help development teams visualize the functional requirements of a system,
including the relationship of the “actors” (human beings who will interact with the system) to
essential processes, as well as relationships among different use cases.
Use case diagram generally show groups of use cases – either al use cases for the complete
system, or a breakout of a particular group of use cases with related functionality (e.g., all
security administration –related use cases).
A use case diagram is typically used to communicate the high level functions of the system and
system scope
Registration
Clinical Details
Login
Appointment
Hospital Search
User Doctor
Emergency
16
Class diagram for Whole System
A class diagram is a static structure diagram that describes the structure of system by shadowing
the systems classes, their attributes, operations (or methods), and the relationship among the
classes
Patient Doctor
Location
Appointment Medication
+Latitude
+Longitude +Day: char +TipId: int
+Time: varchar +TipDescription: char
+Search() +Hospital: char +RemedyId: int
+Doctor: char +RemedyDescription: char
+Patient: char +MedicineId: int
+MedicineName: char
BloodBank
+MatchSymtom()
+Name: char Hospital
+Display()
+Id: int
+HospitalId: int
+Volume: varchar
+HospitalName: char
+Groups: varchar
+Doctors: char
+SearchGroup()
+CheckAvailability()
17
ACTIVITY DIAGRAM
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flowchart to represent a flow from one activity to another
activity. The activity can be described as an operation of the system. So the control flow is drawn
from one operation to another. This flow can be sequential, branched or concurrent. Activity
diagram deals with all type of flow control by using different elements like fork, join etc.
Register
Register
Login
Login
Availability
Cancel Slot
No
Yes
Book an Appointment
No
Yes
18
19
4.4 Database design
20
5. References
6. Presentation Slides
21
Department of Computer Science
and Engineering
Graduate With Excellence
A.Sirisha-3090
K.Shruthi-3088
22
Can be used by Smartphone holders.
23
Display nearby hospitals.
Choose hospital specialty and doctor.
Display doctors schedule.
Book an appointment.
Get Confirmation of the appointment.
Get Remainders.
Doctors manage their appointments
24
GPS determines our current location.
25
Performance constraints
It should use less memory and should be easily
accessible by the user.
Safety Requirements
Android applications run in a sandbox.
Usability
Maintainability
Correctness
Flexibility
Reusability
26
SOFTWARE INTERFACES
COMMUNICATION INTERAFACES
27
Apache Tomcat
28
Appointment
Scheduling
29
Emergency Number
Design document
Details how the software requirements should
be implemented
Provides a blueprint to follow.
Becomes a baseline for limiting changes in the
scope of the project on approval.
30
Profile management:
This module takes the information of clinical details of a patient
and his family members also. The patient or a doctor can
retrieve the information whenever necessary.
Functionalities:
User registers giving all his details.
User can login with his username and password.
User can change his password.
User can register his family members
Appointment:
User can book an appointment with the doctor.
Functionalities:
User can select a hospital and fix an appointment
with the doctor in the available slots.
Doctor can login with his username and password
and view his appointments.
Doctor can also cancel, re-schedule his
appointments.
Doctor can also view the clinical details of the patient
with whom his appointment is booked.
31
Blood bank finder:
Searches for the nearest blood bank based upon the
availability of blood.
Functionalities
Searches for nearest blood bank based on location of the user
and the availability of blood
Get directions
32
Empower Women – Impact
Graduate Withthe World
Excellence
Clinical Details
Login
Appointment
Hospital Search
User Doctor
Emergency
33
ACTIVITY DIAGRAM
User Appointment Doctor
Register
Register
Login
Login
Availability
Cancel Slot
No
Yes
Book an Appointment
No
Yes
Patient Doctor
CLASS DIAGRAM
+Id: int +Id: int
+Name: char +Hospital: char
+DOB: varchar +Name: char
+Gender: char +Gender: char
+BP: varchar +Speciaization: varchar
+Sugar: float +Experience: int Disease & symptoms
+Count: float +Qualification: varchar
+PracticeId: int +DiseaseId: int
+SearchDoctor() +MailId: varchar +DiseaseName: char
+SearchHospital() Emergency +SymptomId: int
+EditAppointment() +EditMedication() +SymptomName: char
+SearchBloodGroup() +EditAppointment() +ServiceNumber: int
+() +DisplaySymptom()
+SendMessage()
+ReceiveCall() +getServiceNumber() +MatchSymptom()
+Call()
Location
Appointment Medication
+Latitude
+Longitude +Day: char +TipId: int
+Time: varchar +TipDescription: char
+Search() +Hospital: char +RemedyId: int
+Doctor: char +RemedyDescription: char
+Patient: char +MedicineId: int
+MedicineName: char
BloodBank
+MatchSymtom()
+Name: char Hospital
+Display()
+Id: int
+HospitalId: int
+Volume: varchar
+HospitalName: char
+Groups: varchar
+Doctors: char
+SearchGroup()
+CheckAvailability()
34
Empower Women – Impact
Graduate Withthe World
Excellence
35
Software Engineering-A Practitioner’s Approach-
Roger.S.Pressman
The Unified Modeling Language User Guide-Ivar
Jacobson,Grady Booch &James Rumbaugh
www.wikipedia.com
www.sdlc.ws
36
37