Tribhuvan University

Faculty of Humanities and Social Sciences

A PROJECT REPORT ON

“EVENT MANAGEMENT SYSTEM”

Submitted to

Department of Computer Application

St.Lawrence College

In partial fulfillment of the requirements for the Bachelor in Computer Application

Submitted by

Raman Tamang [Reg.no 6-2-788-18-2021]

Pawan Shrestha [Reg.no 6-2-788-14-2021]

June 2025

Under the Supervision of

Santosh Neupane
 Tribhuvan University
Faculty of Humanities and Social Sciences

SUPERVISOR’S RECOMMENDATIONS

We hereby recommend that this project prepared under my supervision by Raman

Tamang and Pawan Shrestha entitled “ EVENT MANAGEMENT SYSTEM” in partial
fulfillment of the requirements for the degree of Bachelor of Computer Application is
recommended for the final evaluation.

SIGNATURE

Santosh Neupane

SUPERVISOR

BCA Department

St.Lawrence College

ii
 Tribhuvan University

Department of Humanities and Social Sciences

Aims International College

LETTER OF APPROVAL

This is to certify that this project prepared by RAMAN TAMANG and PAWAN
SHRESTHA entitled “EVENT MANAGEMENT SYSTEM” in partial fulfillment of the
requirements for the degree of Bachelor in Computer Application has been evaluated. In
our opinion, it is satisfactory in the scope and quality as the project for the requirement
degree.

_____________________ _____________________

Supervisor Coordinator
Mr. Santosh Neupane Mr. Basanta Gyawali

BCA Department BCA Department

St.Lawrence College St.Lawrence College

_____________________ _____________________
Internal Examiner External Examiner

iii
 ABSTRACT
Managing events manually often leads to delays, inefficiencies and human errors especially
when dealing with large numbers of participants and multiple activities. To overcome these
challenges, “NepaEvents” an Event Management System has been developed using modern
web technologies — JavaScript, React.js, Node.js, MongoDB, TailwindCSS, and Draw.io
for planning and design. This system is designed to automate event registration, participant
management, and ticket booking processes, providing a centralized platform for organizers
and attendees.

The system uses a secure and scalable database (MongoDB) to store records of events,
users, and transactions, while React ensures a responsive and dynamic front-end
experience. TailwindCSS is used for styling, offering a clean and user-friendly interface,
and Draw.io assisted in designing the system architecture and flow diagrams.

NepaEvents enhances event planning by saving time, reducing administrative effort,

minimizing human error, and offering real-time information updates. It ensures secure
access through authentication, allows easy event creation and registration, and provides
transparent tracking of participants and ticket sales.

Overall, this system addresses traditional problems like manual errors, limited accessibility,
and slow communication, offering a reliable, efficient, and scalable solution for modern
event management.

Keywords:Event Management, Organizers, Participants, Ticket Booking, JavaScript,

React, MongoDB,Node.js, TailwindCSS, Security, Real-time Updates

iv
 ACKNOWLEDGEMENT
This project has been prepared to gain practical knowledge in accordance with the Bachelor
level BCA syllabus, focusing on the development of the Event Management System. We
are thankful to my supervisor and family for the support We received throughout the
journey of working on this project. We are also grateful that through this application We
have been able to gain skills that will impact my life.

We would especially like to thank my supervisor, Mr. Santosh Neupane, whose

invaluable assistance and suggestions were crucial to the success of this project. His
guidance directed us on the right path during our research, and his patience and extensive
experience provided us with essential insights. The knowledge and skills we have gained
under his mentorship will undoubtedly serve us well in our future endeavors. We will
always be grateful for his support and guidance.

Yours sincerely,
Raman Tamang

Pawan Shrestha

v
 TABLE OF CONTENTS
SUPERVISOR’S RECOMMENDATIONS .......................................................................ii

LETTER OF APPROVAL ................................................................................................iii

ABSTRACT ...................................................................................................................... iv

ACKNOWLEDGEMENT .................................................................................................. v

LIST OF ABBREVIATIONS .........................................................................................viii

LIST OF FIGURES ........................................................................................................... ix

LIST OF TABLES .............................................................................................................. x

CHAPTER 1 ....................................................................................................................... 1

INTRODUCTION .............................................................................................................. 1

1.1 Introduction .............................................................................................................. 1

1.2 Problem Statement ................................................................................................... 1

1.3 Objectives ................................................................................................................. 2

1.4 Scope and Limitations .............................................................................................. 2

1.5 Report Organization ................................................................................................. 3

CHAPTER 2 ....................................................................................................................... 4

BACKGROUND STUDY AND LITERATURE REVIEW .............................................. 4

2.1 Background Study ..................................................................................................... 4

2.2 Literature Review ...................................................................................................... 5

CHAPTER 3 ....................................................................................................................... 6

SYSTEM ANALYSIS AND DESIGN .............................................................................. 6

3.1 System Analysis ........................................................................................................ 6

3.1.1 Methodology ...................................................................................................... 6

3.1.2 Requirement Analysis ........................................................................................ 7

3.1.3 Feasibility Analysis .......................................................................................... 10

vi
 3.1.4 Data Modeling (ER-Diagram) .......................................................................... 10

3.1.5 Process Modeling (DFD): ................................................................................ 11

3.2 System Design ......................................................................................................... 13

3.2.1 Architectural Design......................................................................................... 14

3.2.2 Database Schema Design ................................................................................. 15

3.2.3 Interface Design (UI Interface/Interface Structure Diagrams) ......................... 16

3.3 Algorithm ................................................................................................................. 18

CHAPTER 4 ..................................................................................................................... 22

IMPLEMENTATION AND TESTING ........................................................................... 22

4.1 Implementation........................................................................................................ 22

4.1.1 Tools Used ........................................................................................................ 22

4.1.2 Implementation Details of Modules ................................................................. 24

4.2 Testing ..................................................................................................................... 29

4.2.1 Unit testing ....................................................................................................... 29

CHAPTER 5 ..................................................................................................................... 32

CONCLUSION AND FUTURE RECOMMENDATIONS ............................................. 35

5.1 Lessons Learnt / Outcome ....................................................................................... 35

5.2 Conclusion............................................................................................................... 35

5.3 Future Recommendations........................................................................................ 36

APPENDICES .................................................................................................................. 37

REFERENCES…………………………………………………………………………..41

vii
 LIST OF ABBREVIATIONS
CASE Computer Aided Software Engineering

DFD Data Flow Diagram

ER Entity Relationship

UX User Experience

JS Javascript

SQL Structured Query Language

UI User Interface

SDLC Software Development Life Cycle

viii
 LIST OF FIGURES

Figure 3.1: Agile Model .…………..................................................................................... 6

Figure 3.2: Use Case Diagram …………………............................................................... 8

Figure 3.3: ER Diagram ..................................................................................................... 11

Figure 3.4: DFD Level-0.................................................................................................... 11

Figure 3.5: DFD Level-1 Admin' Side ............................................................................... 12

Figure 3.6: DFD Level-1 user’s side.................................................................................. 13

Figure 3.7: Architectural Design ....................................................................................... 14

Figure 3.8: Database Schema Design ................................................................................ 15

Figure 3.9: Interface Design for Home Page ..................................................................... 16

Figure 3.10: Interface Design for Event Page ………........................................................ 17

Figure 3.11: Interface Design for Venue Detail Page ........................................................ 17

Figure 3.12: Interface Design for Dash Board Page ........................................................... 18

ix
 LIST OF TABLES

Table 1: Use Case Descriptions.......................................................................................... 9

Table 2: Test Case for User Registration ........................................................................... 29

Table 3: Test Case for User Login .................................................................................... 30

Table 4: Test Case for Admin Login ................................................................................ 30

Table 5: System Test Case for User Registration .............................................................. 31

Table 6: System Test Case for User Login.......................................................................... 31

Table 7: System Test Case for Admin Login..................................................................... 32

Table 8: System Test Case for Event Add and Deletion.................................................... 32

Table 9: System Test Case for Venue Add and Deletion.................................................... 33

Table 10: System Test Case for Buying Event Ticket....................................................... 33

Table 11: System Test Case for Venue Booking……………………………………….... 33

x
 CHAPTER 1

INTRODUCTION
1.1 Introduction

In today's technology-driven world, the management and organization of events have been
significantly enhanced by web-based platforms. Companies and individual users are
increasingly relying on online solutions to plan, promote, and manage events efficiently.
The Event Management System – NepaEvents is a web-based platform designed to
simplify the process of organizing events, selling tickets, and managing participants
remotely via the internet.

This project focuses on developing a comprehensive Event Management System that

allows users to create and organize events seamlessly. Users can register and log in through
their email IDs, enabling personalized experiences and enhanced security. The system
integrates an interactive event location map, allowing participants to easily view and
navigate to event venues. Additionally, users can purchase event tickets online, ensuring
convenience and reducing the need for physical ticket distribution.

The Event Management System brings several advantages over traditional methods of
event planning, such as reduced manual errors, real-time updates, and the flexibility for
organizers and participants to manage and access event information anytime, anywhere.
By storing event data securely in a central database, the system allows organizers to track
ticket sales, monitor attendance, and make informed decisions to improve event execution.

Therefore, this project aims to create a user-friendly, secure, and efficient platform that
streamlines the entire event lifecycle—from planning and ticketing to participation and
feedback—while enhancing user experience with modern digital tools.

1.2 Problem Statement

 Manual event management is time-consuming.
 Participants face difficulties in buying tickets and accessing event information offline.
 Organizers struggle with promoting events and tracking registrations.
 There is a need for a web-based system to organize events, sell tickets online, and
show event locations on an interactive map.

1
1.3 Objectives
Normal users, event organizers, and companies all can benefit from an online event
management system in a number of ways. This system aims to be useful in the following
ways:

1. To enable users to book tickets online, search venues, receive event

recommendations, and make real-time payments.
2. Integrate an interactive map feature to help users locate event venues easily.
3. To implement a recommendation algorithm that suggests relevant events to users
based on their interests, behavior, and event history.
4. To integrate a dynamic pricing algorithm that adjusts ticket prices based on
demand, booking time, and other market factors, optimizing revenue for event
organizers.

1.4 Scope and Limitations

Scope:

● User Registration and Login:

Users can securely register and log in using their email IDs to access personalized
features.
● Event Browsing and Ticketing:
Participants can browse events, view detailed information, purchase tickets online, and
receive instant confirmation. An integrated interactive map will help users locate event
venues easily. Cross-Device Accessibility and Secure Payments: The platform supports
secure online transactions and is accessible on mobile phones, laptops, and desktops.

● Admin Features:
Administrative users can monitor events, manage venues, and generate reports on ticket
sales and attendance.

Limitations
● Connectivity & Third-Party Dependency: The system requires a stable internet
connection and relies on third-party services for payments and mapping, making it
vulnerable to external service downtimes or inaccuracies.

2
● Limited Scope: It does not manage physical event logistics such as seating
arrangements or on-site security.
● Data Security Risks: Although user data security is prioritized, the system cannot fully
guarantee protection against sophisticated cyberattacks.

1.5 Report Organization

This report consists of five chapters which will cover the designing and the development
of Event Management System.

Chapter One: This chapter includes the system and the problems, given an overview about
the study. It includes introduction, problem of statement, objectives, and solution of the
website.

Chapter Two: This chapter covers the literature review which is the previous related work
that has been done before. It also includes the description of the website where we have
taken the reference.

Chapter Three: This chapter explains the selected methodology that we are going in this
project. This chapter shows the design of the system. It includes Data Flow Diagram, Use
case Diagram, Entity Relation Diagram, Activity Diagram etc.

Chapter Four: This chapter discusses the implementation and testing. It includes the
overall description of the modules that we have implemented into our application. We have
shown the test cases.

Chapter Five: This chapter discusses the conclusion, recommendation and future works
to improve this study

3
 CHAPTER 2

BACKGROUND STUDY AND LITERATURE REVIEW

2.1 Background Study
In today's digital era, a large part of our daily activities, from shopping to education and
work, is managed online. This shift has opened new opportunities to streamline many
traditional processes, and event management is no exception. Whether for small
gatherings, corporate events, concerts, or educational workshops, organizing events online
has become an attractive and efficient solution. Here are a few reasons why adopting an
online event management system can greatly benefit organizers and participants:
•Organize and manage events from anywhere: Today’s busy lifestyles leave little time for
complicated event planning and management. An online event management system allows
organizers to create, update, and monitor events remotely at any time, providing the
flexibility to manage events from the office, home, or on the move, using any device with
an internet connection.
•Easier participant access and ticket purchasing: An online system enables participants to
easily discover events, register, and purchase tickets without visiting a physical location.
This convenience helps attract a larger and more diverse audience, as individuals can
complete their bookings within minutes from anywhere.
•Boost attendance and engagement: By offering easy online registration and ticketing, events
become more accessible to a wider audience. Additionally, event updates, notifications, and
reminders can be sent digitally, helping to boost participation and improve overall engagement.
•Reduce physical infrastructure and costs Managing events online minimizes the need for
traditional resources like printed tickets, physical registration booths, and manual staff
coordination. This leads to significant savings in operational costs and makes the event
management process more environmentally friendly.

4
 • Real-time updates and improved event tracking: An online platform allows organizers
to instantly track ticket sales, monitor registrations, and communicate with attendees.
This improves decision-making, ensures better event preparation, and enhances the
overall experience for both organizers and participants

2.2 Literature Review

This paper discusses the integration of IoT and cloud technologies in event management
systems to streamline real-time data access, automate scheduling, and improve
scalability.“A Smart Event Management System Using Cloud and IoT” [1].
The authors propose a blockchain-based ticket verification mechanism to eliminate ticket
fraud and ensure authenticity, enhancing overall system security.“Design and
Implementation of Online Event Management System with Ticket Verification Using
Blockchain” [2].
This paper presents a machine learning model that recommends events to users based on
their preferences and previous activity, improving engagement and user satisfaction. “AI-
Powered Personalized Event Recommendation Engine” [3].
The study focuses on designing a mobile-first event management system optimized for
various screen sizes and internet speeds, addressing accessibility challenges in rural and
urban areas alike. “A Mobile-Based Event Management Application to Improve User
Accessibility” [4].

This research explores integrating biometric authentication in event check-ins and

ticketing, highlighting its effectiveness in reducing identity fraud and improving user
verification. “Enhancing Security in Event Management Systems Through Biometric
Verification” [5].

The authors present a stakeholder-focused service architecture that enhances collaboration

among event organizers, participants, and developers, emphasizing flexibility and
adaptability. “Event Management as a Service: A Stakeholder-Driven Architecture” [6].

5
 CHAPTER 3

SYSTEM ANALYSIS AND DESIGN (Structured

Approach)
3.1 System Analysis
The system is analyzed using the structured approach, which emphasizes the
decomposition of processes and clear definition of data and control flows. This approach
is ideal for understanding system functionalities through hierarchical modeling and use-
case analysis.

3.1.1 Methodology
The SDLC model implemented for this project is the Agile methodology. Agile is an
iterative and incremental approach to software development that emphasizes flexibility,
collaboration, and customer feedback. It allows teams to adapt to changing requirements
and continuously improve the product through frequent iterations known as sprints.

We selected Agile because it supports dynamic project environments where requirements

may evolve over time. The Agile process involves repeated cycles of planning,
development, testing, and review, enabling early detection of issues and faster delivery of
usable features.

This model is well-suited for projects that demand quick turnaround, continuous user input,
and evolving goals.

Figure 3.1: Agile Model

6
3.1.2 Requirement Analysis

i. Functional Requirements:

 The system must only allow users with valid id and password to enter the
system.
 User must be able to view different events and venues with their location map.
 User must be able to make payments to book venues and buy event tickets.
 User must receive notifications and email receipts of bookings.
ii. Non-functional Requirements:

 Usability requirement: The system is designed to run through standard web

browsers, making it intuitive and easy to use for all users who are already
familiar with typical browser interfaces. No additional software is required,
ensuring a smooth and user-friendly experience.
 Availability requirement: The system is accessible to users at all times—24
hours a day, 7 days a week, throughout the entire year. This ensures
uninterrupted access for event planning, registration, and management activities
whenever needed.
 Reliability requirement: Given the critical nature of event data, the system
must maintain high reliability. Any data loss or inaccuracy could lead to
significant issues, so it is essential that the system consistently performs as
expected and ensures the integrity of all stored information.

Use Case Diagram

A use case diagram is a graphic that illustrates how different actors, such as users or
systems, interact with a system. It demonstrates how users or outside systems work with a
system to accomplish particular objectives. The components of a use case diagram are:

● Actors
● Use cases
● System boundary

The following use-case diagram illustrates the key interactions between users and the
system:

7
Figure 3.2: Use Case Diagram

8
Use Case Descriptions:

Table 1: Use Case Descriptions:

Use Case Actor Description

Allows organizers to create new events by

Add Event User
specifying event details.
Enables admin to add venues that can be
Add Venue Admin
booked for events.
Approve/Reject Venue Admin reviews and approves or denies venue
Admin
Booking Requests booking requests.
Request Venue Booking Organizers can request a venue by submitting
User
with Event Details event details.
Users can pay for booked tickets or venue
Make Payment User
services.
Shows the total earnings from a particular
View Event Earnings User
event.
View Overall Earnings Admin can track total platform earnings across
Admin
from Platform all events and venues.
Customers can browse and purchase event
Buy Event Tickets User
tickets online.

9
3.1.3 Feasibility Analysis

Feasibility analysis helps to determine whether the proposed system is practical and viable
to develop and implement. The study is divided into three core areas: technical,
operational, and economic feasibility.

i. Technical Feasibility
The proposed Event Management System is technically feasible as it relies on
widely adopted open-source technologies such as Node.js for the backend, React
or Next.js for the frontend, and MongoDB for data storage. These technologies
are well-supported, scalable, and suitable for building web-based platforms.
ii. Operational Feasibility
Operationally, the system aligns well with the needs of its users. It supports three
main roles—admin, event organizer, and customer—each with clearly defined
tasks. The interface is designed to be clean, responsive, and easy to navigate,
ensuring that users can perform their actions with minimal training. Workflows
such as booking requests, ticket purchases, and revenue tracking are streamlined
to reduce manual processes and increase operational efficiency once deployed.
iii. Economic Feasibility
The project is economically viable due to low development and hosting costs.
Using free tools and affordable cloud services keeps expenses minimal. The
system has strong potential for revenue through ticket sales and service charges,
ensuring long-term sustainability.
3.1.4 Data Modeling (ER-Diagram)

A visual depiction of the connections among the entities in a database is called an entity-
relationship diagram. It displays the relationships between the various things found in a
database. ERDs act as blueprints for data relationships.

A visual depiction of the connections among the entities in a database is called an entity-
relationship diagram. It displays the relationships between the various things found in a
database. ERDs act as blueprints for data relationships.

The figure below shows the ERD of our system. It represents the entities its attributes and
relation with other entity. It shows how the entities are connected and what their
relationships are. They support relational database modeling in both its conceptual and
physical features.

10
 Figure 3.3: ER Diagram

3.1.5 Process Modeling (DFD):

A Data Flow Diagram is a graphic that shows the flow of data through a system or process.
It displays the connections between data inputs, outputs, storage locations, and paths
between destinations.
In the figure below, we have a level-0 DFD of the system. It is a simple representation of
our system. The figure demonstrates the flow of the data and processes between the user
and admin for booking venue and event creation. Based on the diagram, we can visualize
how the system works.

Figure 3.4: DFD Level-0

11
Figure 3.5: DFD Level-1 Admin' Side

12
 Figure 3.6: DFD Level-1 user’s side

3.2 System Design

The process of defining a system's architecture, modules, interfaces, and data in order to
meet predetermined requirements is known as systems design. One may consider systems
design to be the product development application of systems theory.

13
3.2.1 Architectural Design
This event management system is built using a client-server architecture. It consists of a
client-side User Interface (UI) for user interaction, a web server for processing requests
and handling logic, and a database for data storage. This design guarantees a smooth user
experience and facilitates effective communication.

Figure 3.7: Architectural Design

14
3.2.2 Database Schema Design

Figure 3.8: Database Schema Design

The database schema design defines the fundamental components of this event
management system, including users, events, venues, tickets, category, etc. It uses foreign
keys to create links between tables, such as connecting events to venue or tickets to users,
and primary keys to uniquely identify records within each table.

15
3.2.3 Interface Design (UI Interface/Interface Structure Diagrams)
The goal of NepaEvents design is to provide a user-friendly online shopping environment
with a plant sales focus. The navigation, content, and layout of a website are planned and
visualized using user interface and interface structure diagrams. The homepage, product
pages, checkout, account management, and shopping cart are important pages. In addition
to guaranteeing simple navigation and a flawless shopping experience, the design places
an emphasis on a clear, organic look.

Figure 3.9: Interface Design for Home Page

16
 Figure 3.10: Interface Design for Event Page

Figure 3.11: Interface Design for Venue Detail Page

17
 Figure 3.12: Interface Design for Dash Board Page

3.3 Algorithm:
1. Dynamic Price Algorithm:
The dynamic pricing algorithm used in the event booking system automatically adjusts
ticket prices based on real-time factors such as demand and timing. Instead of using a fixed
price, the system increases or decreases the ticket price depending on how many tickets
have already been sold and how close the event date is. This approach helps reflect the true
market value of a ticket at any given time. When demand is high or the event is
approaching, prices rise to encourage early purchases and maximize revenue. Conversely,
when demand is low or the event is far off, prices remain lower to attract more buyers. This
pricing strategy ensures a balance between affordability and profitability, making the
system more adaptive, competitive, and efficient for both organizers and attendees.

18
2. Recommendation Algorithm:
The event booking system includes a recommendation mechanism that combines
collaborative filtering and content-based filtering to provide personalized event suggestions
for users. Collaborative filtering analyzes the ticket purchase history of users and finds
others with similar behavior, then recommends events attended by those similar users that
the current user hasn’t experienced yet. This allows the system to suggest relevant events
based on collective user trends and shared interests. On the other hand, content-based

19
filtering focuses on the individual user's preferences by analyzing the categories of events
they have favorited or shown interest in and recommending similar events they haven't yet
explored. By combining these two approaches, the system ensures users receive
recommendations that reflect both their personal tastes and the interests of like-minded
individuals, enhancing event discovery and boosting overall engagement.

20
21
 CHAPTER 4

IMPLEMENTATION AND TESTING

4.1 Implementation

4.1.1 Tools Used

Front-end Tools:

 React: React is a JavaScript library used for building user interfaces, especially
single-page applications (SPAs). We used React in this project to create reusable
UI components, manage state, and ensure efficient rendering of dynamic content,
improving both performance and user experience.
● Tailwind CSS: Tailwind CSS is a utility-first CSS framework used for rapidly
building custom designs. It was used in this project to design responsive and
modern user interfaces by applying utility classes directly in the HTML. This
approach allowed for faster styling without needing to write custom CSS for each
element.
● JavaScript: We accomplished client-side validation with JavaScript. It allows
validation logic to be implemented directly on the user's browser, giving prompt
feedback and error checking for user inputs into the system.

Backend Tool:

● Express.js: Express.js serves as the backend framework for building the Event
Management System NepaEvents. It handles essential functionalities such as user
authentication, event creation, ticket booking, API routing, and integration with
external services like databases and maps. Express.js allows developers to structure
the application logically using middleware and route handlers, ensuring scalability,
maintainability, and performance".

Database:

● MongoDB: MongoDB is a NoSQL database that stores data in a flexible, JSON-

like format. In this project, MongoDB was used to store and manage various types

22
 of data such as event details, user information, and ticketing records. Its flexibility
and scalability made it an ideal choice for the system's backend".

Documentation Tools:

● MS Word 2016: We used MS Word 2016 for preparing proposal and report as it
is one of the popular word processing programs for producing extensive project
documentation, such as project plans, requirements, user manuals, and other
project-related documents.
● Draw.io: We used Draw.io to create flowcharts and other diagrams as well as visual
representations of system design. It is used throughout the project to draw diagrams
that show the parts, relationships, and data flows of the system.
● Microsoft Project: It is intended to help us with schedule development, task
assignment, progress monitoring, budget management, and workload analysis for
project managers.

● Figma: Figma is a cloud-based UI/UX design tool used to create visual layouts and
interactive prototypes. For this Event Management System NepaEvents, Figma
helps design key interfaces like login, event creation, and ticket booking pages. It
enables real-time collaboration between designers, developers, and stakeholders.
Interactive prototypes created in Figma simulate user journeys and improve
usability. The tool ensures visual consistency and provides a clear guide for
frontend development. It bridges the gap between design and backend functionality
developed in Express.js. Overall, Figma enhances the design process and improves
user experience.

23
4.1.2 Implementation Details of Modules

Login Module:

By entering their email and password, users can access their accounts. The provided
credentials are first matched with the database records if the records match a token is stored
in the client’s browser cookies which is required for sending request to other protected API
routed.

Add new event:

The code is designed to upload event information to a database. First, it processes a form
submission, then inserts the data into a database, and redirects the user to a success page if

24
the insertion is successful. The code enables the admin to add details of a event, such as
title, ticket price, location and the category into the database.

If the data is not able to be inserted, an alert is shown that says “Error creating a event”,
otherwise the product is added and shown at the bottom of the list.

Edit event details:

The code is designed to update the details of a event in a database. First, it checks the fields
sent by the client and only updates those fields leave others the same, and displays a success
or error message accordingly.

25
Delete Event:

The code is designed to get the event id from the request parameter. It then finds the event
with the given id and deletes a record from the ‘events’ table based on the ‘id’. Then, the
event is deleted from the database.

Venue Booking function:

The users can choose a venue for organizing an event. The user fills the event detail which
he/she is going to host in that venue and submits the booking request if the venue is booked
for the selected date user sees and unavailable error, if not the request is forwarded to the
admin. The admin approves the booking request, then user is notified to make payment for
26
that booking. Once the payment is successfully made the event is created and the venue
appears in my booking section where the user can view the events revenue.

Stripe Payment Function:

In the stripe payment function, the code first fetches the booking data from the provided
venue booking if. Then the user is redirected to the session url which is the stripe payment
page After the user clicks the checkout button, the checkout process is completed and the
user receives a pdf receipts in the email and the purposed event is created and made
available for sales

27
28
4.2 Testing
Finding every flaw in our project was the goal of the system testing procedure. It will be
determined whether or not the software operates as intended after it was exposed to a series
of test inputs and several observations were made. Our project underwent two testing
phases.

4.2.1 Unit testing

Unit testing is started after a module has been developed and approved for review. To test
a single module, we must supply an entire environment, meaning that in addition to the
module we would need:

● The methods that the module that is being tested calls that are part of other modules.
● Non-local data structures accessed by the module.
● A process for invoking the test module's functions with the proper arguments.

User Registration

Table 2: Test Case for User Registration

Test Test Case Test Input Expected Actual Output Test
Id Description Output Result

1. Registration coder.gmail.com Display an Displays Pass

with an error “Please
invalid email message include an ‘@’
in the email
address.’coder.
gmail.com’ is
missing an
‘@’.
2. Registration Password: code Display an Displays Pass
with error “Password
password less message must be at
than 8 least 8
characters characters”

29
 3. Registration Full Name: Event User is User is Pass
with correct Email: directed to directed to the
details in all [email protected] the login login page.
fields Password: event123 page.
Confirm Password:
event123

User Login

Table 3: Test Case for User Login

Test Test Case Test Input Expected Actual Test
Id Description Output Output Result
1. Login through Email: Displays Displays Pass
an [email protected] message for “User not
unregistered unregistered found”.
account’s user.
email
2. Login through Email:[email protected] Displays Displays Pass
an incorrect Password: 123evrnt message for “Invalid
password an incorrect password”.
password.
3. Login through Email: User is User is Pass
correct [email protected] logged into logged in.
credentials Password: event123 the website.

Admin Login

Table 4: Test Case for Admin Login

Test Test Case Test Input Expected Actual Output Test
Id Description Output Result
1. Login with Email: [email protected] Displays error Displays Pass
an invalid message. “User Not
email Found”.

2. Login with Password: myadmin Displays error Displays Pass

an invalid message. “Invalid
password Password ”.

30
 3. Login with Email: Admin is Admin is Pass
correct [email protected] logged in. logged in.
credentials Password: raman@1234

4.2.2 System testing

System testing is an extensive assessment procedure that makes sure the system operates
reliably, securely, and provides a satisfying user experience prior to launch. To find and
address defects or other problems, it involves a variety of testing techniques.

User Registration
Table 5: System Test Case for User Registration
Test Test Case Test Input Expected Actual Output Test
ID Description Output Result
1. Register with Email: Redirect the Redirects the Pass
valid credentials [email protected] user to login user to login
and click on Password: event123 page page
sign-up button Confirm Password:
event123

2. Registration Email: User is not Displays Pass

with invalid [email protected] registered. message to
credentials Password: event123 input correct
Confirm Password: details.
event123

User Login

Table 6: System Test Case for User Login

Test Test Case Test Input Expected Actual Test
ID Description Output Output Result
1. Login with valid Email: Redirect the Redirects the Pass
user credentials [email protected] user to home user to home
and click on login Password: event123 page page
button

31
 Confirm Password:
event123

2. Login with Email: Email is not Displays Pass

invalid user [email protected] logged in. error
credentials Password: event123 message.
Confirm Password:
event123

Admin Login

Table 7: System Test Case for Admin Login

Test Test Case Test Input Expected Actual Test
ID Description Output Output Result
1. Login with Email: Redirect to Redirect to Pass
valid admin [email protected] admin admin
credentials Password: raman@1234 dashboard. dashboard.
and click on
login button
2. Login with Email: Admin is not Admin login Pass
invalid admin [email protected] logged in. failed.
credentials Password: raman@1234

Adding and deleting of event by admin

Table 8: System Test Case for Event Add and Deletion

Test Test Case Description Output Test
ID Result
1. Admin adds events in admin The event added by admin is shown Pass
plane in the admin panel

2. Admin removes event in admin The event is removed from admin Pass
panel panel

3. User views events in the user’s The users can see all the events Pass
panel created by admin and organizers

32
Adding and deleting of venue by admin

Table 9: System Test Case for Venue Add and Deletion

Test Test Case Description Output Test
ID Result
1. Admin adds venue in admin plane The venue added by admin is shown Pass
in the admin panel

2. Admin removes venue in admin The venue is removed from admin Pass
panel panel

3. User views venues in the user’s The users can see all the venues Pass
panel created by admin and request
booking

Buying event tickets and sending pdf tickets to user’s email

Table 10: System Test Case for Buying Event Ticket
Test Test Case Description Output Test
ID Result
1. User view event detail The user can see event’s price, real Pass
location map, performing artist, etc

2. User can apply promo code The user can see discounted prices Pass
if the promo code is valid

3. User clicks buy ticket button Once the payment is made email + Pass
system notification is sent to user
with pdf ticket

Booking venue for organizing event

Table 11: System Test Case for Venue Booking
Test Test Case Description Output Test
ID Result
1. User view venue detail The user can see venue’s price, real Pass
location map, capacity, etc
2. User clicks book now button Event description form is shown Pass

33
3. User fills the form and submits If the venue is already booked for Pass
with already booked date that day show unavailable message

4. User fills the form and submits The user sees a success request Pass
with available date message and waits for admin
approval
5. User gets approval and proceeds After payment, user gets receipt via Pass
to payment email & notification; event is
created and made available for sale

34
 CHAPTER 5

CONCLUSION AND FUTURE RECOMMENDATIONS

5.1 Lessons Learnt / Outcome

The lessons that we learnt during the course of this project are given below.

● System Design & Development Insights:

The Understood the importance of requirement gathering, user-centered design, and

scalability for building a reliable and user-friendly system. Emphasized planning to
prevent scope creep and ensure the system meets both organizer and attendee needs
efficiently.
● Communication skills:

The group's communication abilities were enhanced by this effort in both written
documents and vocal exchanges. We learned how to effectively communicate our ideas
and figure out our shortcomings.
● Problem-solving skills:

We were able to hone their problem-solving abilities thanks to the project's many
hurdles. We gained knowledge on how to recognize various problems with the system
and put fixes in place to fix them.
● Report-writing:

Along with learning how to utilize various case tools, such as use case diagrams, charts,
data flow diagrams, and ER-diagrams, among others, we have also learned how to
construct proposals and project-related documentation.

5.2 Conclusion

The Event Management System has proven to be an effective tool for simplifying the event
planning and ticketing process. By digitizing the event organization process, it allows for
easier access, better organization, and faster transactions for both event organizers and
attendees. The secure user login, seamless event management, and real-time ticketing
system help ensure that the process remains efficient, transparent, and fair. However,

35
challenges remain, particularly regarding system accessibility, ensuring all users are
familiar with the platform, and continuing to maintain robust security to protect user data
and financial transactions.

To improve the system further, it is important to focus on expanding accessibility features

for users with limited technological literacy and to continue enhancing security measures
to safeguard users' personal and payment data. This will make the Event Management
System more inclusive, secure, and user-friendly for future events.

5.3 Future Recommendations

Some future recommendations for this project are stated below.

● AI Integration: Incorporate AI-driven features such as personalized event

recommendations, tailored schedules, and advanced analytics to enhance user
experience.
● Blockchain for Security: Utilize blockchain technology to ensure ticket
authenticity, prevent fraud, and make each ticket unique and verifiable.
● Biometric & Mobile Enhancements: Introduce biometric authentication and
integrate mobile wallets to improve security and simplify the ticket purchasing
process.

● Improved Accessibility: Focus on making the system more accessible across

devices, platforms, and varying internet speeds to reach a broader audience.

● Stakeholder Collaboration: Encourage ongoing collaboration between

developers, event organizers, and stakeholders to ensure the system remains
adaptive, transparent, and effective for all event types.

36
APPENDICES

Login Page

Admin’s Dashboard

37
Product List Page in Admin’s Dashboard

User Dashboard

38
39
40
 References

[1] M. Singh and R. Kaur, "A Smart Event Management System Using Cloud and IoT,"
Electrical and Electronics (ICSTCEE), p. 1–6, 2021.

[2] N. Gupta and A. Sharma, "Design and Implementation of Online Event Management
System with Ticket Verification Using Blockchain," ICCCA, p. 1–5., 2020.

[3] S. Patel and M. Joshi, "AI-Powered Personalized Event Recommendation Engine,"

ICAIA, p. 103–108, 2022.

[4] R. Dey and P. Saha, "A Mobile-Based Event Management Application to Improve
User Accessibility," ICCCS, p. 452–456, 2021.

[5] A. Mehta and k. Iyer, "Enhancing Security in Event Management Systems Through
Biometric Verification," IEEE Transactions on Information Forensics and Security,
p. 2340–2348, 2020.

[6] S. R. Das and T. Banerjee, "Event Management as a Service: A Stakeholder-Driven

Architecture," IEEE Access, p. 134512–134523, 2021.

41