Chaptre 2

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

Chaptre2 System Analysis and Design

Introduction:
This chapter aims to provide a comprehensive description of the function of our system and
create models of how this function works. To achieve this latter, we use the Unified Language
Model (UML).

Requirement specification:
Definition of UML:

The Unified Modeling Language (UML) is a pictogram based graphical modeling language
designed as a standardized visualization method in the fields of software development and
object oriented design. [3]

Static representation of the system:

The class diagram.

The component diagram.

The deployment diagram.

The package diagram.

The use case diagram.

The composite structure diagram.

Dynamic representation of the system:

The activity diagram

The sequence diagram

The state-transition diagram

The collaboration diagram

The communication diagram

To model the needs of our system, we use the three following diagrams:

Use case diagram:

A use case diagram is a modeling tool for describing the interactions between users (actors)
and an IT system. In summary, the use case diagram provides an overview of a system's
functionality from the perspective of its users.

Use case «authentication»:


Figure I.1- Authentication use case diagram.
Following the previous diagram, to access the system, the user enters their name and

His password. If the information is correct, a home page is displayed according to

the user. Each user of the system (dentist, nurse, patient) has access privileges previously
defined by the application administrator.

Dental practice management use case diagram:


Figure 1.2Dental practice management use case diagram.
The figure above shows the functionalities of different actors of our site in which it appears
that the patient can book appointment and the dentist will consult the files of the patients,
manage their consultation besides making the prescription, the nurse will manage the
appointment of the patients. Of course, we need to log into our system first.

Use cases identifier:

Patient: can know the information of the dentist and the service he choose and booking
appointment. With authority of changing the features of it.

Dentist: covers activities related to the management of patient records and medical
prescriptions in a dental clinic.

Nurse: The nurse accesses the computer system to manage appointments and patient
information.

Class diagram:

The class diagram allows you to present the classes of the application, the relationships
between these classes, and the attributes and methods of each class.
Figure 2 classe diagram
The classes on which our system focuses:
Class
Attribute
Field designation Type
Patient Idp Patient identifier Number
Firstnamep Patient first name Varchar
Lastnamep Patient last name Varchar
Emailp Patient email Varchar
Phonep Patient phone Varchar
Adressp Patient address Varchar
dateofbirthp Patient date of birth Date

Dentist Idd Dentist identifier Number


Firstnamed Dentist first name Varchar
Lastnamed dentist last name Varchar
Speciality dentist speciality Varchar
Phonep dentist phone Varchar
Emailp dentist email Varchar

User Ida User identifier Number


Usernamea Username of the user Varchar
Password User password Varchar

appointment Idap Appointment identifier Number


Prefferendateap Date of oppointment Date
Preffeend Hour of apointment Time
hourap

prescreption Idi Prescription identifier Number


Infoi Information Varchar
Pricei Price of appointment Number
nurse Idn Nurse identifier Number

Conclusion:

In this second chapter, we were able to carry out and detail the design and creation of

our information system for the dental clinic by first adapting to the language of

modeling and based on the diagrams of the UML formalism.by using use case diagram and
class diagram.

You might also like