UML Diagram For Hospital Management System
UML Diagram For Hospital Management System
We’ve compiled two types of structural UML diagrams i.e. class and component diagrams, and
three types of behavioral UML diagrams i.e. activity, sequence, and use case diagrams for the
Hospital Management Project.
This application is a web platform to handle and manage all the activity and maintain and
centralize a database about the hospital information that will be easily available with just one
click on the web.
The component diagram below shows the structural relations between components in an online
Hospital Management System. The connected components by dotted lines represent relationships
within the systems.
In the diagram, it can be seen that there total of six components name Patient, Appointment,
Receptionist, Doctor, Appointment List, and Patient List.
Here, Admin can add/delete/edit Doctor details, and Receptionist details. Admin can view
different users list. Doctors can view the appointment in the appointment and patients’ list. A
receptionist can add/view the details of patients on the patient list. Admin can add/delete/edit
appointments in the appointments list.
Activity diagram for Hospital Management Project
Activity diagrams in UML are a leading subset of behavioural diagrams. They display the
functionalities of various activities and flows in management processes and software systems.
The flow in the activity diagram can be sequential, branched, or concurrent.
Admin being the primary user, have to register on the system to carry out further operations of a
Hospital. Admin will solely be responsible for adding receptionists, appointments, patients, and
doctors. Admin can view the doctor list, appointments list, etc.
The Receptionist can log in and add/view patient details. Doctors can view appointments and
patients list after logging in to the system.
Admin can add/delete/edit Doctor details, and Receptionist details. Admin can view different
users list. Doctors can view the appointment in the appointment and patients’ list. A receptionist
can add/view the details of patients on the patient list. Admin can add/delete/edit appointments in
the appointments list.
Admin will be able to keep the records of all the medical history of patients. Details like name,
address, photos, lab test reports, scans, diagnoses, and so on can be managed by the admin.
As you can see from the examples below, use cases are represented by oval shapes, and the lines
then show at which point an actor/user participates and interacts with their corresponding use
case. We can see where each actor is involved within the entire process (and where they’re
excluded).
Admin can access add/view doctor and doctor list use cases. Admin can access adds/view
receptionist and receptionist list use cases. Admin can access adds/views patients and patients list
use cases. Whereas the Receptionist can access add/view patient details use cases. Doctors can
access view appointments and patients list use cases after logging in to the system.
Admin will solely be responsible for adding receptionists, appointments, patients, and doctors.
Admin can view the doctor list, appointments list, etc. Admin can add/delete/edit Doctor details,
and Receptionist details. Admin can view different users list. Doctors can view the appointment
in the appointment and patients’ list. A receptionist can add/view the details of patients on the
patient list. Admin can add/delete/edit appointments in the appointments list.