chapter 03 : detailed study

chapter 03 : detailed
study
 chapter 03 : detailed study

I. Introduction:
In this chapter, we present two main design methods used in the development of information
systems: MERISE and UML. These two methods allow to model the data, processes, and
interactions of a system in order to guarantee a structured and coherent design.
1. MERISE METHOD
1.2Definition:
MERISE, acronym for Method of Study and Realization of Computer Science for Enterprise
Systems, is a method for modeling an information system using formal models to ensure
good understanding and effective implementation.
It is based on two fundamental principles:
 The separation of data and processing.
 A hierarchy of design steps, divided into conceptual, logical, and physical levels.
1.3Objectives of the MERISE method:
 Model business needs and functional specificities.
 Develop a structured, scalable, and reliable system.
 Distinguish business aspects from technical constraints.
 Facilitate communication between stakeholders (users, analysts, developers)
2. Fundamental Principles of MERISE :
2.1 The three levels of abstraction
1. Conceptual level :
Represents the essence of business requirements without taking technical constraints into
account.
2.Includes :
 Conceptual Data Model (CDM): data structure.
 The Conceptual Processing Model (CPM): business processes.
2. Logical level :
 Translates the conceptual model taking into account organizational and logical rules,
but without going into technical details.
 Example: Transformation of entities and relationships into tables and keys.
3. Physical level :
Concerns the practical implementation of logical models on specific technologies (databases,
programming languages, operating systems).
 chapter 03 : detailed study

2.2 The main axes of MERISE

Data axis: The structure and organization of information in the system.
Processing axis: The actions performed on the data to achieve business objectives.
3.Steps in the MERISE method
1.Preliminary study :
 Needs analysis and definition of project objectives.
 Determination of the broad functional outlines.
2.Conceptual study :
Creation of the Conceptual Data Model (CDM) and the Conceptual Processing Model
(CPM).
3.Organizational study:
 Transformation of the conceptual models into logical models (LDM and TLM).
 Taking account of organizational constraints.
4.Technical (or physical) study:
 Design of physical schemas for data storage and processes.
 Implementation in specific technical environments.
4.Conceptual Data Model (CDM)
4.1Definition:
The CDM is a graphical representation that describes the data required by the system in the
form of entities, attributes and relationships.
4.2Components of the CDM :
 Entities: Important objects or concepts (e.g. Customer, Product).
 Attributes: Properties or characteristics of entities (e.g. Name, Address).
 Relationships: Associations between entities (e.g. ‘A customer places an order’).
 Cardinalities: Minimum and maximum number of occurrences between two entities.
5.Conceptual Processing Model (CPM)
5.1Definition:
The CTM describes the processes and operations performed on data. It focuses on
information flows and business rules without specifying technical solutions.
5.2Objectives:
 Identify the processes required to meet user needs.
 Describe the links between processes.
 chapter 03 : detailed study

6.MERISE application example

Case study: Customer management in an invoicing system
 CDM :
 Entities: Customer, Invoice, Product.
 Relationships:
 A customer can have several invoices.
 An invoice contains several products.
 CMT :
 Process: Create an invoice, Calculate the total amount, Generate a receipt.
 LDM :
 Tables: Customer(ID_Customer, Name, Address),
Invoice(ID_Invoice,ID_Customer,Date), Product(ID_Product, Name, Price).
 MPD :
 Creation of tables in a SQL database with primary and foreign keys.

7.UML METHOD
7.1Definition:
UML (Unified Modeling Language) is a standardized method for modelling object-oriented
systems. It is used to graphically represent the different aspects of a system using diagrams.
 Main characteristics:
 UML is object-cent red (object-oriented).
 It offers a global view of the system via several types of diagram.
 Advantages:
 Ease of communication between teams.
 Compatibility with modern technologies.
 Allows both static structure and dynamic behavior to be modelled.
7.2DIAGRAMS:
Diagrams are essential tools for graphically representing a system. Here are the main
diagrams used in design methods.
7.2.1 STATIC CONTEXT DIAGRAM:
 Definition:
This diagram shows an overview of the system and its environment. It illustrates the main
interactions between the system and external players.
 chapter 03 : detailed study

(1,1)

SYSTE
(n)
ADMIN Client

Figure01 CONTEXT DIAGRAM

7.2.2. Use case diagrams. M
1 Definition:
The roles of use case diagrams are to collect ,analyze and organize needs, as well as to list
the major functionalities of a system. It is therefore the first UML step for the design of a
system.
A use case diagram captures the behavior of a system, a subsystem, a class or a component
as an external user sees it. It splits the functionality of the system into coherent units, the use
cases, which make sense to the actors. Thus, these use cases make it possible to express the
needs of the users of a system, they are therefore a user-oriented vision of this need, unlike a
computer vision
This first step should never be neglected in order to produce a website that meets the
expectations of the targeted users. To develop use cases, it is necessary to rely on interviews
with users
Composition of the case diagram
The case diagram consists of three main elements:

actor

An Actor: This is the idealization of a role played by an external person, a process or a thing
that interacts with a system. It is represented by a little man with his name written
underneath.

Use cases
 chapter 03 : detailed study
A use case:
it is a coherent unit representing a functionality visible from the outside. It performs an end-
to-end service, with a trigger, a progress and an end, for the actor who initiates it. A use case
therefore models a service provided by the system, without imposing the mode of realization
of this service. It represents by an ellipse containing the name of the case (a verb in the
infinitive), and optionally, above the name, a stereotype.
Relationships: Three types of relationships are supported by the UML standard and are
graphically represented by particular types of these relationships. Relationships indicate that
the source use case has the same execution conditions as the resulting case. A simple
relationship between an actor and a use is a simple trait
The actors of our project:
Clients
 Register on the platform to search for artisans.
 Browse artisan profiles, view services, and compare prices.
 Contact artisans via the messaging system.
 Request services and provide job details.
 Rate and review artisans based on service quality.
Artisans
 Create and manage professional profiles.
 List services offered along with pricing and expertise.
 Receive and respond to client inquiries.
 Manage service requests and complete tasks.
 View and respond to customer reviews.
Administrators
 Oversee the platform’s operations and user activities.
 Approve or reject artisan registrations to ensure quality.
 Monitor and manage user complaints and reports.
 Moderate reviews and prevent misuse of the system.
 Ensure data security and maintain system performance.
Visitors
 Browse the platform without an account.
 View basic artisan profiles and services.
 Register as a client or artisan to access full functionality.

Use case diagrams of our project:

 chapter 03 : detailed study
 Artisa Use Case:

registration

delete profile

#includ

#includ
Edit service

#include
Identification
Sharing profile
#includ

#includ
View comment

Artisan
contacts client

Browse homme page

Contact admin

Figure02 Artisa Use Case

The craftsman is the primary user of the platform, responsible for providing specialized
services to clients. The use case begins when the craftsman registers on the platform by
providing personal details, professional experience, and service offers. Once authenticated,
the craftsman can create and manage a detailed profile, including work samples and contact
information. Clients can search for craftsmen based on experience and location, and initiate a
conversation through the messaging system to discuss service details. The craftsman can
respond to customer inquiries, accept or decline service requests, and schedule tasks
accordingly. After completing a task, the craftsman receives ratings and reviews from
clients, which helps build credibility and attract more opportunities. The craftsman also has
access to a dashboard, where he can track ongoing projects, manage messages, and update
service details. This organized workflow ensures a seamless interaction between craftsmen
and clients, promoting a professional and efficient exchange of services on the platform.

 client Use Case:

 chapter 03 : detailed study
Browse
homme page

Contact
admin

registration
Client

delete profile
#includ

View #includ Identification

comment

#includ

Message for
Artisan
#includ

Browse detail
service #includ

add comment

Figure02 client Use Case

Customers are the primary users of the platform, using it to find and hire skilled craftsmen
for various services. Their journey begins with registration, which allows them to create a
secure account and access the platform’s full range of features.
Once registered, customers can browse craftsmen’s profiles, explore available services, and
compare prices to find the best match for their needs. They can initiate direct communication
with craftsmen through the messaging system, allowing for seamless discussions about
service details, availability, and pricing.

Customers have the ability to request services, specify job requirements and expectations to
ensure clarity before hiring a craftsman. After completing a service, they can rate and review
 chapter 03 : detailed study
craftsmen, providing feedback based on service quality, professionalism, and overall
experience.
By engaging with the platform, customers benefit from a transparent and efficient process to
find trusted professionals, ensuring a satisfying and hassle-free service experience.
visitor Use Case:

Browse homme
page

browse general
service

VISITOR

Contact admin

registration

Figure03 visitor Use Case

Before becoming a customer, an internet user has limited access to the platform, allowing
them to browse the home page and explore general services. They can view basic
information about artisans and their services but cannot interact with them, request services,
or leave reviews. To access full functionality, the visitor must register on the platform as a
client.
 chapter 03 : detailed study
admin Use Case:

see statistic
#includ
e

admin
management #includ
e

Client #includ
management e

Artisan #includ
management e

management #includ
area e
Identification

#includ
ADMIN e
comment
delete
#include

Figure04 admin Use Case

Administrators play a crucial role in managing the platform and ensuring a smooth and safe
experience for all users. They are responsible for overseeing the platform’s operations,
managing user activities, and ensuring compliance with platform policies.
One of their main responsibilities is approving or rejecting artisan registrations, and
verifying the accuracy of information provided to maintain quality of service and
professionalism. They also monitor and handle user complaints, and ensure that disputes
between customers and artisans are handled fairly.
Administrators actively moderate reviews, prevent fraudulent comments or system abuse,
and ensure that reviews reflect real user experiences. Additionally, they are responsible for
data security and platform maintenance, protecting user information, and improving system
performance for a smooth experience.
By managing these responsibilities efficiently, administrators maintain trust, security, and
functionality within the platform, ensuring a reliable and professional environment for both
customers and artisans.
 chapter 03 : detailed study
Sequence diagrams:
Definition:
A sequence diagram is an interaction diagram that details how operations are performed:
what messages are sent and when they are sent. Sequence diagrams are organized according
to the time that passes as we move through the page.
The objects involved in the operation are listed from left to right according to when they take
part in the sequence

Composition of a sequence diagram:

This type of diagrams is composed by the following elements:
Lifelines: A vertical line that represents the sequence of events, produced by a participant,
during an interaction, while time progresses at the bottom of the line. This participant can be
an instance of a class, a component or an actor.
Messages: two types of messages in the sequence diagram, the first is called synchronous
message used to represent ordinary function calls in a program, the second is called
asynchronous message, being used to represent communication between separate threads or
the creation of a new thread

 Execution occurrences: represents the execution period of an operation.

 Comments: A comment can be attached to any point on a lifeline.
 Iterations: represents a response message following a verification question.
Platform Sequence Diagrams:
 Registration sequence diagram:
To take full advantage of the Dedicated Customer privileges, a visitor must
first successfully begin the registration phase and to do so, he must go through all the
sequences that we will simplify with the following diagram
 The visitor requests the registration form.
 The form is displayed.
 The visitor fills out the form.
 A check of the existence of the customer in the database is launched.
 If the customer already exists an error message is displayed.
 If it is a new customer confirmation of the registration is displayed.
 chapter 03 : detailed study

Figure04 Registration sequence diagram

Figure05 Registration sequence diagram for client

 chapter 03 : detailed study

Figure06 Registration sequence diagram for artisan

Authentication sequence diagram

Before reaching the authentication phase, our visitor is a person present on our website
anonymously, from where it becomes essential to enter his login and password. Then,
throughout his navigation, he only has the possibility of accessing the services for which he
is authorized. The following diagram will show you the sequences to perform to begin the
authentication phase

Figure07Authentication sequence diagram for client

 chapter 03 : detailed study

Figure08Authentication sequence diagram for Artisan

Figure09Authentication sequence diagram for admin

 chapter 03 : detailed study
 The customer enters his login and password.
 A check is launched in the database.
 After a response time or the authentication is validated or not error message is
displayed
Deletion Sequence Diagram:
Among the scenarios the management of the exhibits on our website such as Consultation,
Addition, Modification and Deletion that we will show in the following sequence diagram.

Figure10Deletion Sequence Diagram for client

 chapter 03 : detailed study

Figure 11 deletion Sequence Diagram for artisan

Figure 12 deletion Sequence Diagram for admin

 chapter 03 : detailed study

 The administrator or customer or craftsman selects the delete interface.

 The delete menu is displayed.
 The administrator or customer or craftsman must select that he wants to delete.
 The system notifies the administrator or customer or craftsman of the delete operation.
 The administrator confirms the deletion.
 The delete operation completes successfully.
 disappears permanently from the database.

Edit sequence diagram :

Figure 13 Edit sequence diagram for admin

 chapter 03 : detailed study

Figure 14 Edit sequence diagram for artisan

Figure 15 Edit sequence diagram for client

 chapter 03 : detailed study

added comment sequence diagram:

Figure 16 added comment sequence diagram for client

Messaging sequence diagram:

Figure 17 Messaging sequence diagram for visitor

 chapter 03 : detailed study

Figure 18 Messaging sequence diagram for artisan

Figure 19 Messaging sequence diagram for client

 chapter 03 : detailed study

Message for Artisan sequence diagram:

Figure 20 Message for Artisan sequence diagram

Figure 21 Message for client sequence diagram

 chapter 03 : detailed study

Display Browse detail service sequence diagram for client

Figure 22 Display Browse detail service sequence diagram for client

View comment sequence diagram for client

Figure 23View comment sequence diagram for client

 chapter 03 : detailed study
add sequence diagram for admin:

Figure 24 add sequence diagram for admin

delete Artisan sequence diagram for admin:

Figure 25delete Artisan sequence diagram for admin

 chapter 03 : detailed study
delete client sequence diagram for admin:

Figure 26 delete client sequence diagram for admin

Figure 27 Edit sequence diagram for admin

 chapter 03 : detailed study
Edit Artisan sequence diagram for admin:

Figure 28 Edit artisan sequence diagram for admin

Edit client sequence diagram for admin:

Figure 29 Edit client sequence diagram for admin

 chapter 03 : detailed study
delete sequence diagram for admin:

Figure 30 delete sequence diagram for admin

see statistics diagram for admin:

Figure 31 see statistics diagram for admin

 chapter 03 : detailed study

View comment sequence diagram for artisan

Figure 32 View comment sequence diagram for artisan

 chapter 03 : detailed study
Activity diagrams.
Definition:
It is a diagram associated with a particular object or a set of objects, which illustrates the
flows between activities and actions. It allows to graphically represent the progress of a use
case.
Composition of an activity diagram
The activity diagram is composed of the following elements:

activity

An activity represents an execution of a mechanism, in other words, a sequence of sequential

steps.

Activity1 Activity2
Automatic transition

no

Yes
Activity1 Activity2

Conditional transition

A transition that represents the passage from one activity to another. This transition can be
automatic, which is triggered by the end of an activity, causing the immediate start of
another or conditional, which is triggered only after the satisfaction of the condition also
called guard.

Passage condition
 chapter 03 : detailed study

The guards that represent the condition of passage from one activity to another in the
conditional transitions are symbolized by diamonds as in the following figure:

Activity1 Activity2

Sync Bar

Activity3

Synchronization bars are bars represented by a thick line, the role of this bar is to
synchronize the start of several transitions that arrive from different activities, all leading to a
common activity.

Our Website Activities:

Our website is an interactive platform that connects customers and craftsmen while ensuring
efficient management of interactions and services. It offers various essential activities to
ensure a smooth and secure experience for all users.
User Registration and Login:
 Customers and craftsmen can register and create a secure account.
 An authentication system with password reset guarantees data security.
Profile Management:
Craftsmen can personalize their profile by adding:
 Their experience and qualifications.
 Samples of their work (images, videos).
 Their services and prices.
 Customers can manage their profile and save their favorite craftsmen.
Search and Filter Craftsmen:
Customers can search for craftsmen according to:
 Profession (e.g. carpenter, electrician, plumber).
 Location (city, region).
 Ratings and reviews left by other customers.
Communication and Messaging:
 An integrated messaging system allows customers to contact craftsmen.
 Craftsmen can respond directly to requests and discuss the services offered.
 chapter 03 : detailed study

Order and Service Management:

 Customers can request services from craftsmen and set an appointment.
 Craftsmen can accept or decline requests depending on their availability.
Rating and Review System:
 Customers can rate craftsmen after a service and leave a detailed review.
 A star rating system helps identify the best craftsmen.
Platform Administration and Management
Administrators supervise the platform by:
 Validate craftsmen registrations.
 Manage users (suspension of accounts in the event of non-compliance with the rules).
 According to the performance of the site (number of users, services requested, etc.).
Security and Data Protection:
 Data encryption and protection of personal information.
 Compliance with privacy regulations
Our website activity diagrams
The registration phase is essential to go from a simple visitor of the site, who only has the
right to consult the services and their prices, to an active user who can interact with the
platform. Once registered, the user accesses several essential features according to his role:
 Clients: Can contact craftsmen, send service requests, leave reviews and follow their
current services.
 Craftsmen: Can create and manage their professional profile, publish their services,
receive and respond to customer requests.
 Registration is done via a secure form asking for basic information (name, email,
password) and, for craftsmen, additional details such as experience, specialization and
examples of work carried out.
Thus, the registration phase is a key element in transforming a passive visitor into an active
member of the site, promoting a smooth and secure interaction between customers and
craftsmen.
 chapter 03 : detailed study
Activity diagram Registration for artisan

Figure33 Activity diagram Registration for artisan

 chapter 03 : detailed study
Activity diagram Registration for client

Figure33 Activity diagram Registration for client

 The visitor requests registration.

 chapter 03 : detailed study
 The registration form is displayed on the screen.
 The visitor fills in the fields requested in the form.
 The system checks the data entered.
 If the data is accepted, the system sends it to the database, if not, it returns to the
previous step.
 The server checks the existence of the client in the database
 If the client already exists, an error message is displayed.
 If the client does not exist, the registration is completed successfully.

Authentication diagram:
Authentication is the procedure which consists, for a computer system, in verifying the
identity of an entity (person, computer, etc.), in order to authorize its access to systems,
networks,
applications, etc. It therefore makes it possible to validate the authenticity of the entity in
question.
Customer and Craftsman Authentication Process:
Authentication is an essential step allowing customers and craftsmen to access their personal
spaces and interact on the platform securely.
 Access to the login page
 The user (customer or craftsman) clicks on the Login button located on the home page.
 Display of the authentication form
 The system displays a form asking for a phone number and password Entering
identifiers
 The user enters their registered phone number and password.
 Verifying information
 The system checks the identifiers in the database.
 Authentication result
If the information is correct:
 The user is redirected to their dashboard:
 Customers: Access to craftsmen profiles, messaging, order history, reviews.
 Craftsmen: Service management, messaging with customers, monitoring reviews and
evaluations.
If the information is incorrect:
 An error message is displayed, asking to try again or reset the password.
 chapter 03 : detailed study

Authentication Activity Diagram for admin

Figure34Authentication Activity Diagram for admin

 chapter 03 : detailed study

Authentication Activity Diagram for client

Figure35 :Authentication Activity Diagram for client

 chapter 03 : detailed study
Authentication Activity Diagram for artisan

Figure36 :Authentication Activity Diagram for artisan

Contact with admin Activity Diagram for client :

 chapter 03 : detailed study

Figure37: Contact with admin Activity Diagram for client

Contact with admin Activity Diagram for visitor :

 chapter 03 : detailed study

Figure38: Contact with admin Activity Diagram for visitor

 chapter 03 : detailed study
Contact with admin Activity Diagram for artisan:

Figure39: Contact with admin Activity Diagram for artisan

client activity diagrams:

 chapter 03 : detailed study
delete profile Activity Diagram for client :

Figure40: delete profile Activity Diagram for client

edit profile Activity Diagram for client :

 chapter 03 : detailed study

Figure41: edit profile Activity Diagram for client

add comment Activity Diagram for client :

 chapter 03 : detailed study

Figure42 add comment Activity Diagram for client

send the message to artisan Activity Diagram for client :

 chapter 03 : detailed study

Figure43:send the message to artisan Activity Diagram for client

browse service detail Activity Diagram for client:

 chapter 03 : detailed study

Figure44:browse service detail Activity Diagram for client:

artisan activity diagrams:

 chapter 03 : detailed study
delete profile Activity Diagram for artisan:

Figure45: delete profile Activity Diagram for artisan

edit profile Activity Diagram for artisan:

 chapter 03 : detailed study

Figure46: edit profile Activity Diagram for artisan

send the message to client Activity Diagram for artisan :

 chapter 03 : detailed study

Figure47:send the message to client Activity Diagram for artisan

Admin activity diagrams:

 chapter 03 : detailed study
delete profile Activity Diagram for admin :

Figure48: delete profile Activity Diagram for admin

Add profile Activity Diagram for admin:

 chapter 03 : detailed study

Figure49: Add profile Activity Diagram for admin

Add city Activity Diagram for admin:

 chapter 03 : detailed study

Figure50: Add city Activity Diagram for admin

client management Activity Diagram for admin:

 chapter 03 : detailed study

Figure51: client management Activity Diagram for admin

artisan management Activity Diagram for admin:

 chapter 03 : detailed study

Figure52: artisan management Activity Diagram for admin:

change password Activity Diagram for admin:

 chapter 03 : detailed study

Figure53: change password Activity Diagram for admin

 chapter 03 : detailed study
see statistics Activity Diagram for admin:

Figure54: see statistics Activity Diagram for admin

 chapter 03 : detailed study
Class diagram:
Definition:
A UML class diagram describes the structures of objects and information used on our
website, both internally and in communication with its users. It describes information
without referring to a particular implementation. Its classes and relationships can be
implemented in many ways, such as database tables, XML nodes, or software object
compositions.
The composition of a class diagram:
In general, a class diagram can contain the following elements:
 Classes: A class represents the formal description of a set of objects that have
common semantics and characteristics. It is represented using a rectangle
divided into three sections.
The top section is the name of the class, the middle section defines the properties of the
class, while the bottom section lists the methods of the class.
 Associations: An association is a relationship between two classes (binary
association) or more classes (n-ary association), which describes the structural
connections between their instances. An association therefore indicates that
links can exist between instances of the associated classes.

 Attributes: Attributes represent the data encapsulated in class objects. Each of

these pieces of information is defined by a name, a data type, a visibility and
can be initialized. The attribute name must be unique in the class.
 chapter 03 : detailed study

Figure55: Class diagram

 chapter 03 : detailed study
Relational Schema for the System
1. Admin Table
o Stores information about administrators.
o Primary Key: IDADMIN
o Fields: IDADMIN, Email, Role
2. Client Table
o Stores information about clients.
o Primary Key: ClientID
o Fields: ClientID
3. User Table (VSR)
o Contains user details such as name, gender, age, and contact information.
o Primary Key: Alias
o Fields: Alias, Full Name, Gender, Age, CityID, Address, Phone Number, Password, Account
Type
o Foreign Key: CityID references the Area Table
4. Artisan Table
o Stores details about artisans, including profession, experience, education, and work samples.
o Primary Key: ProfessionID
o Fields: ProfessionID, ExperienceDurationID, EducationID, WorkSampleImage
o Foreign Keys:
 ExperienceDurationID references Experience Duration Table
 EducationID references Education Table
5. Messages Table
o Stores messages exchanged between artisans and clients.
o Primary Key: MessageID
o Fields: MessageID, ArtisanID, CustomerID, MessageText, IsRead, SentDate
o Foreign Keys:
 ArtisanID references Artisan Table
 CustomerID references User Table (VSR)
6. Services Table
o Stores a list of services or professions offered by artisans.
o Primary Key: ProfessionID
o Fields: ProfessionID, ProfessionName
 chapter 03 : detailed study

7. Experience Duration Table

o Stores different experience levels for artisans.
o Primary Key: ExperienceDurationID
o Fields: ExperienceDurationID, ExperienceDurationName
8. Education Table
o Stores different levels of education attained by artisans.
o Primary Key: EducationID
o Fields: EducationID, EducationName
9. Area Table
o Stores details about cities and countries linked to users and artisans.
o Primary Key: CityID
o Fields: CityID, CityName, Country
10. Reviews Table
o Stores customer reviews of artisans.
o Primary Key: ReviewID
o Fields: ReviewID, ArtisanID, ReviewerName, Comment, Rating, ReviewDate
o Foreign Key: ArtisanID references Artisan Table
11. Password Reset Tokens Table
o Stores password reset details for users.
o Primary Key: TokenID
o Fields: TokenID, Email, ResetToken, ExpiryDate
Relationships Between Tables
 User Table (VSR) links to Area Table via CityID.
 Artisan Table links to Experience Duration Table and Education Table.
 Messages Table links artisans and clients via ArtisanID and CustomerID.
 Reviews Table links to Artisan Table via ArtisanID.
 Clients interact with artisans through messages and reviews.
 Password Reset Tokens Table links to users via email.
 chapter 03 : detailed study

The model of our website:

Site structure:
The website is designed to create a seamless connection between clients and artisans,
enabling users to find and hire skilled professionals based on expertise, location, and
reviews. The platform consists of three main user roles:
clients, who search for and hire artisans; artisans , who offer services in various fields and
showcase their experience; and administrators, who oversee the system, validate users, and
manage overall functionality. The website features user authentication, allowing clients and
artisans to register and log in, with a secure password reset system. Artisans can create
detailed profiles, listing their skills, experience, education, and previous work samples.
Clients can search for artisans by profession and location, communicate through an
integrated messaging system, and provide reviews and ratings after service completion. The
platform also includes an admin dashboard, where administrators can manage users, monitor
platform statistics, and validate artisan accounts. Through its structured workflow, the
website ensures an efficient, reliable, and user-friendly experience for all users.

Figure56: Structure of our evolving platform

 chapter 03 : detailed study

Conclusion:
In this chapter, we explored two fundamental design methodologies used in the development
of information systems: MERISE and UML. Both methods provide structured approaches to
modeling systems, but they differ in their focus and application.
Both methodologies have their strengths and are applicable in different contexts. The choice
between MERISE and UML depends on the nature of the system being developed, the
project requirements, and the development environment.
In the next chapter, we will shift our focus to the practical aspects of system development by
introducing key techniques such as the development environment, programming languages,
and database management systems (DBMS). This will provide a foundation for applying the
theoretical concepts discussed in this chapter to real-world scenarios.