Preliminary study - Context

modeling
1-Identification of actors and their roles :

In this section, we present the different actors likely to interact with the system, but first, we
give a definition of the actor concept. Actor: the role played by external entities which
interact directly with the system studied, it can be a user, external equipment or another
system.

Starting up the system essentially requires two players :

Administrator: his role is to manage the accounts of the users of the system and to define
their roles, their premises and the services where they belong. He manages the doctors, and
also the existing services in hospitals.

doctor: he is concerned with the management of patients (analyzes and checks, clinical
diagnosis, functional explorations, prescriptions ...).

Billing service: he checks the patient's financial file.

Actor Roles
Administrator  Authenticate
 Account management (users, doctors)
 Add an account
 Consult an account
 Edit an account
 Delete an account
 Manage hospital services:
 Add services
 Delete services
 Modify a service

Doctor  Authenticate
 Manage a patient
 Add a patient (ID, last name, first
name, email, address, age, etc.)
 Find a patient

Billing service
2- Messages sent and received
This table will present the messages allowing to describe the higher level interactions
between the actors and the system. Like each actor, sending messages that trigger a
behavior of the system expected by the actor within the framework of his activity.
Use case
Authenticate
Account Management
Manage hopital services
Manage a patient
Manage an act
Consult patient’s file
 Edit a patient's record
 Edit patient billing info
 View patient bills
 Delete a patient
 Consult a patient's file
 Print patient record
 View patient status report
 Manage a service
 Add an act
 Consult the statistics
 Access telemedicine services
 Authenticate
 Consult a patient's file
 Consult the invoices of a patient
 Consult Statistics
Actors Sent / received messages
-Administrator Sent: Authentication and
-Doctor access to the account.
-Billing Service Received: Request for
authentication and
connection.
-Administrator Sent: Add/Delete/Edit the
information of a user.
Received: Confirmation.
-Administrator Sent: Add/Delete/Edit the
information of a service.
Received: Confirmation.
-Doctor Sent: Add/Delete/Edit the
information of a patient.
Received: Confirmation.
-Administrator Sent: Add /Edit the
-Doctor information of an act.
Received: Confirmation.
-Doctor Sent: View the information
-Billing Service of a patient (diseases,
billing...)
Received: Confirmation and
 automatic generation of the
patient file.
Access tele medecine -Doctor Sent : Choose tele medecine
services services (tele-training,
teleconsultation, tele-
assistance…)
Received: Confirmation.

3)Context modeling
All the messages (system <-> actors) previously identified can be represented synthetically
on a diagram, which we can qualify as a dynamic context diagram.

Figure1 : Dynamic context diagram

4) Capture needs :
1-Use Cases :
A use case represents a discrete unit of interaction between a user and a system and sees
itself as a significant unit of work.

-Administrator :
 Figure : Administrator use cases

-Doctors service :

Figure :Doctor service use cases

-Billing service :
 Figure :Biling service use cases

2-Class Diagram :

The class diagram is considered the most important of object-oriented modeling. It shows
the internal structure of the system and allows to provide an abstract representation of the
objects of the system which will interact together to realize the use cases.

This diagram is a static view because the time factor is not taken into account in the
behavior of the system. The main elements of this static view are the classes and their
relationships: association, generalization and several types of dependencies, such as
implementation and use.
 Figure :Diagram Class

The application uses 3 actors (Administrator, doctors, Billing service) and 3 services (EMR,
billing service, telemedicine service) which all inherit the same class "Service", each has
several tasks.

 Each user must authenticate to access his workspace and his service.
 Nurse belongs to the billing department.
 The doctor belongs to the EMR service and the telemedicine service.
 Each service is characterized by an identifier, a name and a description.
 User accounts are managed by the administrator.
 The billing department manages invoices for patients who may have one or more
invoices.
 The patient's file is processed by all departments.
 A patient can be supervised by one or more doctors, and can make one or more
visits.
 Each service can consult the patient's file and modify its status
 The EMR service displays the archive which contains information relating to patients
and hospitals.