SBM 4201: Project on Clinical Center Appointment System - Assessment 2

This project focuses on the design and development of a clinical center appointment system. It begins with use case descriptions for registering accounts and making appointments, followed by a use case diagram. The project then details the identification of entities and their attributes, culminating in an Entity-Relationship (ER) diagram. Further, it includes a class diagram, a sequence diagram, and an activity diagram to illustrate the system's behavior. A data entry screen design for personal details is also provided. Finally, the project outlines a testing and deployment plan, including reliability, usability, and performance testing to ensure the system's functionality and efficiency. The project aims to provide a productive and cost-effective way of arranging and assisting in all related activities within a clinical center.

SBM 4201 Assessment 2
1 | P a g e

Table of Contents
Introduction......................................................................................................................................3
1. Draw use case description for registering accounts and making an appointment.......................4
2. Draw use case diagram................................................................................................................5
3. Identify all entities and their attribute and draw an E-R (Entity-Relationship) diagram.............8
4. Draw the class diagram..............................................................................................................10
5. Draw a sequence diagram..........................................................................................................11
6. Draw activity diagram...............................................................................................................12
7. Design a data entry screen for entering personal details...........................................................13
8. Testing and deployment.............................................................................................................15
Summary........................................................................................................................................19
References......................................................................................................................................20

Introduction
The basic aim of this project is to build a site for a clinical center to provide a productive and
cost-effective way of arranging and assisting in all related activities: management of resources
and specialized records, co-operation board orientation and export arrangements for the patients.
Patients need to have quick and easy access to center administrations and monitor the large
number of contracts made. In the meantime, it is also essential that experts can see without
difficulty that all the emerging conditions and deliver the results of those conditions to patients.
1 | P a g e

1. Draw use case description for registering accounts and making an
appointment
Primary path
1. Users logged in to their registered accounts
2. System will verify users account through authentication
3. Users make an appointment by clicking on Book appointment option and after that date
option will appear; users will select day of the visit.
4. System will save appointment date and fees will be deducted from their added account
through sending OTP to user’s phone
5. User enter the OTP
6. Payment successfully done
7. Appointment booked Use case ends with success
Alternate Paths
1a. User gets an appointment but due to some reason wants to cancel the appointment
1. User searches through the log to find particular APPOINTMENT HISTORY
2. System displays screen requiring enter the detail of date for which information required
3. User selects the date from the date option and found the Booked Appointment and click on
Cancel button.
4. System confirms with user by displaying option ARE YOU SURE? YES NO
5. User confirms by either selecting Yes or No
6. For Yes System will cancel the appointment and will refund half of the booked amount in the
account of user automatically
7. For No System will take user to home screen.
8. Use case ends with success in canceling appointment
2 | P a g e

2. Draw use case diagram
Explanation
Guest user registration
While we list the records, in order to eliminate the registration process, we ask only the most
important data from the client. The main items required are: email, full name, secret key and
3 | P a g e

different patient confirmation card number. This number is the username that will be used to log
into the site. The various optional data can be filled in when the patient comes to a face-to-face
interview or by doing it without the support of anyone after enrolling in their registry.
Login
To log in, the patient must go to the "Login / Registration" page. After disabling the username
(patient DNI) and password, the patient must tap the Login button. If all the information
provided is correct, the patient will be signed in and logged into all uses of that account.
Edit your profile information
The client must be registered as any site worker (patient, expert or secretary) and get to the "Edit
Profile" page. The custom profile data will be displayed on the page and a customer will have the
option to switch to the new ones they need. After clicking Submit, the framework confirms all
new information provided. If DNI and email are not of the correct distribution, please notify the
customer about this and do not proceed with the accommodation of the structure. Also, if the
DNI and the new email are already present on another record, please tell the customer and do not
allow the facility configuration to continue. If a check is successful, the customer's data will be
carefully updated.
List all doctor’s appointments
To display the expert 's emerging arrangements or current arrangements, he should go to the
"Rundown Arrangements" page while enrolled in his register. Of course, the default settings will
be displayed in the same table using the table, which can be organized according to different
rules.
Search for specialists
Clients can scan a site for experts who work in the facility according to the different models. Not
all models need to be completed. A customer has to go to the "Search for Experts" page and fill
in the fields he finds basic (in this way the full entry is in the table above). On the off chance that
no fields are filled in, all experts will appear. Following the presentation of the study structure,
several experts reappear.
4 | P a g e

Make the appointment (patient)
To make the adjustment, the patient must be registered and accessed an adjustment sheet. First,
the patient should choose a specialist who can ensure that all specialists in this specialty are lost.
Shortly after, after selecting the specialist, the tablet will be shown to the patient with accessible
dates where the adjustment can be made. As a result of the selected date, all time limits will be
displayed. A patient will fill in the concerns (on the other hand), choose the time of
accommodation, whether this accommodation is for himself or for someone else (he / she can do
the accommodation for a family member. -This situation should identify the name patient) and
decide whether it is an improvement or an initial settlement. This will make it easier for the
specialist to deal with his patients. After a structure is left, a configuration is made which can be
found in the "My configurations" page.
Make a guest appointment
Some customers don't have a ton of idea how to use a PC / program, so they have a hard time
registering on sites. Also, there are customers who would rather not be bothered by signing up
for any part of the imagination. For this type of customer, we allow you to arrange up to 5
visitors at a time. The procedure is very similar for registered messengers, with the exception of
messengers who have not been contacted to indicate who this agreement is for. To identify the
number of contracts entered into by the identified customer, we use his IP address as quality. If 5
have just been made, we will not allow the patient to schedule further visits until he or she goes
to a portion of these visits or to record a record.
List all appointments of the patient
To display the next patient situations, the patient must access the "My dispositions" page while
enrolled in their register. All provisions will be displayed on a page with exchange and release
agreement captures.
Cancel appointment
To cancel the consent, the patient must be listed in his or her register and, as a key consideration,
list all his or her consent and, next to the consent that a patient must cancel delete, click Cancel
5 | P a g e

Agreement. There will be a confirmation before it is canceled in the event that a patient
accidentally hit the socket.
3. Identify all entities and their attribute and draw an E-R (Entity-
Relationship) diagram
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 Appointment System are Doctors
Appointment, Booking, Fees, schedule and Clinics.
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.
6 | P a g e

 The entity Booking, schedule has bonded 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 duplicity
of records
E-R Diagram for appointment
7 | P a g e

4. Draw the class diagram
8 | P a g e

5. Draw a sequence diagram
9 | P a g e

6. Draw activity diagram
10 | P a g e