- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System Activity Diagram
This is the Activity UML diagram of Eye Care Appoitment System which shows the flows between the activity of Test, Doctor Schedule, Patient, Appointment, Booking. The main activity involved in this UML Activity Diagram of Eye Care Appoitment System are as follows:
- Test Activity
- Doctor Schedule Activity
- Patient Activity
- Appointment Activity
- Booking Activity
Features of the Activity UML diagram of Eye Care Appoitment 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 Doctor Schedule
- User will be able to search and generate report of Patient, Appointment, Booking
- All objects such as ( Test, Doctor Schedule, Booking) are interlinked
- Its shows the full description and flow of Test, Appointment, Booking, Patient, Doctor Schedule
Login Activity Diagram of Eye Care Appoitment System:
This is the Login Activity Diagram of Eye Care Appoitment System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Patient, Test, Doctor Schedule, Booking, Appointment. All the pages such as Doctor Schedule, Booking, Appointment are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Eye Care Appoitment System. The various objects in the Booking, Patient, Test, Doctor Schedule, and Appointment page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System Class Diagram
Eye Care Appoitment System Class Diagram describes the structure of a Eye Care Appoitment System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Eye Care Appoitment System are Doctor, Patient, Test, Spectacles, Appointment, Booking.
Classes of Eye Care Appoitment System Class Diagram:
- Doctor Class : Manage all the operations of Doctor
- Patient Class : Manage all the operations of Patient
- Test Class : Manage all the operations of Test
- Spectacles Class : Manage all the operations of Spectacles
- Appointment Class : Manage all the operations of Appointment
- Booking Class : Manage all the operations of Booking
Classes and their attributes of Eye Care Appoitment System Class Diagram:
- Doctor Attributes : doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
- Patient Attributes : patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
- Test Attributes : test_id, test_patient_id, test_name, test_type, test_cost, test_report, test_description
- Spectacles Attributes : spectacle_id, spectacle_patient_id, spectacle_number, spectacle_type, spectacle_description
- Appointment Attributes : appointment_id, appointment_doctor_id, appointment_number, appointment_type, appointment_date, appointment_description
- Booking Attributes : booking_id, booking_title, booking_type, booking_appointmnet booking_date, booking_description
Classes and their methods of Eye Care Appoitment System Class Diagram:
- Doctor Methods : addDoctor(), editDoctor(), deleteDoctor(), updateDoctor(), saveDoctor(), searchDoctor()
- Patient Methods : addPatient(), editPatient(), deletePatient(), updatePatient(), savePatient(), searchPatient()
- Test Methods : addTest(), editTest(), deleteTest(), updateTest(), saveTest(), searchTest()
- Spectacles Methods : addSpectacles(), editSpectacles(), deleteSpectacles(), updateSpectacles(), saveSpectacles(), searchSpectacles()
- Appointment Methods : addAppointment(), editAppointment(), deleteAppointment(), updateAppointment(), saveAppointment(), searchAppointment()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
Class Diagram of Eye Care Appoitment System :
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System Component Diagram
This is a Component diagram of Eye Care Appoitment System which shows components, provided and required interfaces, ports, and relationships between the Doctor, Test, Booking, Patient and Doctor Schedule. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Eye Care Appoitment System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Eye Care Appoitment System:
- Doctor Component
- Test Component
- Booking Component
- Patient Component
- Doctor Schedule Component
Featues of Eye Care Appoitment System Component Diagram:
- You can show the models the components of Eye Care Appoitment System.
- Model the database schema of Eye Care Appoitment System
- Model the executables of an application of Eye Care Appoitment System
- Model the system's source code of Eye Care Appoitment System
- Posted By: freeproject
- Comments: 0
Eye Care Appointment System Dataflow Diagram
Eye Care Appointment System Data flow diagram is often used as a preliminary step to create an overview of the Eye Care without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Eye Care process. It contains all of the userflow and their entities such all the flow of Doctor, Patient, Test, Spectacles, Appointment, Booking, Doctor Shedule. All of the below diagrams has been used for the visualization of data processing and structured design of the Eye Care process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Eye Care Appointment System :
This is the Zero Level DFD of Eye Care Appointment System, where we have eloborated the high level process of Eye Care. It’s a basic overview of the whole Eye Care Appointment System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Appointment,Booking and Doctor Shedule showing the system as a single high-level process, with its relationship to external entities of Doctor,Patient and Test. It should be easily understood by a wide audience, including Doctor,Test and Appointment In zero leve DFD of Eye Care Appointment System, we have described the high level flow of the Eye Care system.High Level Entities and proccess flow of Eye Care Appointment System:
- Managing all the Doctor
- Managing all the Patient
- Managing all the Test
- Managing all the Spectacles
- Managing all the Appointment
- Managing all the Booking
- Managing all the Doctor Shedule
First Level Data flow Diagram(1st Level DFD) of Eye Care Appointment System :
First Level DFD (1st Level) of Eye Care 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 Eye Care Appointment System system as a whole. It also identifies internal data stores of Doctor Shedule, Booking, Appointment, Spectacles, Test that must be present in order for the Eye Care system to do its job, and shows the flow of data between the various parts of Doctor, Test, Booking, Doctor Shedule, Appointment 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 Eye Care.Main entities and output of First Level DFD (1st Level DFD):
- Processing Doctor records and generate report of all Doctor
- Processing Patient records and generate report of all Patient
- Processing Test records and generate report of all Test
- Processing Spectacles records and generate report of all Spectacles
- Processing Appointment records and generate report of all Appointment
- Processing Booking records and generate report of all Booking
- Processing Doctor Shedule records and generate report of all Doctor Shedule
Second Level Data flow Diagram(2nd Level DFD) of Eye Care Appointment System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Eye Care. It may require more functionalities of Eye Care to reach the necessary level of detail about the Eye Care functioning. First Level DFD (1st Level) of Eye Care Appointment System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Doctor Shedule, Booking, Appointment, Spectacles, Test, Patient, Doctor.Low level functionalities of Eye Care Appointment System
- Admin logins to the system and manage all the functionalities of Eye Care Appointment System
- Admin can add, edit, delete and view the records of Doctor, Test, Appointment, Doctor Shedule
- Admin can manage all the details of Patient, Spectacles, Booking
- Admin can also generate reports of Doctor, Patient, Test, Spectacles, Appointment, Booking
- Admin can search the details of Patient, Appointment, Booking
- Admin can apply different level of filters on report of Doctor, Spectacles, Appointment
- Admin can tracks the detailed information of Patient, Test, Spectacles, , Appointment
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Eye Care Appoitment System Entity. The entity-relationship diagram of Eye Care Appoitment System shows all the visual instrument of database tables and the relations between Patient, Spectacles, Doctor, Booking etc. It used structure data and to define the relationships between structured data groups of Eye Care Appoitment System functionalities. The main entities of the Eye Care Appoitment System are Doctor, Patient, Test, Spectacles, Appointment and Booking.
Eye Care Appoitment System entities and their attributes :
- Doctor Entity : Attributes of Doctor are doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
- Patient Entity : Attributes of Patient are patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
- Test Entity : Attributes of Test are test_id, test_patient_id, test_name, test_type, test_cost, test_report, test_description
- Spectacles Entity : Attributes of Spectacles are spectacle_id, spectacle_patient_id, spectacle_number, spectacle_type, spectacle_description
- 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_appointmnet booking_date, booking_description
Description of Eye Care Appoitment System Database :
- The details of Doctor is store into the Doctor tables respective with all tables
- Each entity (Booking, Test, Appointment, Patient, Doctor) contains primary key and unique keys.
- The entity Test, Appointment has binded with Doctor, Patient entities with foreign key
- There is one-to-one and one-to-many relationships available between Appointment, Spectacles, Booking, Doctor
- All the entities Doctor, Appointment, Test, Booking are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Eye Care Appoitment System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System Sequence Diagram
This is the UML sequence diagram of Eye Care Appoitment System which shows the interaction between the objects of Doctor, Spectacles, Booking, Test, Patient. The instance of class objects involved in this UML Sequence Diagram of Eye Care Appoitment System are as follows:
- Doctor Object
- Spectacles Object
- Booking Object
- Test Object
- Patient Object
Login Sequence Diagram of Eye Care Appoitment System:
This is the Login Sequence Diagram of Eye Care Appoitment System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Booking, Doctor, Spectacles, Patient, Test. All the pages such as Spectacles, Patient, Test are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Eye Care Appoitment System. The various objects in the Patient, Booking, Doctor, Spectacles, and Test page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Eye Care Appoitment System which shows the interaction between the objects of Doctor, Spectacles, Booking, Test, Patient. The instance of class objects involved in this UML Sequence Diagram of Eye Care Appoitment System are as follows:
- Doctor Object
- Spectacles Object
- Booking Object
- Test Object
- Patient Object
- Posted By: freeproject
- Comments: 0
Eye Care Appoitment System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Eye Care Appoitment System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Eye Care Appoitment System. The main actors of Eye Care Appoitment System in this Use Case Diagram are: Super Admin, System User, Doctor, Patient, who perform the different type of use cases such as Manage Doctor, Manage Patient, Manage Test, Manage Spectacles, Manage Appointment, Manage Booking, Manage Doctor Schedule, Manage Users and Full Eye Care Appoitment System Operations. Major elements of the UML use case diagram of Eye Care Appoitment System are shown on the picture below.
The relationships between and among the actors and the use cases of Eye Care Appoitment System:
- Super Admin Entity : Use cases of Super Admin are Manage Doctor, Manage Patient, Manage Test, Manage Spectacles, Manage Appointment, Manage Booking, Manage Doctor Schedule, Manage Users and Full Eye Care Appoitment System Operations
- System User Entity : Use cases of System User are Manage Doctor, Manage Patient, Manage Test, Manage Spectacles, Manage Appointment, Manage Booking, Manage Doctor Schedule
- Doctor Entity : Use cases of Doctor are Check Patient Appointment, Add Patient Problems, Create Prescriptions, Add Tests, Add Medicines
- Patient Entity : Use cases of Patient are Request for Appointments, Check Prescription, Make Payment, Check Appointment History
Use Case Diagram of Eye Care Appoitment System :
