Code : LGLSI-3-24-83

Republic of Tunisia
Ministry of Higher Education and Scientific Research

University of Monastir
Faculty of sciences

Final Graduation Project Report

In order to obtain

The Degree of License in Computer Science

Speciality : Software Engineering and Information Systems

Subject : Event management CRM

Realized by : DARDOUR DOUAA

Presented on :06/06/2024 at 15:00 in BIB B3 in front of the review committee :

President : Souheyl Mallat

Examiner : Hend Basly
Professionnal Supervisor : Ahmed Naffati
Uinversity Supervisor : Bel-Hassen MAZIGH

Within : Bee Coders

Academic Year 2023/2024

 Signatures

Company Supervisor
Mr. Ahmed NEFFATI

FSM Supervisor
Mr Bel_Hassan MAZIGH

EVENT MANAGEMENT CRM

 Dedication
In profound appreciation of the unyielding support and boundless love bestowed upon me by my
cherished family and friends. To my sister and brother Eya and Yassine Dardour, whose
unwavering belief in my abilities has been a source of constant strength and inspiration, I
owe a debt of gratitude beyond words. Your encouragement, understanding, and
unwavering faith in my endeavors have been the guiding lights on this journey.

To my parents, whose sacrifices and endless encouragement have paved the way for my success,
I am forever indebted. To my friends, Wiem Ben Salem , Syrine Rjeb , Eya Ghith , Amira
Hassine, Habib Garrab, Rania Tlili , Dali Selmi and Chedli kilani whose camaraderie, love
and unwavering support have made every challenge surmountable and every victory
sweeter, thank you for the dopamine you've infused into my life with your presence. Your
willingness to handle all my problems and stand by me through thick and thin has been a
source of immeasurable comfort and strength.

To everyone who stood by my side during this journey, your unwavering support has been a
beacon of light in times of uncertainty. This project is dedicated to all of you, with heartfelt
thanks for your encouragement, guidance, and belief in my abilities. Your presence in my
life has made all the difference.

To my mom, Monia BenHssouna whose boundless love, wisdom, and unwavering support have
been the cornerstone of my existence. This work stands as a tribute to the enduring power
of familial bonds, the invaluable support of true friendship, and the profound influence of
parental love. With deepest gratitude and love,
I dedicate this accomplishment to you, my beloved family and friends, for being the pillars of
strength and the wind beneath my wings, and academic mentorship. Their dedication to
fostering a stimulating learning environment has greatly enriched my educational
experience.
To the memory of my beloved grandma, Fattouma, who passed away. Grandma, I hope you're
watching over me from the sky. I embarked on this journey with you in my heart, and I
hope to fulfill the dreams you had for me. Your love, wisdom, and guidance continue to
inspire me every day.

In conclusion, I am deeply grateful to everyone who has played a part, no matter how small, in
the realization of this project. Your support and contributions have been invaluable, and I
am truly thankful for the opportunity to undertake this endeavor.

with love , Douaa Dardour !

EVENT MANAGEMENT CRM

 Acknowledgments

I would like to express my sincere gratitude to the following individuals and organizations
for their invaluable support and guidance throughout the development of this final year
project:

Mr. Bel_Hassan MAZIGH: I am deeply grateful to my university supervisor, Mr.

Bel_Hassan MAZIGH, for his unwavering support, invaluable guidance, and expert
mentorship throughout every stage of this project. His wisdom, encouragement, and
dedication have been instrumental in shaping the direction and success of this endeavor.

Mr. Ahmed Neffati: I extend my heartfelt thanks to Mr. Ahmed Neffati, my company
supervisor, for his invaluable insights, support, and mentorship during my time at the
company. His expertise, encouragement, and constructive feedback have been invaluable
in shaping my professional growth and the outcome of this project.

Computer Science Department, Faculty of Sciences Monastir: I am grateful to the

Computer Science Department of the Faculty of Sciences Monastir for providing a
conducive learning environment and access to resources essential for the completion of
this project. Their commitment to academic excellence has greatly enriched my
educational journey.

Bee Coders: Special thanks to Bee Coders, the company that hosted me during the duration
of this project. I am grateful for the opportunity to collaborate with the talented team at
Bee Coders and for their support, encouragement, and hospitality throughout my
internship.

I would also like to express my gratitude to all the faculty members, staff, and fellow
students at the Faculty of Sciences Monastir for their support, encouragement, and
academic guidance.

Lastly, I extend my appreciation to my family and friends for their unwavering support,
encouragement, and understanding throughout this journey. Their love, encouragement,
and belief in my abilities have been my source of strength and motivation.

EVENT MANAGEMENT CRM

Table of contents

General Introduction .................................................................................................................. 1

1. Introduction ........................................................................................................................... 2
2. Presentation of the host Company : Bee Coders ................................................................... 2
3. Study of the Existing ............................................................................................................. 3
3.1. Description of the Existing ............................................................................................. 3
3.2. Critique of the Existing .................................................................................................. 3
3.3. Proposed Solution .......................................................................................................... 4
4. Choice of the development Model ........................................................................................ 5
5. Foreseen Planning ................................................................................................................. 6
6.Conclusion ............................................................................................................................... 6
1. Introduction ............................................................................................................................ 7
2. Specification of functional requirements ............................................................................... 7
2.1. Functional Requirements..................................................................................................... 7
3. Specification of non functional requirements ........................................................................ 7
3.1. Performance ........................................................................................................................ 7
3.2. Usability .............................................................................................................................. 8
3.3. Security................................................................................................................................ 8
3.4. Reliability ............................................................................................................................ 8
3.5. Compatibility ....................................................................................................................... 8
4.1. Presentation of Actors ......................................................................................................... 8
4.2. Description of Use Cases .................................................................................................. 10
5.Global Use Case Diagram ..................................................................................................... 17
1. Introduction .......................................................................................................................... 19
1.1. UML Language ................................................................................................................. 19
1.2. Usage of UML ................................................................................................................... 19
2. Dynamic Modeling ............................................................................................................ 19
2.1. Sequence Diagrams ....................................................................................................... 19
2.2. Activity Diagrams ............................................................................................................ 28
3. Static Modeling ................................................................................................................. 29
3.1. Class Diagram ............................................................................................................... 29
3.2.1. Data Objects and Attributes ........................................................................................... 30
3.3. Data Dictionary ............................................................................................................. 31
3.4. Application Architecture ............................................................................................... 32
3.4.1. MVC Architecture .......................................................................................................... 32

EVENT MANAGEMENT CRM

3.4.2 Advantages of the MVC Architecture:............................................................................ 33
3.4.3. Software Architecture ............................................................................................... 33
3.4.4. Hardware Architecture .............................................................................................. 34
4. Conclusion ......................................................................................................................... 35
1. Introduction .......................................................................................................................... 36
2. Development Environment ............................................................................................... 36
2.1. Hardware Environment ................................................................................................. 36
2.2. Software Environment.................................................................................................. 36
3. Main graphical interfaces .................................................................................................. 38
4. Conclusion ......................................................................................................................... 45
General Conclusion .................................................................................................................. 46
Webography ............................................................................................................................. 47

EVENT MANAGEMENT CRM

List of figures

Figure 1: Bee Coders Logo ........................................................................................................ 2

Figure 2: Identification of Actors ............................................................................................... 8
Figure 3: Admin Global use case Diagram .............................................................................. 17
Figure 4: User Global use case Diagram .................................................................................. 18
Figure 5: Sequence Diagram <<Authentication>> .................................................................. 20
Figure 6: Sequence Diagram <<Reset Password>> ................................................................ 21
Figure 7: Sequence Diagram <<Profile Picture Modification>> ............................................. 22
Figure 8: Sequence Diagram <<Booking Event >> ................................................................. 23
Figure 9: Sequence Diagram <<Create Event >> .................................................................... 24
Figure 10: Sequence Diagram <<Edit Event >> ...................................................................... 25
Figure 11: Sequence Diagram << Give Feedback >> .............................................................. 26
Figure 12: Sequence Diagram << chatting with others _reply on messages >> ...................... 27
Figure 13: Activity diagram <<Authentication>> ................................................................... 28
Figure 14: Activity diagram <<User Profile Management >> ................................................. 28
Figure 15: ClassDiagram<<Eventia>> .................................................................................... 29
Figure 16: MVC Architecture .................................................................................................. 33
Figure 17: Component Diagram << Event Management system >> ...................................... 33
Figure 18: deployment Diagram << Event Management system >> ....................................... 34
Figure 19: welcome screen ....................................................................................................... 38
Figure 20: Login screen............................................................................................................ 38
Figure 21: sign _in screen ........................................................................................................ 39
Figure 22: Forget Password screen .......................................................................................... 40
Figure 23: Pin code screen ....................................................................................................... 40
Figure 24: Profile_screen ......................................................................................................... 41
Figure 25: Add_Profile_screen ................................................................................................ 42
Figure 26:bookings_screen ...................................................................................................... 43
Figure 27:booking_details_screen............................................................................................ 43
Figure 28: Feedback_screens ................................................................................................... 44
Figure 29: Create_event_screen ............................................................................................... 44

EVENT MANAGEMENT CRM

List of Tables

Table 1: Information about Bee Coders ..................................................................................... 2

Table 2: Comparative Table of Existing Solutions .................................................................... 4
Table 3: Foreseen Planning ........................................................................................................ 6
Table 4: The roles of the actors ............................................................................................... 10
Table 5: Description of the use case '001' for the User ........................................................... 12
Table 6: Description of the use case '002' for the User ............................................................ 13
Table 7: Description of the use case '002' for the User ............................................................ 14
Table 8: Description of the use case '001' for the Admin ........................................................ 15
Table 9: Description of the use case '002' for the Admin ........................................................ 16
Table 10Table 10: Hardware Environment .............................................................................. 36

EVENT MANAGEMENT CRM

 General Introduction
Events are crucial parts of societies globally as they form platforms for talk, joyfulness
and knowledge exchange. In the modern age, effectiveness and efficiency in managing events
has turned into a necessity. Technologies for handling events have many benefits not only to
those who plan them but also to participants by making it easier to plan, organize and run an
event.
Event management technologies, possibly the most visible feature of changes in event
preparation and execution globally. Due to technological progress, geographical limits have
vanished which enabled cooperation and involvement across borders. Businesses utilize event
management systems for conducting worldwide trade exhibitions, international conferences as
well as product launches promoting networking on an international scale and market expansion.
In the same way, universities and colleges use them for organizing lectures and conferences
which assist in disseminating information and research globally.
Also, in Tunisia event management systems are very important. Tunisia is a nation full
of diversity and cultural heritage. It has a lively events schedule consisting of festivals,
exhibitions and social gatherings.
Event management systems serve as catalysts for showcasing Tunisian arts and
traditions, increasing travel and boosting the economy by bringing in more money from tourists.
They play a vital role in promoting cooperation between regional companies, governmental
bodies and community groups. This helps to foster socio-economic growth while also creating
an atmosphere of pride and unity among the people of Tunisia.
Furthermore, the significance of virtual event management systems has increased since
the COVID-19 pandemic.
These technologies help to maintain a seamless connection between physical and
virtual events, ensuring stability in times of unprecedented challenges. Management systems
for virtual events have enabled the occurrence of online trade shows, digital conferences and
distant learning in Tunisia. This has assisted people and businesses adjust to the new regularity
while keeping security measures intact as well as hygienic compliance.
Fundamentally, the appearance of event management systems has altered the events
sector by going beyond national limits, enhancing work efficiency and increasing worldwide
connection. These systems are like

Engines of growth in Tunisia that encourage social unity, economic enlargement and
intercultural interaction; these all contribute to overall healthiness and welfare of this nation.

EVENT MANAGEMENT CRM 1

 PROJECT FRAMEWORK PRESENTATION

1. Introduction
An important step in system development is the Analysis and Needs Specifications
phase, which focuses on comprehending project needs and establishing goals. It seeks to build
a clear knowledge of the goals and functions of the system through stakeholder input and
evaluation of current systems. This phase lays the groundwork for effective project planning
and execution through teamwork and meticulous analysis. This section will examine the
approaches and procedures used in this stage, emphasizing their significance in directing the
process of development and guaranteeing stakeholder satisfaction.
2. Presentation of the host Company : Bee Coders
I completed my final internship at "Bee Coders." It is a seasoned IT company with
expertise in software development, internet of things, mobile application development, and
website creation. This business pays close attention to market demands.

Figure 1: Bee Coders Logo

Bee Coders was established in 2020. Table 1 presents an information sheet about this
company:

Company Name Bee Coders

Year of Establishment 2020

Business Sector Information Technology Activities

Headquarters El Ghazela Technological Park, Ariana

2088

Phone +216 58 840 064

Email Address admin@beecoders.tn

Table 1: Information about Bee Coders

Bee Coders is a company specializing in software development and IT services, focusing on:
 Web and mobile (Android and iOS) creation and development,
 Custom software development,
 Design of connected objects and smart services,

EVENT MANAGEMENT CRM 2

 PROJECT FRAMEWORK PRESENTATION

 Custom embedded system development,

 Web design,
 IT consulting,
 Distance learning courses.

3. Study of the Existing

3.1. Description of the Existing

Checking the present event management system is not merely a procedure, it has many
benefits and strategic importance. By deeply studying the existing setup, businesses can locate
trouble spots and ineffective parts that are causing issues in running events smoothly. This
process offers chances to improve procedures, make user experiences better and prompt overall
innovation within the system. Moreover, this type of work is good for making sure resources
are used carefully to give the most benefits with small costs. Firms can also decrease risks and
safeguard delicate information by checking if rules are followed correctly and improving
security steps. Using the understanding acquired from this evaluation, interested parties may
make sensible decisions that steer the event management system towards greater effectiveness
and stakeholder contentment.

3.2. Critique of the Existing

The analysis of the present event management system shows several parts that could
be improved. Initially, the user interface of the system is not simple to use or intuitive for
organizers and guests. It's hard to navigate through various phases such as preparing an event,
registering people in it, then gathering feedback afterward - this causes annoyance and lessens
participation.
Secondly, the system's low integration capabilities make it difficult for different
components and other platforms to communicate smoothly. This kind of compartmentalized
approach hinders the flow of information, stopping organizers from getting a complete picture
about event measurements and interactions with participants.
Moreover, the system's dependence on old-fashioned technologies creates significant
security risks as it becomes vulnerable to intrusions into important attendance data. The
concerns are compounded by weak encryption methods and infrequent audits of security that
put at risk the overall trustworthiness of this platform.
There is also doubt about the system's ability to scale up because it struggles with
increasing needs of larger events or sudden jumps in registration numbers. This lack of
scalability impacts both dependability and performance during peak times, making it difficult
for organizations to grow.
To do this we have carried out a comparative study between some existing solutions
we have around . The following Table describes the criteria used to evaluate these systems
features.

EVENT MANAGEMENT CRM 3

 PROJECT FRAMEWORK PRESENTATION

National international proposed

Solution applications applications solution

Functionalities WeGo Ija Vamos Eventful Eventia

Tunisia

Multilingual _ _ + + +

Agenda + + + _ +

Event Creation _ _ _ _ +

Feedback System _ _ _ _ +

Event Sharing _ _ + + +

Event Participation _ + + + +

Event filtering + + + + +

Category filtering + + + + +

Diversity of + + + + +
categories

Payment For Tickets _ + + + +

Table 2: Comparative Table of Existing Solutions

3.3. Proposed Solution

A complete solution is shown that addresses the shortcomings of the current event
management systems as described in the critique. It covers a number of usability, integration,
security, scalability, and reporting issues.
First, the system's user interface will be redesigned using a user-centered design approach,
with an emphasis on simple navigation and efficient workflows. To improve usability and user

EVENT MANAGEMENT CRM 4

 PROJECT FRAMEWORK PRESENTATION

happiness, this will entail doing user research, getting input from stakeholders, and iteratively
improving the interface.
Second, by putting in place reliable middleware and APIs, efforts will be made to enhance
the system's integration capabilities. This will make it easier for various modules and outside
platforms to communicate with one another, giving event planners access to real-time
information and insights from all over the event ecosystem.
Strict security protocols will be in place to protect private attendee data and reduce the
possibility of data breaches. To guarantee the highest level of data protection, this includes
implementing encryption mechanisms, conducting frequent security audits, and adhering to
industry standards like GDPR and PCI-DSS.
Cloud-native technologies will be used in the system's architecture to overcome
scalability issues, enabling elastic scaling in response to demand. This will guarantee peak
performance and dependability even while managing sizable events with high registration
numbers.
Last but not least, the system will incorporate sophisticated reporting and analytics
features to give event planners thorough insights into attendance demographics, ROI, and
success measures. This will enable event planners to optimize their strategy, make data-driven
decisions, and effectively communicate the value of their events to stakeholders.
The event management system will change as a result of putting these suggested solutions
into practice; it will become more integrated, scalable, secure, and data-driven. This will
increase the overall experience for sponsors, attendees, organizers, and other stakeholders in
the event ecosystem, in addition to increasing the efficacy and efficiency of event planning and
execution.
4. Choice of the development Model
In the development of my event management system, I have decided to use the Agile
model because it is naturally flexible, adaptable and iterative. Being a lone developer, I know
how crucial it is to quickly respond to changing requirements and feedback. Agile helps me
divide the project into smaller parts or "sprints" that can be managed more easily with focus on
delivering functional work in short cycles. This way allows me to focus on important tasks and
produce value step by step for those involved. Also, Agile encourages working together and
talking, even when you are alone, because of frequent check-ups and changes. As I adopt Agile
ideas like always getting better and working with customers closely, my goal is to create an
event managing system that adapts as needs change while still being effective in responding
promptly to user suggestions during its development stage

EVENT MANAGEMENT CRM 5

 PROJECT FRAMEWORK PRESENTATION

5. Foreseen Planning

Semaine Février Mars Avril Mai

Etape
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Preliminary Study

Design

Implementation

Testing and Validation

Table 3: Foreseen Planning

6. Conclusion
To sum up, this chapter brought in the project framework. It started with a general view
of Bee Coders, the company hosting it. I then looked at the present system, talked about its
criticism and suggested solutions for problems found in it. I also discussed the model of
development and planning that I expect to use. This gives an outline to the following chapters
where more details and implementations will be explained.

EVENT MANAGEMENT CRM 6

 SPECIFICATION OF REQUIREMENTS

1. Introduction
In this section we will present the functional and non-functional needs of our system and
the graphical charter.

2. Specification of functional requirements

The upcoming subsections define the different functional and non-functional

requirements that our application follows.

2.1. Functional Requirements

The application has to present users with these main functional requirements:
 Users should be able to register for events through the mobile app.
 The app should provide a personalized dashboard for users to view upcoming events,
event details, and notifications.
 Users should be able to purchase tickets or register for sessions within events through
the mobile app.
 The app should support secure payment processing for ticket purchases.
 Users should be able to view and edit their profile information, including
 contact details and preferences, within the mobile app.
 The app should allow users to receive real-time updates and alerts regarding event
changes or announcements.
 Users should be able to access digital tickets or badges for events directly from the
app.
3. Specification of non functional requirements

All existing applications need to follow a set of non-functional requirements in order to

ensure the quality and proper functioning of the system and provide a satisfactory user
experience.

3.1. Performance
 The mobile app should have fast loading times and smooth navigation, even under high
user loads.
 Response times for user interactions within the app should be minimal, aiming for
under 1 second.

EVENT MANAGEMENT CRM 7

 SPECIFICATION OF REQUIREMENTS

3.2. Usability
 The app should have an intuitive user interface, with clear navigation and easily
accessible features.
 Accessibility features should be implemented to ensure usability for users with
disabilities.
 3.3. Security
 User authentication and authorization mechanisms should be implemented to protect
user data and transactions.
 The app should adhere to industry standards for data encryption and protection of
sensitive information.
3.4. Reliability
 The mobile app should be stable and reliable, with minimal crashes or downtime.
 Error handling mechanisms should be in place to gracefully handle unexpected errors
or disruptions.
3.5. Compatibility
 The app should be compatible with a wide range of mobile devices and operating
systems, including iOS and Android.
 Compatibility testing should be conducted to ensure consistent performance across
different devices and screen sizes.
 4. Presentation of use case
The use case describes the communication between the system and the actors in the form
of actions. In fact, it is a means of analyzing user needs to link the actions of a user with the
expected reactions of a system. This section clarifies and specifies the context and requirements
of the essential parts of a system. The figure below shows the overall use case diagram that
allows each user to apply certain actions. Each actor must authenticate first to access the
features provided by the system.
4.1. Presentation of Actors
In this section, I will give a description of the different players with the system. Starting
with a small definition of the actor: an actor is an idealization of a role played by external
entities (user, hardware devices, or other systems) which interact with the studied system.
The actors in relation to this system are:

Figure 2: Identification of Actors

EVENT MANAGEMENT CRM 8

 SPECIFICATION OF REQUIREMENTS

Actor Role Responsibilities Actions

Manage event listings, Admin performs

including creating, administrative tasks to
updating, and deleting ensure the smooth
system events. operation and integrity of
Represents
the Event Management
administrators or personnel
System, maintaining
Admin responsible for managing Approve or reject event
quality, security, and user
and overseeing the Event submissions from satisfaction.
Management System. Admin organizers.
has elevated privileges and
access rights compared to
regular users View analytics and
reports on event
participation,
attendance, and
feedback.

Manage user accounts

and profiles, including
user roles and
permissions.

Configure system
settings, such as event
categories, notification
preferences, and
security settings.

View list of upcoming Users primarily engage in

events. actions related to
browsing, registering, and
managing their event
Search for specific participation within the
Represents individuals who events based on
interact with the Event criteria like date, system.
User Management System to location, or category.
participate in events, view
event details, register for
events, and perform other View detailed
user-specific actions. information about
events, including

EVENT MANAGEMENT CRM 9

 SPECIFICATION OF REQUIREMENTS

descriptions, date,
time, location, and
organizer details.

Register or RSVP for

events they are
interested in attending.

View their registered

events and manage
their registrations
(e.g., cancel
registration).

Provide feedback or
ratings for attended
events.

Receive notifications
or reminders about
upcoming events.

Table 4: The roles of the actors

4.2. Description of Use Cases

When presenting the use cases by actor, each actor in the system is associated with a list
of use cases corresponding to their responsibilities and actions within the system. This approach
is appropriate when the functions of the actors are clearly defined and independent from each
other. It provides a clear and structured view of the interactions between the actors and the
system.
In this context, the use cases for the Admin and User Actors would include tasks and
responsibilities specific to administrative roles within the event management system

For the Admin Actor in an Event Management System:

When presenting the use cases by actor, each actor in the system is associated with a list
of use cases corresponding to their responsibilities and actions within the system. This approach
is appropriate when the functions of the actors are clearly defined and independent from each
other. It provides a clear and structured view of the interactions between the actors and the
system.
In this context, the use cases for the Admin Actor would include tasks and responsibilities
specific to administrative roles within the event management system.

EVENT MANAGEMENT CRM 10

 SPECIFICATION OF REQUIREMENTS

These may involve functions such as:

 Managing Events: Creating, updating, and deleting event listings.
 Managing Users: Adding, modifying, or removing user accounts.
 Viewing Reports: Accessing analytics and generating reports on event attendance,
user engagement, etc.
 Managing Permissions: Setting access levels and permissions for other users.
 Handling Payments: Managing financial transactions related to events.
 Resolving Issues: Addressing user inquiries, troubleshooting technical issues, etc.
 Configuring System Settings: Adjusting system configurations, preferences, and
settings.

Each use case should be described textually to eliminate ambiguity and clarify points such
as preconditions, post_conditions, main flow, extensions, and any special requirements
associated with the task.

For the User Actor in an Event Management System:

Similarly, the use cases for the User Actor would encompass tasks and interactions
specific to end users utilizing the event management system. These may include functionalities
such as:

 Browsing Events: Searching, viewing, and selecting events to attend.

 Registering for Events: Signing up for participation in specific events.
 Managing Registrations: Modifying or canceling event registrations.
 Providing Feedback: Submitting reviews, ratings, or feedback for attended events.
 Interacting with Event Organizers: Communicating with event organizers
regarding inquiries or issues.
 Making Payments: Processing payments for event registrations or ticket purchases.
 Accessing Event Information: Viewing event details, schedules, locations, etc.
 Sharing Events: Sharing event information with others via social media or
messaging platforms.

EVENT MANAGEMENT CRM 11

 SPECIFICATION OF REQUIREMENTS

Each use case involving the User Actor should be described comprehensively to ensure
clarity and understanding of the user's interactions with the system.

The tables below cover typical actions that an Admin or a User actor might perform within
an Event Management System:

Use Case n° UC_User_001

Use Case Name User Registration

Actor(s) : User

Objectives : To allow the user to register for an account.

Pre-condition(s) None
:

The user successfully registers for an account.

Post-condition(s)
:

1. User navigates to the registration page.

Nominal 2. User fills out the registration form with required information (Full
Scenario : Name, email, password,Phone Number).
3. User submits the registration form.
4. System validates the information provided.
5. If validation is successful, the system creates a new user account.
6. End of use case.

 If the username or email is already in use, the system prompts the

Alternative user to choose a different one.
Scenario :  If the password does not meet the requirements, the system prompts
the user to choose a stronger password.

Table 5: Description of the use case '001' for the User

EVENT MANAGEMENT CRM 12

 SPECIFICATION OF REQUIREMENTS

Use Case n° UC_User_002

Use Case Name Event Creation

Actor(s) : User

Objectives : To allow the user to create a New Event .

Pre-condition(s): The User must be logged in to the system.

The new event is successfully created and added to the system.

Post-condition(s):

1. User navigates to the "Create Event" page.

Nominal Scenario: 2. User fills out the event creation form with details (event name,
description, date, location, Sponsors , guests , etc…)
3. User uploads any required event images or files.
4. User submits the event creation form.
5. System validates the information provided.
6. If validation is successful, the system creates a new event entry in
the database.
7. End of use case.

 If any required fields are missing or invalid, the system prompts the
Alternative user to correct them before submission.
Scenario :  If there are any errors during submission, the system displays an
error message and prompts the user to try again.

Table 6: Description of the use case '002' for the User

EVENT MANAGEMENT CRM 13

 SPECIFICATION OF REQUIREMENTS

Use Case n° UC_User_003

Use Case Name Event Registration

Actor(s) : User

Objectives : To allow the user to register for an Event .

Pre- The User must be logged in to the system.

condition(s) :

The user's registration for the event is successfully recorded.

Post-
condition(s) :

1. User navigates to the event details page.

Nominal 2. User selects the option to register for the event.
Scenario :
3. System checks if the user is eligible to register ( availability,
registration deadline).
4. If eligible, the user's registration is recorded in the system.
5. End of use case.

 If the event registration deadline has passed or the event is already

Alternative at full capacity, the system notifies the user that registration is closed.
Scenario :

Table 7: Description of the use case '002' for the User

EVENT MANAGEMENT CRM 14

 SPECIFICATION OF REQUIREMENTS

Use Case n° UC_Admin_001

Use Case Name Event Approval

Actor(s) : Admin

Objectives : To allow the admin to review and approve events submitted by users.

Pre- The admin must be logged in to the system.

condition(s) :

The event is either approved or rejected by the admin.

Post-
condition(s) :

1. Admin navigates to the "Pending Events" section of the admin

Nominal dashboard.
Scenario : 2. Admin views the list of pending events awaiting approval.
3. Admin selects a pending event to review its details.
4. Admin evaluates the event details and determines whether it meets the
criteria for approval.
5. If the event meets the criteria, the admin approves the event.
6. System updates the event status to "Approved" and notifies the user.
7. If the event does not meet the criteria, the admin rejects the event.
8. System updates the event status to "Rejected" and notifies the user.
9. End of use case.

 If the admin encounters any issues or discrepancies with the event

Alternative details, they may request additional information from the user before
Scenario : making a decision.
Table 8: Description of the use case '001' for the Admin

EVENT MANAGEMENT CRM 15

 SPECIFICATION OF REQUIREMENTS

Use Case n° UC_Admin_002

Use Case Name User Management

Actor(s) : Admin

Objectives : To allow the admin to manage user accounts and permissions.

Pre- The admin must be logged in to the system.

condition(s) :

User accounts and permissions are successfully managed by the admin.

Post-
condition(s) :

1. Admin navigates to the "User Management" section of the admin

Nominal dashboard.
Scenario : 2. Admin views the list of registered users and their account details.
3. Admin selects a user account to manage.
4. Admin can perform various actions such as:
5. Editing user details (e.g., name, email).
6. Resetting user passwords.
7. Assigning or revoking user permissions (e.g., admin privileges).
8. Suspending or deleting user accounts.
9. Admin saves the changes made to the user account.
10. End of use case.

 If the admin encounters any issues with a user account (e.g.,

Alternative suspicious activity), they may choose to suspend or delete the account
Scenario : immediately without further editing.

Table 9: Description of the use case '002' for the Admin

EVENT MANAGEMENT CRM 16

 SPECIFICATION OF REQUIREMENTS

5. Global Use Case Diagram

Figure n° 3 below represents the Admin Global Case Diagram :

Figure 3: Admin Global use case Diagram

EVENT MANAGEMENT CRM 17

 SPECIFICATION OF REQUIREMENTS

Figure n° 4 below represents the User Global Case Diagram :

Figure 4: User Global use case Diagram

EVENT MANAGEMENT CRM 18

 SYSTEM DESIGN

1. Introduction

The purpose of the conceptual data model is to create a static image of the information
system. Its goal is to generate an unambiguous and orderly depiction of data handled by this
information system. This section will be shown in the following manner: we start with the
selection of the design methodology and its justification. Then, we identify use case diagrams.
After that, the presentation of sequence diagrams, and finally the class diagram.
To elaborate on the application, we want to set up a design that is humble and will
accomplish what our project aims for. So, it’s necessary to pick a design language which can
be adjusted according to our requirements.

1.1. UML Language

UML, which stands for Unified Modeling Language, is a graphical modeling language
that employs pictograms. It was born in the software engineering realm from "object-oriented
design." In software projects, it can be used for all types of systems not limited to information
technology. The 14 UML diagrams are related in a hierarchical manner, making them all
necessary for modeling a project from start to end.

1.2. Usage of UML

UML is a formal and standardized language in terms of object modeling. It’s
independent from programming languages, flexible, and versatile which has made it universal.
UML, first and foremost, serves as a communication tool aiding in the expression and
comprehension of object-oriented solutions. The graphical symbols and structure of UML
make it simple to understand, promoting clear communication about an object-oriented
solution. It provides a common way for expressing design ideas that can be easily compared
and evaluated. The aspect of its notation reduces confusion or misinterpretation

2. Dynamic Modeling
2.1. Sequence Diagrams

The sequence diagram is a type of diagram used in software engineering to model

interactions between objects in a system. It is part of the Unified Modeling Language (UML).
The main role of a sequence diagram is to visually represent the chronological sequence
of interactions between different objects in a system, showing the messages exchanged
between them. It allows visualization of the flow of control and communication between
objects and helps understand how actions are chained over time.
The sequence diagrams presented in this report represent interactions between
components of an application according to the MVC architecture:
View: Represents the view, which is responsible for displaying data to the client.
Controller: Manages interactions between the view and the data model.

EVENT MANAGEMENT CRM 19

 SYSTEM DESIGN

Model: Encapsulates both business logic and access to database data

Figure 5: Sequence Diagram <<Authentication>>

This screenshot shows the system sequence diagram for the authentication case: To access
their session, each user must provide their email address and password. If the provided
information is incorrect, an error message will be displayed. If the email address exists and the
password is correct, but the user has not yet been verified, a verification email will be sent with
a code that the user must enter. After entering the code, the user will be able to log in. If
everything goes smoothly and the data is valid, the user is redirected to their private space

EVENT MANAGEMENT CRM 20

 SYSTEM DESIGN

Figure 6: Sequence Diagram <<Reset Password>>

This image depicts the sequence diagram of the password reset system: To enter their
session, each user must enter their email address and password. If they have forgotten their
password, they must reset it by clicking on the 'Forgot Password' button and providing their
email address.The system then sends an email containing the password reset code, and the user
must enter this code: if it is correct, a form appears where they must enter their new password,
which will update their password in the database and allow them to log in with their new
password. If the code is incorrect, the system sends an error.

EVENT MANAGEMENT CRM 21

 SYSTEM DESIGN

Figure 7: Sequence Diagram <<Profile Picture Modification>>

This sequence diagram describes the various steps required to update a user's profile
picture. First, the user accesses the option to update the profile picture from their account. The
application opens an interface allowing the user to select a new photo from the gallery. Once
the user selects the new photo, the application generates a unique link for this photo and stores
it in the application's database, associating it with the corresponding user. Finally, the
application displays the user's new profile picture on their account.

EVENT MANAGEMENT CRM 22

 SYSTEM DESIGN

Figure 8: Sequence Diagram <<Booking Event >>

In the scenario where the event is available, the user initiates the booking process via the
view, leading to a series of interactions between the components of the MVC architecture. The
controller orchestrates the flow by querying the model for event availability, which in turn
communicates with the database. Upon Confirmation of availability, the controller provides
event options to the view, and the user selects the desired event. The controller then reserves
the event slot, updating the database accordingly, and finally confirms the booking to the user
via the view. Conversely, if the event is unavailable, the flow halts after the controller receives
the unavailability status from the model, prompting the view to display a corresponding
message to the user, indicating the event's unavailability for booking.

EVENT MANAGEMENT CRM 23

 SYSTEM DESIGN

Figure 9: Sequence Diagram <<Create Event >>

The sequence diagram shows how an event is made in the system. At first, the user starts
this process by asking to make an event through the user interface (View). The request goes to
the Controller, which checks and confirms if all details of the event from View are correct.
When validation is complete, the Controller communicates with the Model to save event
details. The Model talks to Database for saving event details. After Database shows that it has
successfully created the event, Model gives confirmation back to Controller who then tells View
about this success.
To end, the View will show a message of confirmation to the user that says the event has
been created successfully.

EVENT MANAGEMENT CRM 24

 SYSTEM DESIGN

Figure 10: Sequence Diagram <<Edit Event >>

The sequence diagram shows the situation of an organizer going to the edit event screen
after they create a new event. When the event is successfully made, the organizer (User) starts
the process for editing it by moving directly from View to edit event screen.

The request gets passed on to the Controller from View, and then it goes into Model for
getting details about this particular event. The Model gets all the necessary event details from
the Database and gives them back to the Controller. Then, the Controller sends these event
details to View for showing the edit event screen on the organizer's end.

This sequence makes it easy for organizers to get into and change things about their events
which improves how usable our system is because they can conveniently access everything
needed in this way.

EVENT MANAGEMENT CRM 25

 SYSTEM DESIGN

Figure 11: Sequence Diagram << Give Feedback >>

This sequence diagram shows how feedback is given in the system. It starts when the user
begins a feedback process via user interface (View). View sends forward feedback to
Controller, then Controller validates details from the user. After validation, the Model is being
interacted with by the Controller to save feedback.

The Model communicates with Database and this way feedback data gets persisted in it.
When Database confirms that it has saved feedback successfully, Model gives a confirmation
back to Controller.

Afterwards, the Controller tells the View about the feedback confirmation and the View
shows a message saying confirmation to the user. This series makes sure that any input from
users is correctly saved, confirmed and shown in the system. It helps to keep people interested
and improve things constantly.

EVENT MANAGEMENT CRM 26

 SYSTEM DESIGN

Figure 12: Sequence Diagram << chatting with others _reply on messages >>

This diagram depicts a simplified view of a chat room system's core functionalities.
Users interact with the chat room through a client interface, and the server manages message
communication and potentially stores chat history.

EVENT MANAGEMENT CRM 27

 SYSTEM DESIGN

2.2. Activity Diagrams

Figure n° 13 below represents the Activity diagram <<Authentication>>

Figure 13: Activity diagram <<Authentication>>

Figure 14: Activity diagram <<User Profile Management >>

EVENT MANAGEMENT CRM 28

 SYSTEM DESIGN

3. Static Modeling

3.1. Class Diagram

Following is our system’s class diagram , in software engineering, class diagram in the
UML, is a way to describe the system structure by showing its classes their attributes,
operations and the relationship among them.
Figure n° 15 below represents the Global Class Diagram :

Figure 15: ClassDiagram<<Eventia>>

EVENT MANAGEMENT CRM 29

 SYSTEM DESIGN

3.2. Relational Model

3.2.1. Data Objects and Attributes
This is a brief view of the potential attributes I have in my “Eventia” system

Admin = Email+password

User = First_Name+Last_Name+Date_of_birth(dob)+Phone_Number+Location+Gender+Image

Organizer=
First_Name+Last_Name+Date_of_birth(dob)+Phone_Number+Location+Gender+Image+email+password

Event=Name+Price+Location+Max_Entries+Description+saves+tags+points+Media

3.2.2. Entity Relationship(ER) Diagram

EVENT MANAGEMENT CRM 30

 SYSTEM DESIGN

3.3. Data Dictionary

Event
Attributes Type

Name Varchar (30)

Price Varchar (30)

Location Varchar (30)

Max_Entries Int (10)

Description Varchar (500)

saves Array

tags Varchar (30)

Points Varchar (30)

Media Map

Date Date

Admin
Attributes Type
email Varchar (30)
Password Varchar (30)

EVENT MANAGEMENT CRM 31

 SYSTEM DESIGN

User

Attributes Type
First_Name Varchar (30)
Last_Name Varchar (30)
Date_of_birth(dob) Date
Phone_Number Varchar (30)
Location Varchar (30)
Gender Boolean
Image Varchar (30)
email Varchar (30)
Password Varchar (30)
3.4. Application Architecture
It is crucial in the design of any computer system to choose the architecture model that
will be suitable, ensuring proper functioning, optimal performance, as well as the reuse and
reliable interconnection of the system with others. To this end, we opt for the MVC (Model-
View-Controller) model, which will also be very practical for managing the interaction between
the various components of our Android and web applications. We describe this architecture in
the following section.
3.4.1. MVC Architecture
The MVC (Model-View-Controller) architecture is a three-layer architecture used for
client/server programming and graphical user interface development. It is a very powerful
architectural model that plays a crucial role in application development. Its power derives from
its fundamental concept, which is the separation of data (Model), display (View), and actions
(Controller).
These three layers are described as follows:
 The Model: This corresponds to the data stored, typically in a database. In an object-
oriented language, this data is manipulated in the form of classes. The model can also
interact with the view by updating this data.
 The View: It contains only the information related to the display. The view simply displays
the content it receives without having knowledge of the underlying data. It serves as the
human-machine interface of the application.
 The Controller: The controller serves as the intermediary to retrieve information, process
it based on the parameters requested by the view (by the user), and then return the data to
the view to be displayed. It is responsible for using the data and sending it to the view.

EVENT MANAGEMENT CRM 32

 SYSTEM DESIGN

Figure 16: MVC Architecture

3.4.2 Advantages of the MVC Architecture:

The advantages brought by the MVC architecture are:

 Clear and efficient application design facilitated by the separation of data from the view
and the controller.

 Independence of data, display, and actions, providing greater flexibility for system
maintainability and scalability.
 Time-saving in maintenance and evolution of the application.

3.4.3. Software Architecture

Figure 17: Component Diagram << Event Management system >>

EVENT MANAGEMENT CRM 33

 SYSTEM DESIGN

This component diagram depicts a simplified view of a mobile application's core

functionalities for event management. Authorized admins can manage event data through a
dedicated interface, while regular users (if applicable) can view events and potentially interact
with them in a limited way.
3.4.4. Hardware Architecture

Figure 18: deployment Diagram << Event Management system >>

This deployment diagram depicts a mobile event management system. It shows a mobile
app as the user interface, where people can browse events, manage their RSVPs, and potentially
create events themselves. Behind the scenes, backend services handle the core logic like event
management and user accounts. These services interact with a database server to store all the
event and user data persistently. Optionally, an API Gateway can act as a central entry point for
app requests, and external services like payment gateways might be integrated for additional
functionalities. This diagram provides a high-level overview of how the system's components
work together

EVENT MANAGEMENT CRM 34

 SYSTEM DESIGN

4. Conclusion
This chapter was dedicated to various stages of detailed design. From refining the use
case diagram, moving on to the sequence diagram of multiple use cases to show interactions
between actors and the system. Finally, we concluded with the class diagram, which we used
to present the structure of our application.
The next chapter will contain explanations and clarifications of several concepts related
to the context of our work.

EVENT MANAGEMENT CRM 35

 SYSTEM IMPLEMENTATION

1. Introduction
After completing the modeling phase, in this chapter we begin the realization part.
The first part is devoted to presenting the hardware and software working environment
suitable for the implementation. Next, we describe the process of making the application by
showing a few screen prints. The operation of some interfaces will then be detailed.
After completing the modeling phase, in this chapter we begin the realization part. The
first part is devoted to presenting the hardware and software working environment suitable for
the implementation. Next, we describe the process of making the application by showing a few
screen prints. The operation of some interfaces will then be detailed.
2. Development Environment
2.1. Hardware Environment
To develop the application, we utilized the following hardware environment consisting
of a laptop and a mobile phone with the following specifications:

Brand hp EliteBook

Processor intel (R ) Core (TM) i5-5300U CPU @ 2.30 GHz

Memory 8.00 GB

Hard Drive 1 TB

Operating System Windows 10 Professional

Table 10Table 10: Hardware Environment

2.2. Software Environment

The choice of development tools is a critical step in the project since this choice will have
direct effects on the effort provided and the time devoted to the work, and therefore in
development costs. During the development cycle, we used Windows 10 Professional 64-bit
Edition as the operating system. Thus, we have used a set of software useful for carrying out
the various tasks of the application which are described in the following points:

EVENT MANAGEMENT CRM 36

 SYSTEM IMPLEMENTATION

Database and Backend Stack:

 A platform developed by Google for creating mobile and web applications. It provides
tools for tracking analytics, reporting and fixing app crashes, creating marketing and
product experiment.

Frontend Framework: Flutter

 Flutter: Google's UI toolkit for building mobile, web, and desktop applications with a
single codebase.
 Ensures consistency and efficiency across different platforms and devices.
 Offers a comprehensive approach to developing user interfaces with modern design
principles.
Key Features:
 Flutter allows for the creation of cross-platform user interfaces with a single codebase,
ensuring consistency and efficiency across different devices and operating systems.
 Firebase is a comprehensive platform offering real-time database, cloud storage,
authentication, cloud functions, hosting, messaging, machine learning, and analytics
services, enabling developers to build and scale apps quickly with powerful features,
seamless integration, and robust performance.
Overall Benefits:
 Utilizing each technology's strengths to deliver high-quality and performant applications.
 Comprehensive and modern approach to web and mobile application development.
 Ensures consistency and efficiency across diverse platforms, enhancing user experience.
=> ensuring consistency and efficiency across different platforms. This development
environment offers a comprehensive and modern approach to building mobile applications,
leveraging the strengths of each technology to deliver a high-quality and performant end
product.
Modeling and report :
 UML diagrams, created using tools like Draw.io, are included in the documentation to
provide insights into the design and architecture of the software system.
 Google Docs is used for writing reports, offering collaborative editing features and easy
sharing capabilities, facilitating effective communication and documentation management
throughout the development process.
Integrated development environments (IDEs) :
Visual Studio Code (VS Code):
 Lightweight and highly customizable source code editor developed by Microsoft.
 Supports multiple programming languages and frameworks.
 Features built-in Git integration, debugging tools, and extensions marketplace.
 Known for fast performance, efficient memory usage, and cross-platform compatibility.

EVENT MANAGEMENT CRM 37

 SYSTEM IMPLEMENTATION

Android Studio:
 Official integrated development environment (IDE) for Android app development by
Google.
 Based on IntelliJ IDEA and tailored for building Android applications.
 Offers comprehensive tools for designing UI, debugging, and profiling Android apps.
 Supports Kotlin, Java, and C++ programming languages.
 Integrates with Google services like Firebase and Google Play Store for app distribution.
3. Main graphical interfaces
 Authetification

Figure 19: welcome screen

Figure 20: Login screen

EVENT MANAGEMENT CRM 38

 SYSTEM IMPLEMENTATION

Figure 21: sign _in screen

EVENT MANAGEMENT CRM 39

 SYSTEM IMPLEMENTATION

Figure 22: Forget Password screen

Figure 23: Pin code screen

EVENT MANAGEMENT CRM 40

 SYSTEM IMPLEMENTATION

 Profile and Add_ Profile Screens

Figure 24: Profile_screen

EVENT MANAGEMENT CRM 41

 SYSTEM IMPLEMENTATION

Figure 25: Add_Profile_screen

EVENT MANAGEMENT CRM 42

 SYSTEM IMPLEMENTATION

 Bookings

Figure 26:bookings_screen

Figure 27:booking_details_screen

EVENT MANAGEMENT CRM 43

 SYSTEM IMPLEMENTATION

 FeedBack Screens

Figure 28: Feedback_screens

 Create_event_screen

Figure 29: Create_event_screen

EVENT MANAGEMENT CRM 44

 SYSTEM IMPLEMENTATION

4. Conclusion
In this chapter, we focused on describing the characteristics of the work environment and
outlined the hardware and software platforms on which we built our application.
Additionally, we depicted the various interfaces developed throughout the application.
Finally, we concluded this chapter with the presentation of the activity timeline.

EVENT MANAGEMENT CRM 45

 General Conclusion

In the computer science degree program, our last project was to make an application for
mobile technologies (smartphones). I got to know a fresh development platform and increased
our understanding and familiarity.

This project aligns with the applied computer science course we are pursuing from the
Faculty of science of Monastir, sponsored by Bee coders company.
In the application's implementation phase, we did a preliminary study on smartphones
and their significance in social contexts to confirm what our future app will do. This explanation
phase acted as the beginning for analysis and requirement specification. When I had defined
the objectives, I moved into the design phase to carry out the project successfully. After that, I
started the work of making it happen. In this phase, I got to know about the Flutter , Node js
and postman.
To finish, I might have some extensions for my work. In fact, I’m thinking about putting
an "Eventia" application on the Play Store as a part of my work and there could be further
development for other platforms too.

EVENT MANAGEMENT CRM 46

 Webography

1. Eventbrite. (n.d.). The Ultimate Guide to Event Management. Retrieved from

https://www.eventbrite.com/
2. Cvent. (2020). Event Management Technology Trends. Retrieved from
https://www.cvent.com/
3. Virtual Event Management. (2021). Best Practices for Virtual Events. Retrieved
from https://www.virtualeventmanagement.com/
4. Tunisian National Tourist Office. (n.d.). Discover Tunisia: Festivals and Events.
Retrieved from https://www.discovertunisia.com/
5. UNESCO. (2020). The Impact of COVID-19 on Cultural Events. Retrieved from
https://en.unesco.org/
6. Cvent. (2020). Event Management Technology Trends. Retrieved from
https://www.cvent.com/
7. Agile Alliance. (2021). Agile Software Development. Retrieved from
https://www.agilealliance.org/agile101/
8. Flutter. (n.d.). Flutter - Build apps for any screen. Retrieved from https://flutter.dev/
9. Draw.io. (n.d.). Draw.io - Flowchart Maker & Online Diagram Software. Retrieved
from https://www.draw.io/
10. Google Docs. (n.d.). Google Docs: Free Online Document Editor. Retrieved from
https://www.google.com/docs/about/
11. Visual Studio Code. (n.d.). Code editing. Redefined. Retrieved from
https://code.visualstudio.com/
12. Android Studio. (n.d.). Android Studio - the official IDE for Android. Retrieved
from https://developer.android.com/studio
13. Microsoft. (n.d.). Introduction to Model View Controller. Retrieved from
https://docs.microsoft.com/en-us/aspnet/mvc/overview/getting-
started/introduction/
14. GeeksforGeeks. (2021). Model-View-Controller (MVC) Architecture. Retrieved
from https://www.geeksforgeeks.org/mvc-design-pattern/
15. Tutorialspoint. (n.d.). MVC Framework Introduction. Retrieved from
https://www.tutorialspoint.com/mvc_framework/mvc_framework_introduction.ht
m
16. IBM. (n.d.). MVC Architecture. Retrieved from
https://www.ibm.com/docs/en/rad/9.1.1?topic=architectures-mvc-architecture
17. Techopedia. (n.d.). Model-View-Controller (MVC) Definition. Retrieved from
https://www.techopedia.com/definition/24099/model-view-controller-mvc
18. Microsoft. (n.d.). Sequence Diagrams: A UML Introduction. Retrieved from
https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-
2008/ms181341(v=vs.90)
19. Lucidchart. (n.d.). UML Sequence Diagram Tutorial. Retrieved from
https://www.lucidchart.com/pages/uml-sequence-diagram
20. GeeksforGeeks. (2021). Unified Modeling Language (UML) | Sequence Diagrams.
Retrieved from https://www.geeksforgeeks.org/unified-modeling-language-uml-
sequence-diagrams/

EVENT MANAGEMENT CRM 47

 21. Visual Paradigm. (n.d.). What is a Sequence Diagram?. Retrieved from
https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
sequence-diagram/
22. Firebase Official Documentation: https://firebase.google.com/docs
23. Firebase Google Developers Codelabs:
https://codelabs.developers.google.com/?cat=Firebase

EVENT MANAGEMENT CRM 48