System Analysis and Design

This report covers the second stage of system analysis and design, focusing on the designing of a digital management system for a dental care practice. It includes use case diagrams, class diagrams, interaction diagrams, and provides a comprehensive understanding of the importance of system analysis and design in software development.

System Analysis and
Design

Table of Contents
INTRODUCTION...........................................................................................................................1
MAIN BODY...................................................................................................................................1
Use case diagram....................................................................................................................1
Use case documentation.........................................................................................................2
Class diagram.........................................................................................................................7
Interaction diagrams...............................................................................................................8
CONCLUSION..............................................................................................................................11
References:.....................................................................................................................................12

INTRODUCTION
System analysis and design can be defined as the development of software and
application related to any management system to improve the operations of an organization
(Davis and Yen, 2019). It involves various stages of software development life cycle such as first
it is planned and analyse the requirements of the software, secondly it is designed on pen paper,
thirdly it is to be developed and programmed through coding, fourthly it is tested to detect errors,
fifthly it deployed to the client or for personal use and sixthly it is maintained to update
frequently for safety and security of the system (Qianyi, Xiaoshun, Ping and Lu, 2018). This
report is covering the second stage that is the designing of the digital management system for
Priory Central Dental Care Practice by Harborne council as per the scenario given. The
following discussion is made on the use case diagram, class diagram, sequence diagram and
activity diagram with proper findings and conclusion.
MAIN BODY
Use case diagram
Functional requirements
Harborne council has developed a new Central Dental Care Practice in the city and they
want to built a Digital Management System (DMS) that permits the employees and patients to
operate it comfortably and conveniently. The software must have the functional requirements
such as : system must record all the information of the patients like their private and reservation
details including name, date of birth, contact number, their joining date, their check up date and
many more which are necessarily important to record. Admins should be capable to discover,
remove and modify patient's information including reservation and nullification of appointments.
It should also be easy for the patients to modify their contact number themselves and to make
and cancel bookings online which means self online updates. If a patient is early for some time
for the reservation, the software should offset it and should inform the admin mechanically or
automatically (Pedrycz, 2018). Managers should be capable to manage the logistics and
instrumentality of the treatment and should be capable to upgrade the software with all accessible
instruments and devices needed to treat people. Also, they should be capable to nominate
substitutive doctors in case the daily doctor is lacking. It should also be achievable to create a
1

full written report on all of the reservations to admins and managers at any 1 point collectively
with all of the nullifications taking place.
Diagram
Use case documentation
Case description
Assumptions made are as follows:
 Cancel appointment as well as change appointment is also added in this system
 If there is no available time slot for the patient, then receptionist ask for the change for
the same
 A treatment is given to the patient if any medicine is needed after the prescription
 Outstanding bill contains letter and reminder postcard are kept exterior of the system
 UML Personal edition is used to fulfil the needs of the systems for all the diagrams
2

Use cases which are used by primary actors are as follows:
Patient: Request Appointment in which the Patient query for a new appointment or alter an
existing appointment or nullify the current appointment and request Payment in which the
Patient pays the amount for getting the dental facilities.
Receptionist: Administer Patient’s details in which the Receptionist creates new patient and
upgrades current patient information concerning an appointment is made by the Patient and
prepare Schedule in which the Administrator monitors the schedule for the patient’s appointment
with the accessibility of dentist and confirms the same.
Dentist: Manage Treatment in which the Dentist treats the patient in time based manner and
upgrade the treatment information in the system and Record Accessibility in which the Dentist
upgrades the accessibility into the systems to generate schedule for the patient’s appointment.
Use Case Name: Request Appointment ID: 1 Importance Level: High
Primary Actor: Patient Use Case Type: Detail, essential
Stakeholders and Interests:
Patient: interested to alter or nullify the appointment for the dental facilities
Dentist: desires to ensure patient’s dental issue has been checked on time
Brief Description: This use case defines that how it can request an appointment as well as
nullifying or altering an appointment also.
Trigger: Patient contacts and request for a fresh appointment or request to change or cancel a
current appointment
Type: External
3

Relationships:
Association: Patient
Include: generate New Patient
Extend: upgrade Patient information
Generalisation: Making appointment of fresh Patient, Making appointment of existing
Patient.
Standard Flow of Events:
1. The Patient interacts the Harborne Council about an appointment
2. The Patient renders the Administrator with their name and other basic details
3. The Administrator maintains that the Patient information in the Patient’s database
management system
4. The Receptionist request the Patient if they are interested to make a new appointment or
cancel a current appointment or alter a current appointment
If the Patient is interested to make a New Appointment then,
The S-1: New appointment sub-flow is performed
If the Patient wants to nullify a current Appointment then,
The S-2: Cancel appointment sub-flow is performed
If the Patient wants to change an existing Appointment then,
The S-3: Change appointment sub-flow is performed
5. The Receptionist provides the results of the transaction to the Patient
Sub-Flows:
S-1: New Appointment
1. The Receptionist request the Patient for appointment times that are comfortable for
them
2. The Receptionist matches the Patient desired appointment times with available date
and times
3. if a timeslot is found then
4

3.1 scheduling the new appointment and confirm the Patients
4. Else
4.1 The Receptionist request the Patient for other appointment times
4.2 The Receptionist duplicates the tasks 2-4 from this sub-flow S-1
S-2: Cancel Appointment
1. The Receptionist request the Patient for the old appointment time
2. The Receptionist find the Patient’s existing appointment in the appointment file and
nullifies it
S-3: Change Appointment
1. The Receptionist executes the S-2: nullifies appointment sub-flow
2. The Receptionist performs the S-1: New appointment sub-flow
Alternative/Exceptional Flows:
3.1a: The Receptionist executes the Create New Patient use case.
S-1, 4.1a1: The receptionist also sets some other appointment times based on what is present
in the schedule of appointment
S-1, 4.1a2: The Patient selects one of the planned times or chooses not to make selection
Use Case Name: Make Payment ID: 2 Importance Level: High
Primary Actor: Patient Use Case Type: Detail, essential
Stakeholders and Interests:
Patient: desires to pay for the for the dental services acknowledged from the surgery
Receptionist: wants to ensure patient’s pays the right amount of money
Brief Description: This use case describes how to pay for the dental services received by
making an appointment.
Trigger: Receptionist generate bill for the service and ask patient for paying the bill
5

Type: External
Relationships:
Association: Patient
Include: Generate Bill
Extend: N/A
Generalisation: N/A
Normal Flow of Events:
1. The Patient comes to surgery to see the dentist according to their appointment
2. The Patient is seen by a dentist and get treatment
3. The Receptionist asks the Patient if he or she would like to pay now for the treatment
If the Patient wants to pay full amount then,
The S-1: Full Payment sub-flow is performed
If the Patient wants to pay partly then,
The S-2: Part Payment sub-flow is performed
If the Patient wants to pay later,
The S-3: Outstanding Payment sub-flow is performed
4. The Receptionist generate receipt for the payment and handed to the patient
Sub-Flows:
S-1: Complete Payment
1. The Receptionist creates Bill
2. The Receptionist generates the bill in full
S-2: Partial Payment
1. The Administrator creates bill
2. The Administrator generates the partial-payment
S-3: Pending Payment
6

bill
Substitute/Incomparable Flows:
3a: The Receptionist performs the create invoice use case.
S-1, S-2 2a1: The patient can pay fee by money or online
S-2, S-3: The administrator send the pending bill to the patient’s location
(Rajaraman, 2018).
Class diagram
Diagram
Description
7

Class diagram can be defined as the designing method of unified modelling language
which consist the classes, attributes, functions and data types associated with the system's
requirements (Paik, 2018). This figure of class diagram demonstrates the classes named such as
person, medical history, bill, payment, appointment, treatment, patient, employee, hygienist,
receptionist, dentist and schedule. Person contains the attributes such as title with string data
type, first name, last name, gender and telephone are also of string data type, post code as char
and date of birth as date with create, update and delete function with boolean data type. Medical
history contains GP, previous history and dentist as string data type with add, update and delete
functions as boolean. Bill contains date as date and amount as currency data type with function
generate as string. Payment contains patient, bill, type as string and amount as currency with
generate as string. Appointment contains date as date and schedule and reason as string with
functions insert, update and delete as boolean. Treatment contains medications, symptoms and
instructions as string with functions produce as string. Patient contains patient ID and status as
char with functions create, update, delete, status and appointment as boolean, treatment as
treatment and calculate as integer. Employee contains ID as char, role and type as string and
salary as currency with functions create, update and delete as boolean. Hygienist contains
experience as string with functions create, update and delete as boolean. Receptionist contains
communication as string with functions create, update and delete as boolean. Dentist contains
specialisation as string with functions create, update and delete as boolean. Schedule contains
start time and end time as time and date as date with function generate as string.
Interaction diagrams
Sequence diagram
8

Description
There are basically six pillars demonstrating the patient, receptionist, appointment
schedules, billing, patient's profile and dentist. Activities scheduled in sequencing are as follows
such as first is call for schedule of appointment, second is check for availability, third is record
appointment, fourth is schedule appointment, fifth is check in, sixth is record patient's
information, seventh is notification to dentist, eighth is consult patient, ninth is provide dental
service, tenth is payment and eleventh is recoding of payment (Adamtey, 2021). Therefore, this
is the sequencing framed to conduct each and every activity and function in an orderly manner
strategically by the digital management system.
Activity diagram
9

Description
Activity diagram can be defined as the description of activities that can be generated
upon some conditions and cases involved in it in a systematic manner (Hu, Youn and Wang,
2019). Flow of the activity involves the first is get patient's information, second is check patient's
details, third is create new patient, fourth is get appointment request details, fifth is create new
appointment, sixth is change appointment, seventh is cancel appointment, eighth is checking
appointment slot, ninth is schedule appointment, tenth is take alternative date and time, eleventh
is get appointment details, twelfth is update patient details, thirteenth is obtain treatment and
10

fourteenth is make payment. Major conditions taken here are the cancellation of appointment and
patient is absent. Therefore, taking various situations into considerations, activity diagram is
figured out for digital management system in a systematic manner.
CONCLUSION
It is concluded that system analysis and design is an important conception to understand
for developing software such as various information systems like management information
system (MIS), decision support system (DSS), executive support system (ESS), transaction
processing systems (TPS), digital management systems (DMS) and many more (Åström and
Murray, 2021). Therefore, it is essential to analyse the use case diagram, it is necessary to
examine the class diagram, it is significant to determine the activity diagram and it is crucial to
study about the sequence diagram with all their descriptions. Hence, this report covers all such
aspects to better learn and execute about the concept of system analysis and design. Reason
behind studying and gaining knowledge about this topic is that, it enhances the skills and abilities
of an information technology specialised person so that they can apply such concepts in real time
organizations to build up the software system for the company either personally or
professionally.
11

References:
Books and Journals
Adamtey, S.A., 2021. A case study performance analysis of design-build and integrated project
delivery methods. International Journal of Construction Education and
Research. 17(1). pp.68-84.
Åström, K.J. and Murray, R.M., 2021. Feedback systems: an introduction for scientists and
engineers. Princeton university press.
Davis, W.S. and Yen, D.C. eds., 2019. The information system consultant's handbook: Systems
analysis and design. CRC press.
Hu, C., Youn, B.D. and Wang, P., 2019. Engineering design under uncertainty and health
prognostics (pp. 1-100). Springer International Publishing.
Paik, J.K., 2018. Ultimate limit state analysis and design of plated structures (pp. i-643).
Chichester: John Wiley & Sons.
Pedrycz, W., 2018. Granular computing: analysis and design of intelligent systems. CRC press.
Qianyi, Z., Xiaoshun, L., Ping, H. and Lu, N., 2018, March. Analysis and Design of the
Innovation and Entrepreneurship Training Management System based on School
Enterprise Cooperation (Taking the School of Computer and Information Engineering of
Beijing University of Agriculture as an example). In IOP Conference Series: Materials
Science and Engineering (Vol. 317, No. 1, p. 012009). IOP Publishing.
Rajaraman, V., 2018. Analysis and design of information systems. PHI Learning Pvt. Ltd.
12