Clinic Appointment System UML Diagram

Posted By freeproject on March 18, 2018

Clinic Appointment System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Clinic Appointment System which shows the flows between the activity of Appointments, Doctor Fees, Doctors, Booking, Doctor Schedule. The main activity involved in this UML Activity Diagram of Clinic Appointment System are as follows:

  • Appointments Activity
  • Doctor Fees Activity
  • Doctors Activity
  • Booking Activity
  • Doctor Schedule Activity

Features of the Activity UML diagram of Clinic Appointment System

  • Admin User can search Appointments, view description of a selected Appointments, add Appointments, update Appointments and delete Appointments.
  • Its shows the activity flow of editing, adding and updating of Doctor Fees
  • User will be able to search and generate report of Doctors, Booking, Doctor Schedule
  • All objects such as ( Appointments, Doctor Fees, Doctor Schedule) are interlinked
  • Its shows the full description and flow of Appointments, Booking, Doctor Schedule, Doctors, Doctor Fees
Clinic Appointment System Activity Diagram

Clinic Appointment System Class Diagram

Posted By freeproject on August 2, 2017

Clinic Appointment System Class Diagram describes the structure of a Clinic Appointment System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Clinic Appointment System are Clinic, Patient, Doctors, Booking, Appointments, Doctor Schedule.

Classes of Clinic Appointment System Class Diagram:

  • Clinic Class : Manage all the operations of Clinic
  • Patient Class : Manage all the operations of Patient
  • Doctors Class : Manage all the operations of Doctors
  • Booking Class : Manage all the operations of Booking
  • Appointments Class : Manage all the operations of Appointments
  • Doctor Schedule Class : Manage all the operations of Doctor Schedule

Classes and their attributes of Clinic Appointment System Class Diagram:

  • Clinic Attributes : clinic_id, clinic_doctor_id, clinic_name, clinic_place, clinic_type, clinic_description, clinic_address
  • Patient Attributes : patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
  • Doctors Attributes : doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
  • Booking Attributes : booking_id, booking_patient_id, booking_number, booking_type, booking_appointment, booking_date, booking_description
  • Appointments Attributes : appointment_id, appointment_doctor_id, appointment_number, appointment_type, appointment_date, appointment_description
  • Doctor Schedule Attributes : doctor_schedule_id, doctor_schedule_time, doctor_schedule_type, doctor_schedule_date, doctor_schedule_description

Classes and their methods of Clinic Appointment System Class Diagram:

  • Clinic Methods : addClinic(), editClinic(), deleteClinic(), updateClinic(), saveClinic(), searchClinic()
  • Patient Methods : addPatient(), editPatient(), deletePatient(), updatePatient(), savePatient(), searchPatient()
  • Doctors Methods : addDoctors(), editDoctors(), deleteDoctors(), updateDoctors(), saveDoctors(), searchDoctors()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Appointments Methods : addAppointments(), editAppointments(), deleteAppointments(), updateAppointments(), saveAppointments(), searchAppointments()
  • Doctor Schedule Methods : addDoctor Schedule(), editDoctor Schedule(), deleteDoctor Schedule(), updateDoctor Schedule(), saveDoctor Schedule(), searchDoctor Schedule()

Class Diagram of Clinic Appointment System :

Class Diagram Image: 
Clinic Appointment System Class Diagram

Clinic Appointment System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Clinic Appointment System which shows components, provided and required interfaces, ports, and relationships between the Patient, Appointments, Doctor Fees, Doctors and Clinic. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Clinic Appointment System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Clinic Appointment System:

  • Patient Component
  • Appointments Component
  • Doctor Fees Component
  • Doctors Component
  • Clinic Component

Featues of Clinic Appointment System Component Diagram:

  • You can show the models the components of Clinic Appointment System.
  • Model the database schema of Clinic Appointment System
  • Model the executables of an application of Clinic Appointment System
  • Model the system's source code of Clinic Appointment System
Component Diagram: 

Clinic Appointment System Dataflow Diagram

Posted By freeproject on April 14, 2017

Clinic Appointment System Data flow diagram is often used as a preliminary step to create an overview of the Clinic without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Clinic process. It contains all of the userflow and their entities such all the flow of Doctor, Appointment, Booking, Doctor Fees, Doctor Shedule, Patient, Medicine. All of the below diagrams has been used for the visualization of data processing and structured design of the Clinic process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Clinic Appointment System :

This is the Zero Level DFD of Clinic Appointment System, where we have eloborated the high level process of Clinic. It’s a basic overview of the whole Clinic Appointment System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Doctor Shedule,Patient and Medicine showing the system as a single high-level process, with its relationship to external entities of Doctor,Appointment and Booking. It should be easily understood by a wide audience, including Doctor,Booking and Doctor Shedule In zero leve DFD of Clinic Appointment System, we have described the high level flow of the Clinic system.

High Level Entities and proccess flow of Clinic Appointment System:

  • Managing all the Doctor
  • Managing all the Appointment
  • Managing all the Booking
  • Managing all the Doctor Fees
  • Managing all the Doctor Shedule
  • Managing all the Patient
  • Managing all the Medicine
Zero Level DFD Clinic Appointment System

First Level Data flow Diagram(1st Level DFD) of Clinic Appointment System :

First Level DFD (1st Level) of Clinic Appointment System shows how the system is divided into sub-systems (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 Clinic Appointment System system as a whole. It also identifies internal data stores of Medicine, Patient, Doctor Shedule, Doctor Fees, Booking that must be present in order for the Clinic system to do its job, and shows the flow of data between the various parts of Doctor, Booking, Patient, Medicine, Doctor Shedule 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 Clinic.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Doctor records and generate report of all Doctor
  • Processing Appointment records and generate report of all Appointment
  • Processing Booking records and generate report of all Booking
  • Processing Doctor Fees records and generate report of all Doctor Fees
  • Processing Doctor Shedule records and generate report of all Doctor Shedule
  • Processing Patient records and generate report of all Patient
  • Processing Medicine records and generate report of all Medicine
First Level DFD Clinic Appointment System

Second Level Data flow Diagram(2nd Level DFD) of Clinic Appointment System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Clinic. It may require more functionalities of Clinic to reach the necessary level of detail about the Clinic functioning. First Level DFD (1st Level) of Clinic Appointment System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Medicine, Patient, Doctor Shedule, Doctor Fees, Booking, Appointment, Doctor.

Low level functionalities of Clinic Appointment System

  • Admin logins to the system and manage all the functionalities of Clinic Appointment System
  • Admin can add, edit, delete and view the records of Doctor, Booking, Doctor Shedule, Medicine
  • Admin can manage all the details of Appointment, Doctor Fees, Patient
  • Admin can also generate reports of Doctor, Appointment, Booking, Doctor Fees, Doctor Shedule, Patient
  • Admin can search the details of Appointment, Doctor Shedule, Patient
  • Admin can apply different level of filters on report of Doctor, Doctor Fees, Doctor Shedule
  • Admin can tracks the detailed information of Appointment, Booking, Doctor Fees, , Doctor Shedule
Second Level DFD Clinic Appointment System

Clinic Appointment System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Clinic Appointment System Entity. The entity-relationship diagram of Clinic Appointment System shows all the visual instrument of database tables and the relations between Patient, Booking, Clinic, Doctor Schedule etc. It used structure data and to define the relationships between structured data groups of Clinic Appointment System functionalities. The main entities of the Clinic Appointment System are Clinic, Patient, Doctors, Booking, Appointments and Doctor Schedule.

Clinic Appointment System entities and their attributes :

  • Clinic Entity : Attributes of Clinic are clinic_id, clinic_doctor_id, clinic_name, clinic_place, clinic_type, clinic_description, clinic_address
  • Patient Entity : Attributes of Patient are patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
  • Doctors Entity : Attributes of Doctors are doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
  • Booking Entity : Attributes of Booking are booking_id, booking_patient_id, booking_number, booking_type, booking_appointment, booking_date, booking_description
  • Appointments Entity : Attributes of Appointments are appointment_id, appointment_doctor_id, appointment_number, appointment_type, appointment_date, appointment_description
  • Doctor Schedule Entity : Attributes of Doctor Schedule are doctor_schedule_id, doctor_schedule_time, doctor_schedule_type, doctor_schedule_date, doctor_schedule_description

Description of Clinic Appointment System Database :

  • The details of Clinic is store into the Clinic tables respective with all tables
  • Each entity (Doctor Schedule, Doctors, Appointments, Patient, Clinic) contains primary key and unique keys.
  • The entity Doctors, Appointments has binded with Clinic, Patient entities with foreign key
  • There is one-to-one and one-to-many relationships available between Appointments, Booking, Doctor Schedule, Clinic
  • All the entities Clinic, Appointments, Doctors, Doctor Schedule are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Clinic Appointment System tables for fast query execution.
Clinic Appointment System ER Diagram

Clinic Appointment System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Clinic Appointment System which shows the interaction between the objects of Patient, Appointments, Doctor Schedule, Doctor Fees, Booking. The instance of class objects involved in this UML Sequence Diagram of Clinic Appointment System are as follows:

  • Patient Object
  • Appointments Object
  • Doctor Schedule Object
  • Doctor Fees Object
  • Booking Object

This is the UML sequence diagram of Clinic Appointment System which shows the interaction between the objects of Patient, Appointments, Doctor Schedule, Doctor Fees, Booking. The instance of class objects involved in this UML Sequence Diagram of Clinic Appointment System are as follows:

  • Patient Object
  • Appointments Object
  • Doctor Schedule Object
  • Doctor Fees Object
  • Booking Object

Clinic Appointment System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of Clinic Appointment System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Clinic Appointment System. The main actors of Clinic Appointment System in this Use Case Diagram are: Super Admin, System User, Doctor, Patient, who perform the different type of use cases such as Manage Clinic, Manage Patient, Manage Doctors, Manage Booking, Manage Appointments, Manage Doctor Schedule, Manage Doctor Fees, Manage Users and Full Clinic Appointment System Operations. Major elements of the UML use case diagram of Clinic Appointment System are shown on the picture below.

The relationships between and among the actors and the use cases of Clinic Appointment System:

  • Super Admin Entity : Use cases of Super Admin are Manage Clinic, Manage Patient, Manage Doctors, Manage Booking, Manage Appointments, Manage Doctor Schedule, Manage Doctor Fees, Manage Users and Full Clinic Appointment System Operations
  • System User Entity : Use cases of System User are Manage Clinic, Manage Patient, Manage Doctors, Manage Booking, Manage Appointments, Manage Doctor Schedule, Manage Doctor Fees
  • Doctor Entity : Use cases of Doctor are Check Appointments, Create Prescriptions, Add Tests, Add Medicines, View Appointments
  • Patient Entity : Use cases of Patient are Create Appointments, Make Payments, View Prescriotion, View Tests, View Medicines

Use Case Diagram of Clinic Appointment System :

 Clinic Appointment System Use Case Diagram

Project Category