Doctor Appointment System UML Diagram

Posted By freeproject on March 19, 2018

Doctor Appointment System Activity Diagram

Posted By freeproject on March 13, 2018

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

  • Test Activity
  • schedule Activity
  • Doctors Activity
  • Appointment Activity
  • Fees Activity

Features of the Activity UML diagram of Doctor Appointment System

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

Doctor Appointment System Class Diagram

Posted By freeproject on August 2, 2017

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

Classes of Doctor Appointment System Class Diagram:

  • Doctors Class : Manage all the operations of Doctors
  • Appointment Class : Manage all the operations of Appointment
  • Booking Class : Manage all the operations of Booking
  • Fees Class : Manage all the operations of Fees
  • schedule Class : Manage all the operations of schedule
  • Clinics Class : Manage all the operations of Clinics

Classes and their attributes of Doctor Appointment System Class Diagram:

  • Doctors Attributes : doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
  • Appointment Attributes : appointment_id, appointment_doctor_id, appointment_number, appointment_type, appointment_date, appointment_description
  • Booking Attributes : booking_id, booking_title, booking_type, booking_appointment, booking_date, booking_description
  • Fees Attributes : doctor_fee_id, doctor_fee_doctor_id, doctor_fee_amount, doctor_fee_total, doctor_fee_payment, doctor_fee_type, doctor_fee_description
  • schedule Attributes : doctor_schedule_id, doctor_schedule_time, doctor_schedule_type, doctor_schedule_date, doctor_schedule_description
  • Clinics Attributes : clinic_id, clinic_doctor_id, clinic_name, clinic_place, clinic_type, clinic_description, clinic_address

Classes and their methods of Doctor Appointment System Class Diagram:

  • Doctors Methods : addDoctors(), editDoctors(), deleteDoctors(), updateDoctors(), saveDoctors(), searchDoctors()
  • Appointment Methods : addAppointment(), editAppointment(), deleteAppointment(), updateAppointment(), saveAppointment(), searchAppointment()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Fees Methods : addFees(), editFees(), deleteFees(), updateFees(), saveFees(), searchFees()
  • schedule Methods : addschedule(), editschedule(), deleteschedule(), updateschedule(), saveschedule(), searchschedule()
  • Clinics Methods : addClinics(), editClinics(), deleteClinics(), updateClinics(), saveClinics(), searchClinics()

Class Diagram of Doctor Appointment System :

Class Diagram Image: 
Doctor Appointment System Class Diagram

Doctor Appointment System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Doctor Appointment System:

  • Fees Component
  • schedule Component
  • Doctors Component
  • Appointment Component
  • Test Component

Featues of Doctor Appointment System Component Diagram:

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

Doctor Appointment System Dataflow Diagram

Posted By freeproject on April 18, 2017

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


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

This is the Zero Level DFD of Doctor Appointment System, where we have eloborated the high level process of Doctor Appointment. It’s a basic overview of the whole Doctor Appointment System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Timeslot,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 Timeslot In zero leve DFD of Doctor Appointment System, we have described the high level flow of the Doctor Appointment system.

High Level Entities and proccess flow of Doctor Appointment System:

  • Managing all the Doctor
  • Managing all the Appointment
  • Managing all the Booking
  • Managing all the Patient
  • Managing all the Timeslot
  • Managing all the Patient
  • Managing all the Medicine
Zero Level DFD Doctor Appointment System

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

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

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 Patient records and generate report of all Patient
  • Processing Timeslot records and generate report of all Timeslot
  • Processing Patient records and generate report of all Patient
  • Processing Medicine records and generate report of all Medicine
First Level DFD Doctor Appointment System

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

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

Low level functionalities of Doctor Appointment System

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

Doctor Appointment System ER Diagram

Posted By freeproject on July 17, 2017

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

Doctor Appointment System entities and their attributes :

  • Doctors Entity : Attributes of Doctors are doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
  • Appointment Entity : Attributes of Appointment are appointment_id, appointment_doctor_id, appointment_number, appointment_type, appointment_date, appointment_description
  • Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_appointment, booking_date, booking_description
  • Fees Entity : Attributes of Fees are doctor_fee_id, doctor_fee_doctor_id, doctor_fee_amount, doctor_fee_total, doctor_fee_payment, doctor_fee_type, doctor_fee_description
  • schedule Entity : Attributes of schedule are doctor_schedule_id, doctor_schedule_time, doctor_schedule_type, doctor_schedule_date, doctor_schedule_description
  • Clinics Entity : Attributes of Clinics are clinic_id, clinic_doctor_id, clinic_name, clinic_place, clinic_type, clinic_description, clinic_address

Description of Doctor Appointment System Database :

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

Doctor Appointment System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Doctor Appointment System which shows the interaction between the objects of Appointment, schedule, Fees, Test, Doctors. The instance of class objects involved in this UML Sequence Diagram of Doctor Appointment System are as follows:

  • Appointment Object
  • schedule Object
  • Fees Object
  • Test Object
  • Doctors Object

This is the UML sequence diagram of Doctor Appointment System which shows the interaction between the objects of Appointment, schedule, Fees, Test, Doctors. The instance of class objects involved in this UML Sequence Diagram of Doctor Appointment System are as follows:

  • Appointment Object
  • schedule Object
  • Fees Object
  • Test Object
  • Doctors Object

Doctor 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 Doctor Appointment System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Doctor Appointment System. The main actors of Doctor 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 Doctors, Manage Appointment, Manage Booking, Manage Fees, Manage schedule, Manage Clinics, Manage Users and Full Doctor Appointment System Operations. Major elements of the UML use case diagram of Doctor Appointment System are shown on the picture below.

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

  • Super Admin Entity : Use cases of Super Admin are Manage Doctors, Manage Appointment, Manage Booking, Manage Fees, Manage schedule, Manage Clinics, Manage Users and Full Doctor Appointment System Operations
  • System User Entity : Use cases of System User are Manage Doctors, Manage Appointment, Manage Booking, Manage Fees, Manage schedule, Manage Clinics
  • Doctor Entity : Use cases of Doctor are Check Appointments, Create Prescriptions, Search Patient, Appointment History
  • Patient Entity : Use cases of Patient are Request for Appointments, Check Appointment Status, Make Payment

Use Case Diagram of Doctor Appointment System :

Doctor Appointment System Use Case Diagram

Project Category