BY

NARESH PRAJAPATI (Roll No: 517)

SANDIP PATEL (Roll No: 504)
HITUL PATEL (Roll No: 518)
JAYKISHAN PATEL (Roll No: 520)
SEMESTER -IV

INCHARGE NAME
ASST. PROF. HITESH PANCHAL
COMPUTER DEPARTMENT

Faculty of Engineering & Technology

Computer Department
Gujarat technological University
May 2011
 GUJARAT TECHNOLOGICAL UNIVERSITY
GROW MORE FACULTY OF ENGINEERING
Computer Department
2010-11

CERTIFICATE
This is to certify that Mr. Naresh Student of B.E. Semester IV, Roll No.
517 has satisfactorily completed his term work of the subject Object Oriented
Analysis and Design (140703) during the academic year 2010-11 and
submitted on 25-04-2011.

Staff in charge Head of department

.
 GUJARAT TECHNOLOGICAL UNIVERSITY
GROW MORE FACULTY OF ENGINEERING
Computer Department
2010-11

CERTIFICATE
This is to certify that Mr. Sandip Student of B.E. Semester IV, Roll No.
504 has satisfactorily completed his term work of the subject Object Oriented
Analysis and Design (140703) during the academic year 2010-11 and
submitted on 25-04-2011.

Staff in charge Head of department

.
 GUJARAT TECHNOLOGICAL UNIVERSITY
GROW MORE FACULTY OF ENGINEERING
Computer Department
2010-11

CERTIFICATE
This is to certify that Mr. Hitul Student of B.E. Semester IV, Roll No.
518 has satisfactorily completed his term work of the subject Object Oriented
Analysis and Design (140703) during the academic year 2010-11 and
submitted on 25-04-2011.

Staff in charge Head of department

.
 GUJARAT TECHNOLOGICAL UNIVERSITY
GROW MORE FACULTY OF ENGINEERING
Computer Department
2010-11

CERTIFICATE
This is to certify that Mr. Jaykishan Student of B.E. Semester IV, Roll
No. 520 has satisfactorily completed his term work of the subject Object
Oriented Analysis and Design (140703) during the academic year 2010-11
and submitted on 25-04-2011.

Staff in charge Head of department

.
 INDEX

1. Abstract

2. Requirement

3. Introduction of Tool used to draw

diagram(MS-Visio)

3.1 Use Case Diagram

3.2 Class Diagram
3.3 Object Diagram
3.4 Activity Diagram
3.5 State Diagram
3.6 Sequence Diagram

4. List of Diagram

4.1 User’s View Diagram

4.2 Structural View
4.2.1 Class Diagram
4.2.2 Object Diagram
4.3 Behavioral Diagram
4.3.1 Activity Diagram
4.3.2 State Diagram
4.3.3 Sequence Diagram

5. Conclusions

6. Reference
 1. Abstract

Analysis and design of Hospital management system is based on

UML diagram.

A Project of Hospital Management includes registration of patient

storing their details into the system and also computerized billing
in the pharmacy, and test labs.

The main objectives of the system is which shows and help us to

collect most of the information about Hospitality and Medical
services the system is very simple in design and to implement it.
At the same time, the correct use of it will reduce system
complexity and improve software development efficiency and
portability.
 2. Requirement

1. ADMISSIONS:

This Module helps in registering information about patients

and handles patient’s query.

2. DOCTOR APPOINTMENTS
This Module deals with, when the ID is generated the
Appointment time & number from the Receptionist
and accordingly visit the doctor.

3. TESTS APPOINTMENTS

This Module Deals with, when the ID is generated the

patient receives the Appointment time & number from
the Receptionist and accordingly undergoes the tests.

4. BED ALLOTMENT

This Module handles with allotting the Bed to various

patients by checking their ID.
5. UNDERGO OPERATION

This Module handling with undergoes the various

operations by diagnosing the patients.

6. DRAW SALARY

This Module checks whether the person is a Doctor/Staff

and draws salary based on the information.

7. EDIT DOCTOR/STAFF INFORMATION

This Module handles the activities such as editing
(Updating) Doctor/Staff information into the database.

7.1 ADD DOCTOR/STAFF INFORMATION

This Module handles the activities such as adding
Doctor/Staff information into the database.
7.2 DELETE DOCTOR/STAFF INFORMATION
This Module handles the activities such as deleting
Doctor/Staff information into the database.

8. PRESCRIBE TESTS
This Module handles various activities such as Doctor
Diagnoses the patient, gives treatment & gives suggestions
to the patients, & prescribes laboratory tests & medicines.
 9. WARDWISE BED STATUS

It deals with the maintenance of the wards, inter- and intra-

ward transfers.

10. ADMISSION/DISCHARGE REPORTS

This Module helps in generating patient’s discharge

summary, which includes patient’s health at the time
of discharge, medical history, various diagnosis and
drug prescriptions, history of present illness and course
in hospital.

11 . PATIENT INFORMATION

This Module helps in generating the patient information

Which is provided by doctor.
 3. Introduction
to
tools

3.1 Use Case Diagram

Actor
An actor is a direct external user of a system, it is not part
of system Actor can be person, device, & other system.
Ex. Patient is an actor of hospital management system.

UseCase

A use case is a coherent piece of functionality that a

system can provide by interacting with actors.
Ex. Check up patient by doctor.

System

System boundary is a rectangle in which use case

mentioned in & it have system name also.
Ex. Hospital Management system.
 «uses»

The include relationship incorporate one use case within

The behavior of other use case.

«extends»

The extend relationship adds increment behavior to a

use case.

An arrow indicates the relationship among actor & use

case.
3.2 Class Diagram
Class1

A class describe a group of objects with the same

properties (attributes), behavior(operation),kinds of
relationship, Semantic.
Ex. Hospital is a class.

End1 End2

An association is a description of group of links with

common Structure & common semantic.
Ex. A person works for a company.

An aggregation is a strong form of association in which

an Aggregate Object is made of constituent parts.
Ex. Patient use catering for meals.

1 *

Composition is a form of aggregation with two

additional Constrain.
Ex. Hospital has Department.
 A generalization is the relationship between a class
(super class) & One or more variation of the class
(subclass).
Ex. Patient, Doctor, & Nurse are sub class of a Person
class.

An N- array association is relationship among three

classes Inter dependent to each other.
Ex. A Patient get prescription from Doctor in Hospital.
3.3 Object Diagram
Object1

An object is a instant of a class.

Ex. Joe:Doctor

Note: In Object diagram the relations are as same as in class

diagram like as association, aggregation, generalization,
Composition, N- array association.
3.4 Activity Diagram

Initial state is a notation of starting of activity.

ActionState

An action state is noted the working flow .

Ex. Get appointment is a active state.

In decision if one condition is satisfied, it’s arrow

indicate The next activity to perform.
Ex. Pay fees of doctor is a guard condition.

Fork pseudo state enable to take a single event

transmission & split it into several control parts.

Join pseudo manages multiple transmission part into one

Transmission.
Final state is a notation of ending of activity.
3.5 State Diagram

Fork pseudo state enable to take a single event

transmission & split it into several control parts.

Join pseudo manages multiple transmission part into

one Transmission.

State

A state is an abstraction of the values and links of an

Objects, sets of values and links are grouped to gather
Into a state according to the group behavior of object.
Ex. Prescribing is a state.

Drawn as a line from the origin state to the target state.

An arrowhead points to the target state.

Note: Final & Initial state are as same as in Activity diagram.

3.6 Sequence Diagram

Object

In Sequence diagram each actor, object or system is

represent by vertical line called object life line.

An Activation describe that the system is in process by

means system in use.

Message

Message

Messages extend from the lifeline of one object to the

lifeline of another except in the case of a message
from an object to itself, in which case the message
begins and ends on the same lifeline.
 4. List of diagram

4.1.1. Use Case Diagram(user’s view diagram)

Use case Diagram is a visual representation of actor

and use case together with any additional definition
and specification.

It has use cases(requirement) & Actor(person or system)

There may be some use cases that do not directly interact
with actors.

In many instance, a function requirement maps directly

to a use case.

In Use case diagram of hospital management system there

are an actors patient, doctor, nurse, technologist,
technician& employee.

An employee are generalized as receptionist,

administration, Cleaner & cooker.
 A use case diagram of hospital management system
HOSPITAL MANAGEMENT SYSTEM
Doctor appoinment
info.
«uses»

Check up

«extends»

Tests appoinment

Patient

Under go operation

«extends»

Doctor

Prescribstion

«uses»

Addmit /Discharge

Patient information

Ward wise bed

status

Employee
Nurse Edit doctor/staff

Cleaning

Meals/breakfast

Opn.machinary
application
Technologist
«extends»

Opn.machinary
repair

Technistion
4.2 Structural View

4.2.1. Class Diagram

Class Diagram shows a set of classes, interfaces, and

collaborations and their relationships. They are important
for visualizing, specifying, and documenting structural
models and also for constructing executable systems
through forward and reverse engineering.

In class diagram of hospital management there are many

classes like Hospital, Patient, Doctor, Receptionist, Nurse
etc. the relationship among classes are association,
generalization, composition, aggregation.
 A class diagram of hospital management system
Hospital
Person Department
-name:string
-name:string * -add:Address -d.name:string
* -title:string * -phone:Phone -d.staff:string
-gender:Gender -d.staff member:Member
+add/delete doctor()
1 -b.date:Date 1 *
+draw salary() +treatment()
+visit() +patient-info() +cleaning the hospital()
+addmit() *
+manegment()
+write prscription()
Catring Staff
-c.name:string -s.name:string 1
-c.add:Address -s.member:Member
-contect.no:Number -staff specialityt:string
-facility:Facylity type +patient-info()
+make meal() +mainten machinary()
+make tea/breakfast() +treatment()
+sale meal/tea/brakfast()

Addministration staff
Patient Operation staff Technical staff
-name:string
-accepted:Date * -name:string -name:string
-post:Post
-sikness:History -add:Address -post:Post
* -accountent:Accountent
-1 -presciption:string -speciality:string +mainten machinary()
-reciptionist:Reciptionist
-allergies:string +check up() +order machinary()
+login()
+appoinment() +write priscription() +use machinary()
+accont()
* +addmit() +advice()
+patint billing -info()
+leave() +doctor-info()
+under go opretion() +cash collection()

-* *
Examination Doctor Nurse Front desc staff Technician Technologist
-e.type:string -d.name:string -n.name:string -front desk name:string -t.name:string -t.name:string
-e.name:string 1 -d.add:Address -n.degree:string -staff member:Member
-phone:Phone +repairing of machinary() +use of machinary()
+check up() -vard .no:ward number +detail of patient()
-d.speciality:string
+set warding() +all detail doctor&nurse()
-* +give advice() +check up()
*
+write prescription()
+treatment()
1
+sergery()
* 1

Diagonosis Surgical technologhist

Receptionists
-d.name:string Surgeon -s.name:string
-d.specialist:string -r.name:string -s.type:string
-surgeon name:string -r.post:Post
+advice() +surgery()
-surgeon speciality:string
+check up() +account ()
+opretion() +login()

Prescription Tretment Medical

1 -p.type:string -t.type:string -m.name:string
-p.number:P number -t.name:string -m.liesenceno:Liesence
-p.name:string -t.cost:Cost -stock of drug:Stock
-1 +give madicine(drug)() +surgery() +sale drug()
+cencle medicine() +theory() +buy drug()
+account()

*
Theory Surgery *
-t.name:string -s.name:string
-t.cost:Cost -s.type:Type
+apply to patient() -s.cost:Cost
+apply to patient()
4.2.2. Object Diagram
An object diagram shows individual objects and their
relationship .Object diagram are helpful for documenting
test cases and discussing example. A class diagram
correspond to infinite set of object diagrams.
In object diagram there mainly consist name of system.
 An object diagram for hospital management system

*
Strling : Hospital
* *
1
: Person Ortopadic : Department
*
1
*

: Staff 1
Michel's cantin : Catring

* *
-1 John : Patient : Operation staff : Administretive staff : Technical staff

*
-* *

1
: Examination Joe : Doctor Mery : Nurse : Front desk staff Alis : Technician Martin : Technoligist
-*
1
*

*
: Diagonosis William : Surgeon Karl : Receptionist Mike : Surgical technologist
1

1
: Prescription : Tretment
-1 James pharma : Medical

*
*

: Theory : Surgery
4.3. Behavioral Diagram

4.3.1. Activity Diagram

An activity diagram shows the sequence of steps that make

up a complex process, such as an algorithm or work flow.
It focus on operation.
An activity diagram for hospital management system

Go to Reception

[Pay fees of docyor]

Get appoinment for doctor

Waiting for turn

Check up

[normal disease]
Prescription

Admit

Tests or Under go opn.

[If patient good]

Discharge

Go to medical

Buy drug

[Pay money]

Buy
4.3.2. State Diagram

A state diagram is a graph whose nodes are states & whose

direct arcs are transition between states. A state diagram
specifies the state sequence caused by event sequence.
A state diagram for hospital management system

Go to Reception

Paying fees [Not paying] pay fees first

Getting appoinment

Wait for turn

Cheking Prescribing

Admiting

Tests or under go opn.

Discharging

[If patint good]

Discharged

Go to madical

Buying drug

Buyed
4.3.3. Sequence Diagram

A sequence diagram shows the participants in an

interaction and the sequence of messages among them.
It is not attempt to be general.
 A sequence-1 diagram for hospital management system

Patient Receptionist Doctor Lab test man Medical

Get appoinment

Pay fees

Petient type

Check up

Normal disease

Prescription
Buy drug

Get drug

Not good

Give testes

Test report

Prescription
By drug

Get drug
 A sequence-2 diagram for hospital management system

Patient Doctor Operation theator Medical

Check up

Major dieses

Admit

Check up

Patient is good

Prescription
Buy drug

Get drug
 5. Conclusion

According to Unified Modeling Language, we use UML diagram

For represent the complex system in simplest and compact form.
In short time we describe the flow of system. It is easily
understandable by user.
 6. References
Michael R Blaha, James R Rumbaugh. The Object-Oriented
Modeling and Design with UML, Second Edition.
Dorling Kindersley, India: Pearson Prentice Hall, 2010.