Department of Computer Science & Engineering

University Institute of Engineering & Technology

Kurukshetra University, Kurukshetra

(Session: 2019-2023)

OOSE Lab Report

SUBMITTED TO:- SUBMITTED BY:-

Mr. Atul Sharma Prakriti

Assistant Professor CSE-A (7 Sem )

CSE Department 251902045

UIET, KUK

1
 INDEX

Practical No. Practical Page No. Signature

1. 3
Choose any one project and write the
complete problem statement.

2. 5
Write the software requirements
specification document.

3. Draw the entity relationship diagram. 7

4. 9
Draw the data flow diagrams at level 0
and level 1.

5. Draw use case diagram. 12

6. Draw activity diagram of all use cases. 14

7. Draw state chart diagram of all use cases. 20

8. Draw sequence diagram of all use cases. 22

9. 24
Draw collaboration diagram of all use
cases.

10. 26
Assign objects in sequence diagram to
classes and make class diagram.

Practical-1

Choose any one project and write the complete problem statement.
Project: Hospital Patient Management System

Problem Statement: The hospital needs an online system whereby it can accommodate the
patients comfortably and avoid any confusion to the doctors regarding their work. There

2
AIM :

should be a system where the patients are categorised under insurance policy and non policy
holders and the system helps the hospital management to claim the bills from concerned
insurance companies.

The software system should be useful:

● to record a patient's details along with the complaint
● should record the inpatient details and outpatient details and arrange the appointment
of doctors
● Should also provide the management reports like schedules, appointments of doctors,
inpatients, insurances and discharges
● generate bills dynamically for the discharged patients etc.

Features:-
1. The administrative user should create new users and change their passwords.
He should be able to add the doctor’s information as well as new doctor’s
details. Also can add information related to inpatients, outpatients, rooms
availability, billing and insurance information. The administrator can view the
management reports.
2. The doctors can change their own passwords. He can view his own
appointments and information of inpatients and outpatients for any day.
3. Manager is another person who manages the activities in the hospital. He can
add a new doctor to the list. He can also add new room information. He can
view the information of doctors, rooms and patients.
4. An accountant can add the information related to patient insurances and view
all the reports. He can view the details of inpatients, outpatients and
discharged patient’s information. He also collects the bill amount from the
patient and enters it into the system.

5. Catchy and user-friendly interface

6. Smooth and fast user experience.
7. All access in system for ADMIN
8. When a patient is admitted, the front-desk staff checks to see if the patient is
already registered with the hospital. The system shall allow front-desk staff to

3
 give each patient an Id and add it to the patient’s record. This ID shall be used
by the patient throughout his/her stay in hospital.
9. Create an ERP account for all registration in DB and send login credentials
via email.
10. The consulting nurse shall use a system to assign the patient to an appropriate
ward. The consulting nurse shall use system to assign Patient to a waiting list
if no bed is available.
11. Maintain a list of doctors, surgeons and nurses that are assigned to patients in
each ward.
12. The system generates reports on the following information: patients, bed
availability and staff schedules after every six hours.

4
AIM :

Practical-2

Write the software requirements specification document.

Software Specification Documents: Requirements are prone to issues of ambiguity,

incompleteness and inconsistency techniques such as rigorous inspection have been shown to
help deal with these issues.
Ambiguity, incompleteness and inconsistencies that can be resolved in the requirement phase
typically cost orders of magnitude less to correct than when these same issues are found in
later stages of product development.
The purpose of developing the specified software is to describe the analysis involved in the
Hospital Management System.

Software Requirement :
● Windows 8 or higher
● Notepad++/VS Code

Hardware Requirement :
● Laptop or PC
● i5 processor or higher
● 4GB RAM
● 200 MB Storage

CONTENTS FOR SRS DOCUMENT :

1. Introduction:
● Purpose
● Scope
● Definitions, Acronyms and Abbreviations
● References
● Overview

2. Overall Description:

5
 ● Product perspective
❖ System Interfaces
❖ User Interfaces
❖ Hardware Interfaces
❖ Software Interfaces
❖ Communication Interfaces
❖ Memory Constraints
❖ Operations ❖ Site Adaptation Requirements

3. Specific Requirements :
● User Interfaces
● Hardware Interfaces
● Software Interfaces
● Communication Interfaces

6
AIM :

Practical-3

Draw the entity relationship diagram.

E-R (Entity-Relationship) Diagram is used to represent the relationship between entities in a

table. ER diagrams represent the logical structure of databases. ER Diagram represents the
relationship between two database tables.

E-R diagram means Entity Relationship diagram. Entity is an object of a system, generally
we refer entity as a database table , the E-R diagram represents the relationship between each
table of the database. E-R diagrams represent entities with attributes, attributes are the
properties of entities. If we assume an entity is a database table then all the columns of the
table are treated as attributes.

So,

This ER (Entity Relationship) Diagram represents the model of Patient Management System
Entity. The entity-relationship diagram of Patient Management System shows all the visual
instrument of database tables and the relations between Doctor, Disease, Patient, Medicine
etc.

Patient Management System Entities are:

● Patient Entity ● Doctor Entity

● Doctor Schedule Entity
● Disease Entity
● Test Entity
● Medicine Entity

7
 Practical-4

Draw the data flow diagrams at level 0 and level 1.

The Patient Management System Data flow diagram is often used as a preliminary step to
create an overview of the Patient without going into great detail, which can later be
elaborated. It normally consists of overall application dataflow and processes of the Patient
process. It contains all of the user flow and their entities such as all the flow of Patient,
Medicines, Tests, Doctor Schedule, Disease, Doctors, Report.
All of the below diagrams have been used for the visualisation of data processing and
structured design of the Patient process and working flow.

8
AIM :

Zero Level Data Flow Diagram(0 Level DFD) Of Patient Management System:
This is the Zero Level DFD of Patient Management System, where we have elaborated the
high level process of Patient. It's a basic overview of the whole Patient Management System
or process being analysed or modelled. It's designed to be an at-a-glance view of Disease,
Doctors and Report showing the system as a single high-level process, with its relationship to
external entities of Patient, Medicines and Tests. It should be easily understood by a wide
audience, including Patient, Tests and Disease.
In zero level DFD of Patient Management System, we have described the high
level flow of the Patient system.

High Level Entities and process flow of Patient Management System:

● Managing all the Patient
● Managing all the Medicines
● Managing all the Tests
● Managing all the Doctor Schedule
● Managing all the Disease
● Managing all the Doctors
● Managing all the Report

9
First Level Data Flow Diagram(1st Level DFD) Of Patient Management System: First
Level DFD (1st Level) of Patient Management System shows how the system is divided into
subsystems (processes), each of which deals with one or more of the data flows to or from an
external agent, and which together provide all of the functionality of the Patient
Management System system as a whole. It also identifies internal data stores of Report,
Doctors, Disease, Doctor Schedule, Tests that must be present in order for the Patient system
to do its job, and shows the flow of data between the various parts of Patient, Tests, Doctors,
Report, Disease of the system.
DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will
highlight the main functionalities of Patient.

10
Main entities and output of First Level DFD (1st Level DFD):
● Processing Patient records and generate report of all Patient
● Processing Medicines records and generate report of all Medicines
● Processing Tests records and generate report of all Tests
● Processing Doctor Schedule records and generate report of all Doctor Schedule
● Processing Disease records and generate report of all Disease
● Processing Doctors records and generate report of all Doctors
● Processing Report records and generate report of all Report

Practical-5

AIM : Draw use case diagram.

11
The Use Case Diagram is a graphic depiction of the interactions among the elements
of the Hospital Patient Management System. It represents the methodology used in
system analysis to identify, clarify, and organise system requirements of Hospital
Management System.
The main actors of Hospital Patient Management System in this Use Case Diagram
are:
● Super Admin
● System User
● Hospital Staffs
● Anonymous Users who perform the different types of use cases such as
Manage Hospitals, Manage Patient, Manage Doctors, Manage Nurses, Manage
Appointments, Manage Medicines, Manage Users and Full Hospital Patient
Management System Operations.

12
 Practical-6

AIM : Draw activity diagram of all use cases.

This is the Activity UML diagram of the Patient Management System which shows the flows
between the activity of Doctor Schedule, Patient, Disease, Doctor, Medicine.

13
The main activity involved in this UML Activity Diagram of Patient Management System are
as follows:
● Patient Activity
● Doctor Schedule Activity
● Disease Activity
● Doctor Activity
● Medicine Activity

Features Of The Activity UML Diagram of Hospital Patient Management System

Admin User can search Doctor Schedule, view description of a selected Doctor Schedule,
add Doctor Schedule, update Doctor Schedule and delete Doctor Schedule.

● Its shows the activity flow of editing, adding and updating of Patient
● User will be able to search and generate report of Disease, Doctor, Medicine
● All objects such as (Doctor Schedule, Patient, Medicine) are interlinked
● Its shows the full description and flow of Doctor Schedule, Doctor, Medicine,
Disease, Patient

14
15
16
17
18
19
 Practical-7

Draw state chart diagram of all use cases.

20
21
 Practical-8

Draw sequence diagram of all use cases.

This UML sequence diagram of Patient Management System which shows the
interaction between the objects of Doctor, Doctor Schedule, Medicine, Test, Disease.
The instance of class objects involved in this UML Sequence Diagram of Patient
Management System are as follows:
● Doctor Object
● Doctor Schedule Object
● Medicine Object
● Test Object
● Disease Object

Login Sequence Diagram Of Patient Management System:

22
This is the Login Sequence Diagram of Patient Management System, where admin
will be able to login in their account using their credentials. After login, users can
manage all the operations on Medicine, Doctor, Doctor Schedule, Disease, Test. All
the pages such as Doctor Schedule, Disease, Test are secure and users can access these
page after login. The diagram below helps demonstrate how the login page works in a
Patient Management System.

23
24
 Practical-9

AIM : Draw collaboration diagram of all use cases.

Collaboration diagrams are also known as communication diagrams. They can demonstrate
how objects communicate to execute a specific use case's actions or an aspect of a use case.
Designers can use collaboration diagrams to explain and identify the roles of objects
performing a specific flow of events in a use case. They are the main information source used
to establish class roles and interfaces.

25
26
27
 Practical-10

Assign objects in sequence diagram to classes and make class diagram.

Patient Management System Class Diagram describes the structure of a Patient Management
System class, their attributes, operations (or methods), and the relationships among objects.
The main classes of the Patient Management System are Patient, Doctor, Doctor Schedule,
Disease, Test, Medicine.

Classes of Patient Management System Class Diagram:

● Patient Class: Manage all the operations of Patient
● Doctor Class : Manage all the operations of Doctor
● Doctor Schedule Class Manage all the operations of Doctor Schedule
● Disease Class : Manage all the operations of Disease
● Test Class : Manage all the operations of Test

28
 ● Medicine Class: Manage all the operations of Medicine

Classes and their attributes of Patient Management System Class Diagram:

● Patient Attributes: patient_id, patient_name, patient_mobile, patient_email,
patient_username, patient_password, patient_address,
● Doctor Attributes: doctor_id, doctor_name, doctor_specialist, doctor_mobile,
doctor_email, doctor_username, doctor_password, doctor_address
● Doctor Schedule Attributes: doctor_schedule_id, doctor_schedule_time,
doctor_schedule_type, doctor_schedule_date, doctor_schedule_description
● Disease Attributes: diease_id, diease_patient_id, diease_name,
diease_type, diease_description
● Test Attributes : test_id, test_patient_id, test_name, test_type, test_cost, test_report,
test_description
● Medicine Attributes: medicine_id, medicine_name, medicine_company,
medicine_composition, medicine_cost, medicine_type, medicine_dose,
medicine_description

Classes and their methods of Patient Management System Class Diagram:

● Patient Methods: addPatient(), editPatient(), deletePatient(), update Patient(),
savePatient(), searchPatient()
● Doctor Methods: addDoctor(), editDoctor(), deleteDoctor(), updateDoctor(),
saveDoctor(), searchDoctor()
● Doctor Schedule Methods: addDoctor Schedule(), editDoctor Schedule(),
deleteDoctor Schedule(), updateDoctor Schedule(), saveDoctorSchedule(),
searchDoctor Schedule()
● Disease Methods: addDisease(), editDisease(), deleteDisease(), updateDisease(),
saveDiease(), searchDisease()
● Test Methods: addTest(), editTest(), delete Test(), update Test(), save Test(), search
Test()
● Medicine Methods: addMedicine(), editMedicine(),
deleteMedicine(), updateMedicine(), saveMedicine(), searchMedicine()

29
30