MAHARASTRA STATE BOARD OF TECHNICAL EDUCATION, LATUR

Puranmal Lahoti Government

Polytechnic, Latur
A PROJECT REPORT ON

“use case diagram for Hospital management system”

Submitted By
1. Phulmante Ganesh
2. Gambhire Aditya
3. Rode Rudresh
4. Kate Prachet

Under the Nobel Guidance Of

Prof. V. M. Khanapure

Submitted to

Department of IT Engineering
Puranmal Lahoti Government Polytechnic, Latur
For the Academic Year: 2020-21

Micro-Project: Part A
Title of the micro-project

Use case diagram for hospital

management system

1.0 Aim/Benefits of the Micro-Project:

 The aim of the project is to know the information about use case diagram.
 To know the elements, components and relationship of use case.
2.0 Course Outcomes Addressed:
 Select suitable software process model for software development.
 Use software modelling to create data design.
3.0 Proposed Methodology:
 A standard form of use case diagram is defined in the Unified Modelling
Language.
 To get an outside view of system using use case diagram, we can select
the topic that is hospital management system.
 Under the guidance of subject teacher, we can complete this
microproject and achieve the course outcomes that have been
addressed in the project and we can successfully complete our micro-
project.
Name of
Planned Planned
S. No. Details of Activity Responsible
Start Date Finish Date
Team Members
Collect information Gambhire
1 about program through 26-04-21 29-04-21 Aditya &
internet. Phulmante Ganesh

Rearrange and discuss Kate Prachet &

2 29-04-21 2-05-21
with subject teacher. Rode Rudresh

Prepare report with

3 2-05-21 7-05-21 Phulmante Ganesh
chart of micro project.

4.0 Action Plan:

5.0 Resources Required:

6.0 Names of Team Members with Roll No’s.:

S. No Resources Specifications Qty. Remarks
1 DESKTOP Win-10 RAM-4GB 1

2 SOFTWARE EdrawMax 1
3 Google Wikipedia 1
Software Engineering
4 Reference book 1
(Tech-Max)
S. No. Name Roll No.
1 Gambhire Aditya 36
2 Phulmante Ganesh 37
3 Rode Rudresh 39
4 Kate Prachet 52
Micro-Project: Part B

Title of the micro-project

Use case diagram for hospital

management system
1. Rationale:

 Software Engineering is the foundation for professional processes to be

followed involving principles, techniques, and practices for software
development. The micro-project provides a framework for software
professionals for building quality assured software products. It enables
students to blend the domain specific knowledge with the programming
skills to create quality software products.

2. Aims/Benefits of the Micro-Project:

 The aim of the project is to know the information about use case
diagram.
 To know the elements, components and relationship of use case.
3. Course Outcomes Achieved:

 Select suitable software process model for software development.

 Use software modelling to create data design.
4. Literature Review:

 One of the major challenges existing hospital management system

face is around operational efficiency and weir times between
different processes .departments and persons this paper highlights
such limitations of existing systems and proposes a RFID ( Radio
frequency ID)and wireless sensor based location and information
management framework that facilities real time tracking of hospital
assets ,personal and patients as they move through pre-set
procedure as part of daily activities of the hospital.
5. Actual Methodology Followed:

 A standard form of use case diagram is defined in the Unified

Modeling Language.
 To get an outside view of system using use case diagram, we can
select the topic that is hospital management system.
 Under the guidance of subject teacher, we can complete this
microproject and achieve the course outcomes that have been
addressed in the project and we can successfully complete our micro-
project.

6. Actual Resource Used:

Sr. No Resources Specification Qty. Remarks

1 DESKTOP Win-10 RAM-4GB 1

2 SOFTWARE EdrawMax 1
3 Google Wikipedia 1
Software Engineering
4 Reference book 1
(Tech-Max)
7. Outputs of the Micro-Projects:

 The output of our micro-project is to develop use case diagram

of hospital management system.

8. Skill Developed/ Learning Outcome of this Micro-Project:

 Presentation skills
 Team-interaction
 Communication skills

9. Applications of this Micro-Project:

 Application of the micro project are following:

1. We are able to access the whole information of hospital related to

staff, doctors, medicines, paramedical, etc.
2. Identifying the external and internal factors influencing the hospital.
3. Used to gather a requirement of patients.
4. Used to get an outside view of a hospital management.
Report of microproject

What is use case diagram?

Why Use case diagram? or simply, Why use cases? Some people
don't know what use case is, while the rest under-estimated the
usefulness of use cases in developing a good software product. Is use
case diagram underrated? I hope you will find the answer when
finished reading this article.
A UML use case diagram is the primary form of system/software
requirements for a new software program underdeveloped. Use
cases specify the expected behavior (what), and not the exact
method of making it happen (how). Use cases once specified can be
denoted both textual and visual representation (i.e., use case
diagram). A key concept of use case modeling is that it helps us
design a system from the end user's perspective. It is an effective
technique for communicating system behavior in the user's terms by
specifying all externally visible system behavior
.

A use case diagram is usually simple. It does not show the detail of
the use cases:
 It only summarizes some of the relationships between use
cases, actors, and systems.
 It does not show the order in which steps are performed to
achieve the goals of each use case.
As said, a use case diagram should be simple and contains only a few
shapes. If yours contain more than 20 use cases, you are probably
misusing use case diagram.

Hospital Management System is a large system including several

subsystems or modules providing variety of functions. UML use case
diagram example below shows actor and use cases for a hospital's
reception.
Purpose: Describe major services (functionality) provided by a
hospital's reception.
Hospital Reception subsystem or module supports some of the many
job duties of hospital receptionist. Receptionist schedules patient's
appointments and admission to the hospital, collects information
from patient upon patient's arrival and/or by phone. For the patient
that will stay in the hospital ("inpatient") she or he should have a bed
allotted in a ward. Receptionists might also receive patient's
payments, record them in a database and provide receipts, file
insurance claims and medical reports.

Origin of Use Case

These days use case modeling is often associated with UML, although
it has been introduced before UML existed. Its brief history is as
follow:
 In 1986, Ivar Jacobson first formulated textual and visual
modeling techniques for specifying use cases.
 In 1992 his co-authored book Object-Oriented Software
Engineering - A Use Case Driven Approach helped to popularize
the technique for capturing functional requirements, especially
in software development.
Purpose of Use Case Diagram
 Use case diagrams are typically developed in the early stage of
development and people often apply use case modelling for the
following purposes:
 Specify the context of a system
 Capture the requirements of a system
 Validate a systems architecture
Drive implementation and generate test cases
Developed by analysts together with domain experts

Elements of use case diagram

Actor

 Someone interacts with use case (system function).

 Named by noun.
 Actor plays a role in the business
 Similar to the concept of user, but a user can play different
roles
 For example:
 A prof. can be instructor and also researcher
 plays 2 roles with two systems

Use Case

 System function (process - automated or manual)

 Named by verb + Noun (or Noun Phrase).
 i.e., Do something
 Each Actor must be linked to a use case, while some use cases
may not be linked to actors.

Boundary of system

 The system boundary is potentially the entire system as defined

in the requirements document.
 For large and complex systems, each module may be the
system boundary.
 For example, for an ERP system for an organization, each of the
modules such as personnel, payroll, accounting, etc.
 can form a system boundary for use cases specific to each of
these business functions.
 The entire system can span all of these modules depicting the
overall system boundary
Use Case Relationship

Extends

 Indicates that an "Invalid Password" use case may include

(subject to specified in the extension) the behavior specified by
base use case "Login Account".
 Depict with a directed arrow having a dotted line. The tip of
arrowhead points to the base use case and the child use case is
connected at the base of the arrow.
 The stereotype "<<extends>>" identifies as an extend
relationship
Include

 When a use case is depicted as using the functionality of

another use case, the relationship between the use cases is
named as include or uses relationship.
 A use case includes the functionality described in another use
case as a part of its business process flow.
 A uses relationship from base use case to child use case
indicates that an instance of the base use case will include the
behavior as specified in the child use case.
 An include relationship is depicted with a directed arrow having
a dotted line. The tip of arrowhead points to the child use case
and the parent use case connected at the base of the arrow.
 The stereotype "<<include>>" identifies the relationship as an
include relationship.

Generalization

 A generalization relationship is a parent-child relationship

between use cases.
 The child use case is an enhancement of the parent use case.
 Generalization is shown as a directed arrow with a triangle
arrowhead.
 The child use case is connected at the base of the arrow. The
tip of the arrow is connected to the parent use case.
Output of the microproject