Technology Project Report

(2021-2025)

EventBliss

BSIET- FALL-(2021)

Submitted by

Shaiza Noor FUI-FURC-F21BSET033

Muneeb Iqbal FUI-FURC-F21BSET021

Fatima Kazmi FUI-FURC-F21BSET012

PROJECT SUPERVISOR

Asad Javed

Lecturer

Department of Engineering Technology

Information Engineering Technology Program

Foundation University School of Science and Technology

 ACKNOWLEDGEMENTS
First of all, we would like to thank Allah Almighty, who gave us the courage and
strength to complete this project report. We would like to thank our project supervisor,
Sir Abrar Ahmed and our HOD Engineering Technology respected Sir Dr. Ateeq Ur
Rehman. Without his assistance and dedicated guidance in every step throughout the
learning process of various Engineering courses, this project would have never been
accomplished. We would also like to thank our other course supervisors for their
continues support and understanding.
Presenting millions of appreciations to our beloved parents, siblings, and all the
admirers, for their encouragement and their endorsement. Who stood with us at every
moment and gave us the right zest and without them it was not possible for us to
complete this project.

Thank you very much.

20 December, 2023.

a
 COPYRIGHT STATEMENT
Copyright in text of this report rests with the student authors Fatima Kazmi, Shaiza
Noor, Muneeb Iqbal. Copies (by any process) either in full, or of extracts, may be
made only in accordance with instructions given by the author. Details may be obtained
by the Librarian. This page must form part of any such copies made. Further copies (by
any process) of copies made in accordance with such instructions may not be made
without the permission (in writing) of the author. The ownership of any intellectual
property rights which may be described in this project is vested in FUI, subject to any
prior agreement to the contrary, and may not be made available for use by third parties
without the written permission of the FUI, which will prescribe the terms and conditions
of any such agreement.

b
 CERTIFICATE OF COMPLETION
This is to certify that this project report entitled “Event Bliss” by Fatima Kazmi(012),
Shaiza Noor (033), Muneeb Iqbal (021), submitted in partial fulfillment of the
requirements for final year project during the academic year 2021-25, is a bonafide record
of work carried out under my guidance and supervision.

Project Supervisor
Name: Abrar Ahmed
Designation: Lecturer

c
 STATEMENT OF ORIGINALITY
We namely Fatima Kazmi, Shaiza Noor, and Muneeb Iqbal Submitting final year
Project Report Phase-1 titled “Event Handler”. State that I/we clearly understand what
plagiarism is and we have also read about it using online sources. As such, I/we claim
that this entire work (code, reports etc.) is our own effort. We have not used/copy or
pasted or paraphrased even a single line of code or sentence from any other source
without giving a proper reference to it. Based on our confidence in our originality,
we allow the University to run anti-plagiarism software on the report.
We understand that if now, or in the future, ever it is found out that we have not been
honest and have plagiarized, the university will take action and will result in
disciplinary action, such as the cancellation of our degree and I/we can be liable for any
subsequent punishments as deemed appropriate by the University as well as the Higher
Education Commission Pakistan.

____________
Signature
Fatima Kazmi
Date:

____________
Signature
Shaiza Noor
Date:

____________
Signature
Muneeb Iqbal
Date:

d
 ABSTRACT
The goal of this project is to completely transform the field of event planning by
launching the Event Handler website, a cutting-edge online tool that makes planning a
variety of events easier and more enjoyable. Traditional event management systems
frequently have limited access to problem details, necessitate in-person visits for issue
resolution, and lack comprehensive online support. Acknowledging these flaws,
EventBliss (EB) presents itself as a way to close these gaps and revive the event
organizing process. The objective of EB is to offer an easy to use online stage that
simplifies it for individuals and associations to coordinate and manage occasions of
every kind imaginable. This stage utilizes cutting edge innovation to empower clients
to follow issues connected with occasions, recover thorough data about their issues, and
exploit different administrations, without visiting face to face. Furthermore, we will use
AI algorithms for image recognition, dynamic budgeting and recommendations which
will be for the convenience of users.
The essential objective of EventBliss is to give a simple to-involve interface for
occasion arranging that empowers clients to easily oversee spending plans, redo
occasion subtleties, set inclinations, and access broad help administrations. Through the
coordination of cuttingedge innovation with an instinctive point of interaction, this
stage desires to lay down a good foundation for itself as the favored decision for
individuals, associations, instructive organizations, and neighborhood affiliations
searching for a basic, successful, and extensive strategy for overseeing occasions.
Through its devotion to ease of use, exhaustive critical thinking, and a scope of
administrations took special care of different occasion necessities, EventBliss means to
rethink the field of occasion arranging, transforming each occasion into a stunningly
arranged and remarkable experience for every one of those included.

e
 TABLE OF CONTENTS
INTRODUCTION ......................................................................................................... 1
1.1. Introduction: .................................................................................................... 1
1.2. Project Scope: .................................................................................................. 2
1.3. Intended Audience: ......................................................................................... 2
1.4. Existing system: .............................................................................................. 3
1.5. Problem definition:.......................................................................................... 3
1.6. Market Possibility: ………… ................................................................................ 4
1.7. Block Diagram: ............................................................................................... 5
LITERATURE REVIEW .............................................................................................. 6
2.1 Literature review................................................................................................... 6
METHODOLOGY ........................................................................................................ 8
3.1 Introduction: ......................................................................................................... 8
3.2 Research Design: .................................................................................................. 8
3.3 Data Analysis:....................................................................................................... 9
3.4 System Development Methodology: .................................................................... 9
3.5 System Requirements: .......................................................................................... 9
3.6 Functional Requirements: ................................................................................... 10
3.7 Nonfunctional requirement: ................................................................................ 12
3.8 Use Case Diagram: ............................................................................................. 14
Design and Implementation ......................................................................................... 23
4.1 Design of Our Project: ........................................................................................ 23
4.2 Implementation requirement: ............................................................................. 24
4.3 Tools and Technologies: ..................................................................................... 25
Conclusion ................................................................................................................... 26
5.1 Conclusion: ......................................................................................................... 26
5.2 User’s Benefits by accessing our website: ......................................................... 26
5.3 Filters: ................................................................................................................. 27
5.4 Limitations: ......................................................................................................... 27
5.5 Uniqueness of Our Website: ............................................................................... 27

f
 LIST OF TABLES
Table 1: Benchmarking. ............................................................................................................................ 3
Table 2: Functional Requirements ........................................................................................................... 9
Table 5: Vendor Use-Case.........................................................................Error! Bookmark not defined.

LIST OF FIGURES
Figure 1 : Block Diagram........................................................................................................................... 5
Figure 2: Use-Case Diagram. ................................................................................................................ 13

g
Figure 3: User Use-Case Diagram. ....................................................................................................... 14
Figure 4: Vendor Use-Case Diagram...................................................................................................... 17
Figure 5: Admin Use-Case Diagram. ....................................................................................................... 20
Figure 6: Sequence Diagram. ................................................................................................................ 24
Figure 7: Class Diagram. ....................................................................................................................... 25
Figure 8: ERD. ...................................................................................................................................... 26

h
 LIST OF ABBREVIATIONS
ABBREVATION EXPLANATION
IT. Information Technology.
EB. Event Bliss.
UC. Use Case.
SQL Server. Structured Query Language.
SMS. Short Message Service.
PHP Language. Hypertext Preprocessor.
WO. Wedding Organizer.
UX User Experience.
UI User Interface.
ERD. Entity Relationship Diagram

i
 CHAPTER 1: INTRODUCTION

CHAPTER 1
INTRODUCTION

1.1 Introduction:
We recognize the importance of honoring these occasions, whether they are birthdays,
marriages, partings, game evenings, film evenings, school functions, intimate home
celebrations, and more. At EB, we give you the power of command. You can easily
share event details and set a budget with others using your customized profile. Using
our cutting-edge technology, we create custom event packages that perfectly match
your goals and budget. EventBliss is available to assist in creating treasured memories
whether you are an experienced event planner or starting your most important event.
Our goal is to make event planning easier for everyone. We can handle any kind of
event, be it a dream wedding, a birthday party, a boys’ game night at home, a slumber
party with your girls, a family movie night within the comfort of your home or anything
else. First of all, we offer an intuitive platform and website that anyone can use to create
their perfect event, even those without prior experience in event planning. Second, we
are incredibly inclusive and welcome any event with open arms. We help plan a variety
of events, from small parties to large events, making sure everyone is planned with the
same care.
If you have any financial limitations it is not a problem. You set the spending limit, and
we thoughtfully create custom designs that precisely fit within it. Furthermore,
Accessibility is also crucial. You can access our website with ease from any computer
or smartphone, no matter where you are or when you want. Most importantly, we
appreciate your opinions. Your feedback is important to us because it motivates us to
continuously improve and update our website, giving users an ever-better experience.
However, we will provide you with multiple options within your range. For example,
if you choose us for your birthday party event we will provide you with different menus,
different decoration options from number of vendors which will be within your
provided range and you can easily choose from the provided options this is how you
can customize your birthday or any event package according to your affordability and
satisfaction. And for instance if you want to plan a game night we will provide you with
different packages of games (e.g. chess, cards, carom board, PlayStation etc.) which
will also include catering and decor according to your need. You can also add on extra
games in the provided game packages. However, we also implemented AI algorithms
in our projects such as image recognition which will analyze images which user
provided and show or recommend them venues that are matching with that ambiance.
Furthermore, many more AI algorithms are used like, AI recommendation etc.

1.2 Project Scope:

 Key Features:
 Event Creation: Users can plan events, specifying details like date,
time, and budget.
 Customization: Users can tailor event packages by selecting services.
 Reviews and Ratings: Users can provide feedback to help others.
 Customer Support: Responsive help for user inquiries.
 Marketing and Monetization: Strategies to attract users and vendors.
 Login: User, admin, and vendor can login.

1
 CHAPTER 1: INTRODUCTION


Budget Friendly: Vendors will be chosen according to customer’s
budget.
 Event: All types of events can be managed (birthday, gaming night,
wedding etc.).
 Services: All services (catering, decoration etc.)
 Admin: Manage communication with vendors and users and will
manage data (view, modify, delete etc.).
 Ecommerce Platform.
 Database Management System: History of past events and records of
events.
 Use of AI tools and technology: AI Recommendation,
 Project Scope Exclusions:
 No Event Execution.
 No Legal Services
 No Event Insurance
 No Venue Ownership
 No Transportation Services
 No Event Photography/Videography
 No Event Licensing
 No Event Security Services
 No Event Entertainment
 No Physical Goods Sales
 No Event Planning Certification
 No Travel Planning
 No Event Cleaning Services
 No Ticketing Services

1.3 Intended Audience:

 Stake Holders:
 Project team members
 IT Manager:
 Project supervisor
 End Users:
 Individual event planners
 Couples and families
 Event planning professionals
 Educational Institutes
 Small businesses
 Community groups (for charity fundraising events)
 Event Attendee

1.4 Existing system:

In the existing event management system, individuals who require assistance must go
to an office. They can communicate about their issues, but they are unable to access
many other useful services or view all the details. This system is difficult to use and
isn't very popular. However, there are websites similar to ours that assist with online
event management all over the world. These websites are more widely used because
they offer more functionality and are simpler to use. We wish to implement a

2
 CHAPTER 1: INTRODUCTION

significant change to our event management website project. Our website will operate
differently than it did in the past. Because everything will be done online, you won't
need to visit an office. You can describe your event to us.[11]

Table 1: Benchmarking.

BENCHMARKING
Websites Customization Vendor Pricing Filter AI
In Order Selection (By (Dynamic Alogrithm
Choice Of Pricing)
Customer)
Wonder
Events
✘ ✘ ✘ ✘
Dawat. pk
✘ ✘ ✔ ✘
Elleaevents
✘ ✘ ✘ ✘
Proposed
Website
✔ ✔ ✔ ✔

1.5 Problem definition:

 Rivalry: Numerous sites offer comparable administrations, making it hard to
stick out.
 Client Trust: Acquiring trust from clients, particularly new ones, is extreme.
Individuals could stress over sharing individual and monetary data.
 Merchant Dependability: Ensuring sellers are reliable is a test. Keeping a
rundown of good sellers and it means quite a bit to really look at their work.
 Complex Customization: Offering loads of decisions can confound clients,
particularly on the off chance that they're not experienced occasion organizers.
 Exact Spending plans: It's hard to make occasion designs that match the
financial plan completely because of differing merchant costs and client
assumptions.
 Taking care of Criticism: Managing client ideas and grumblings needs work
to keep clients cheerful.
 Ordinary Updates: The site needs normal updates to remain secure, without
bug, and effective.
 Developing Difficulties: Resolving these issues will help our occasion
arranging site stay effective over the long haul.
 Consistent Improvement and Transformation: AI systems need to be
constantly updated, monitored, and adapted to new conditions or data patterns.
It is essential to Lay out systems for continuous improvement.

1.5.1 Problem’s Solution:

 Standing Out: Make website unique by offering special features, a wide range
of vendors, or excellent customer service that others don't have.
 Building Trust: Be clear about how to protect user data. Let users read reviews
from others to build trust.
 Vendor Reliability: Check vendors thoroughly with background checks,
references, and licenses.

3
 CHAPTER 1: INTRODUCTION

 Making Customization Easy: Guide users step-by-step if they're not

experienced. Provide good customer support for complex needs.
 Budget Accuracy: Keep vendor prices updated and make sure they're accurate.
 Fair Pricing: Be clear about how to make money and how users benefit.
 Handling Feedback: Have a dedicated team to handle user feedback.
 Regular Maintenance: Keep the website secure and bug-free with regular
updates.

1.6 Market Possibility:

 Serious Investigation: We will examine current event planning platforms and
websites to identify their advantages, disadvantages, and positioning in the
market. We will also recognize the competitive landscape and how our website
can stand out.
 Customer feedback: We will compile customer feedback via summaries,
conferences, or center events to validate the demand for our website. Recognize
our clients' needs and how they perceive our proposal during the event planning
phase.
 Inquiry:
 Differentiating Hazards: We will acknowledge the risks and challenges
that are likely to arise and have the potential to impact the success of the
task, such as security risks, or client behavior changes.

4
 CHAPTER 1: INTRODUCTION

1.7 Block Diagram:

Figure 1 : Block Diagram

5
 CHAPTER 2: LITERATURE REVIEW

CHAPTER 2
LITERATURE REVIEW

2.1 Literature review:

This chapter explains the literature we have studied in developing our system and this
document is written for the students, researchers, and software developers. The Event
management systems that have been developed in the past have been narrowly focused
and have only addressed certain areas of event preparation. One of the ways that our
website stands out is that it provides a whole solution to improve the general
effectiveness of event planning and management.
There is a website named "Event Management System" that centers on using several
software technologies to plan, organize, and supervise events. It consists of modules
for handling client and staff data, events, services, e-card generation, and a website
where clients may monitor the status of events. Databases for employee and client
information as well as information about events are included in the project, which is
being implemented with Microsoft Visual Studio as the front end and Microsoft SQL
Server as the back end. [1]
The system named ‘Event management system with SMS alerts’ notifies staff members
of important announcements and events. Compared to traditional approaches, the
solution, which is deployed using Microsoft's Visual Studio and SQL Server, improves
efficiency, saves time, and guarantees the security of documents. Without relying on
the Internet, the SMS notification feature promotes efficient communication between
managers and their staff within the organization.[2]
The Loyolas Wedding Hall understands the need to update its processes for the benefit
of customers. The platform, which has converted to an online wedding hall
management system, offers a variety of package options and simplifies the booking
process for both the venue and extra services like makeup artists, filmmakers, and
videographers. The technology is available whenever needed and guarantees that
customers may manage their preferences and bookings at any moment, delivering
prompt and effective services. The solution, which was created with the PHP language,
WAMP server, and MySQL database, ensures excellent flexibility and has passed
extensive reliability testing utilizing sample data and a range of user situations.
Simplifying and improving the modern-day wedding experience for clients is the aim.[3]
"Wedding Organizer " the online portal for wedding preparation functions as a one-
stop shop, providing information on the various goods and services that are offered. A
useful checklist that outlines work for the big day, allows you to take notes and check
your progress is included in the system. The approach helps couples manage expenses
and make decisions.[4]
A web application titled the ‘Event Management Solution’ was developed to make it
simple for users to manage announcements, events, and website content. Events and
announcements can be added, deleted, updated, and viewed by users, including the
Administrator and System Manager. End users have access to created events, posted
announcements, and an electronic form for registering for events that are available. An
easy-to-use platform for effectively organizing and registering for events is offered by
Event Management Solutions Website.[5]
A web app called ‘Digital Wedlock Help’ is meant to help with wedding reservations
for things like location, catering, clothing, jewelry, and decorations for the stage. After
completing an enrollment form, clients register, and the administrator activates them.

6
 CHAPTER 2: LITERATURE REVIEW

Organizers can reply to requests from clients and be added by the administrator. For all
parties involved, this tool simplifies the wedding preparation process.[6]
An online software project called the ‘Online Event Management System’ functions as
an event manager. When registering for an event, users select the equipment, date, time,
and venue. In addition to examining reviews and costs, they can book locations, caterers,
decorators, and DJs. Users get a reservation receipt, and information is saved. The
technology improves advertising, improves registration, and streamlines event
organizing.[7]
The virtual (Your Dream) wedding planner is a useful tool for people who are
organizing weddings. Users enter the date of their wedding and indicate if they require
a full-time, weekend, or weekday planner. The system notifies users automatically via
SMS when tasks are due on the date specified after they enter their details. Details about
guests and vendors, including roles, are effectively managed by the system. It may use
keywords to do an intelligent web search for vendor details. Good service delivery is
ensured by the system's ability to accommodate users who are fluent in any of the
languages spoken in Sri Lanka.[8]
"My Wedima" web application for wedding planning provides couples with a
convenient way to gather information about various bridal items and services in one
place. Customers can use the site to sign up, look up package costs, and make online
product reservations with sellers. Through an event calendar, vendors may manage
bookings, advertise, and build profiles. The application is designed with PHP,
Bootstrap, and MySQL and follows the Agile technique, which guarantees client
involvement. This online wedding planning company offers to make the wedding
planning process easier for time-pressed couples.[9]
The ‘Online Wedding Organizer’ help families and brides arrange and carry out
wedding ceremonies within specified expenses and timetables. However, limited
information, ordering issues, and the time-consuming nature of visiting WO locations
make it difficult for would-be brides to get information about wedding organizers (WO).
To solve this, WOs are now given a platform to advertise their services to couples at
any time. website built with PHP and MySQL. With consideration for elements such as
invitations, budget, food, venues, and decorations, the project attempts to develop a
web-based WO information system that will make it simple for aspiring women to
locate wedding themes that suit their tastes. Additionally, WOs can use it as a
promotional tool to interact with customers and carry out commercial operations related
to wedding organizers by conducting electronic transactions.[10]

7
 CHAPTER 3: METHODOLOGY

CHAPTER 3
METHODOLOGY

3.1 Introduction:
Creating and managing an EventBliss Website requires a comprehensive approach that
involves multiple elements to ensure effective organization and management of events.
The communication starts with a serious assessment of essentials, considering the
outstanding necessities and focuses of the site, going from event creation to part the
leaders. Portraying essential features and functionalities, such as straightforward
selection structures, secure portion blends, and responsive arrangement, is huge. The
client experience (UX) plan stage is based on making a characteristic association point,
maintained via cautious back-end and front-end headway to ensure ideal execution and
accessibility across contraptions. Solid event data on the board and secure client
confirmation further work on the stage's convenience. Comprehensive testing,
including client affirmation testing and security assessments, goes before the site's
farewell. Post-sending, advancing upkeep and updates are central for keeping the stage
agreed with creating mechanical examples and client presumptions. This iterative
philosophy, put aside by facilitated exertion between specialists, organizers, and
accomplices, ensures the EventBliss Site is a dynamic and strong gadget for regulating
various events.

3.2 Research Design:

While making an EventBliss Site, we start by setting clear goals for the stage and
figuring out what we need to accomplish. We research existing writing and examine
other occasion the executives sites to comprehend what functions admirably and what
challenges we might confront. Gives significant experiences into their inclinations and
assumptions. Dissecting contenders assists us with situating our site really and gain
from industry rehearses. Moreover, we survey accessible innovations, guaranteeing we
pick a stack that lines up with our undertaking objectives and conforms to legitimate
prerequisites. Making point-by-point client personas assists us with picturing our
optimal interest group, directing plan choices. The examination configuration gives
major areas of strength for the resulting periods of plan and improvement, guaranteeing
the site is custom-made to the particular necessities of occasion organizers and
participants.

3.3 Data Analysis:

While fostering an EventBliss Site, information investigation is a pivotal step that
includes separating significant bits of knowledge from the information accumulated all
throughout the venture. At first, we gathered significant information from different
sources, including client associations, enrollment subtleties, and stakeholder criticism.
The gathered information goes through exhaustive cleaning and planning to guarantee
exactness and consistency. Client division helps tailor the site to various client
gatherings, upgrading the general client experience. In further developed situations, the
prescient examination might be utilized to expect future patterns. The discoveries from
the information examination illuminate the heading, directing continuous upgrades to
meet client assumptions. A complete report recording key bits of knowledge fills in as
a significant reference for the future turn of events and guarantees the EventBliss Site
stays receptive to client needs.

8
 CHAPTER 3: METHODOLOGY

3.4 System Development Methodology:

The Framework Improvement Philosophy for an EventBliss Site follows an organized
way to deal with make a proficient and easy to use stage. It begins with exhaustive
preparation, characterizing project degree, goals, and necessities while likewise
thinking about attainability concerning specialized, monetary, functional, and lawful
viewpoints. The ensuing framework configuration stage shapes the engineering, data
set design, and UI, giving an outline to improvement. Prototyping permits partners to
envision and refine the plan almost immediately. The improvement stage includes
coding backend and frontend parts, trailed by testing to distinguish and address any
blunders. Organization brings the site into a live climate, and preparing and
documentation guarantee clients and directors are prepared to utilize and keep up
with the framework. Progressing upkeep and backing, including standard updates and
brief issue goal, are critical for supported execution. Assessment and persistent
improvement include checking webpage, gathering client input, and executing
upgrades to guarantee the EventBliss Site stays successful and receptive to client
needs. This approach involves a cooperative and iterative interaction that expects to
convey a dependable and versatile stage for occasion coordinators and members. [12]

3.5 System Requirements:

While making an occasion the board site, characterizing the framework prerequisites is
a critical step that covers different viewpoints fundamental for the outcome of the stage.
Comprehending the needs of the client entails learning bits and pieces about the
expectations and needs of event planners, attendees, and leaders in order to ensure that
the website caters to their preferences and provides the best possible customer
experience.

3.6 Functional Requirements:

Table 2: Functional Requirements

FR# Description

User Will Be Able To View Event Details Without Logging in

FR01
(Guest Mode).

FR02 Users Will Be Able To Select From Available Packages.

Users Will Also Be Able To Select Budget Friendly Packages If

FR03
They Want(customization).

FR04 Mode Of Payment.

FR05 Confirm Event By Booking.

FR06 User Authentication(Login/Signup).

9
 CHAPTER 3: METHODOLOGY

Users will be able to take help from AI algorithms such as,

FR07
dynamic budget, and recommendations

FR08 Fill Details Form.

FR09 Booking Management(Cancel, modify.)

FR10 User History Of Bookings..

FR12 Customer Support (Chatbot Ai)

FR13 Vendors will be able to register.

Vendors shall be able to create a profile where they should list

FR14
their services.

Vendors will be able to confirm bookings according to their

FR15 availability and should manage the calendar (manage
availability for different dates and times).

Vendors will receive notifications (new inquiries, booking

FR16
requests).

FR17 Vendors will be able to manage payments.

FR18 Vendors will also be able to receive user feedback.

Admin will be able to manage users and permissions (admin,

FR19 event planner, vendor) and define their access levels and will
also manage users authentication.

FR20 Admin shall be able to view the dashboard.

FR21 Admin will manage data (view, modify, delete).

FR22 Admin will be able to approve, reject, or edit events.

10
 CHAPTER 3: METHODOLOGY

Admin will be able to view and approve new vendor

FR23 registrations.

FR24 Admin will monitor vendors (performance, reviews).

FR25 Admin will monitor communication between users and vendors.

FR26 Admin will manage and monitor customer support.

3.7 Nonfunctional requirement:

 Speed and Reliability:
 Reaction Time: The stage will actually want to answer immediately to
client's activities, like clicking any button or stacking any page, immediately
longer than a couple of moments to ensure client experience is proficient
and smooth.
 Performance Reliability: The system should scale perfectly to manage a
rising number of simultaneous clients during active times, for instance,
when ticket bargains open for renowned events.
 Safety and Security:
 Access Controls: Use versatile access controls to confine client access
according to occupations and assents, ensuring that principal people with
the proper endorsement can get to explicit components or secret information.
 Easy to Use:
 Steady Client Interface: Keep a dependable and simple to-use UI (UI) on
each page to increase straightforwardness and decrease the prerequisite for
clients to get new capacities and change as they investigate different district
of the site.
 Handles a Ton of Users:
 Planning for Multiple uses: Construct the site's engineering to oblige a
huge expansion in simultaneous clients, particularly during top interest
conditions such as occasion enlistments, to anticipate changes.
 Execution Improvement: Perform server-side upgrades and convincing
data base inquiries as a part of execution movement cycles to ensure most
prominent capability even with significant client loads.
 Works on Various Devices:
 Cross-Program Compatibility: Affirm and test that the website works
dependably with various web programs, including notable decisions like
Chrome, Firefox, Safari, and Edge
 Gadget Responsiveness: Plan the site as per responsive arrangement
guidelines so it can adjust to different screen sizes and gadgets, offering
the most ideal audit and joint effort experience on cell phones, tablets, and
workstations.

11
 CHAPTER 3: METHODOLOGY

 Easy to Update:
 Code Maintainability: Make that your codebase keeps coding
guidelines and is proficient and solid. This further develops code
feasibility, which makes it more straightforward for originators to
comprehend, change, and upgrade the code over the long haul.
 Measured Architecture: Choose a specific design that takes into
account the addition of additional components and features without
changing the overall structure. To adapt to changing needs, this isolated
approach is updated and improved over time.
 Stays Alert Generally of the Time:
 Excellent Availability: Aim high by implementing feedback activities
and regular frameworks to restrict unplanned margin periods.
Continually monitor and resolve any problems that can affect the
accessibility of the website.

12
 CHAPTER 3: METHODOLOGY

3.8 USE CASE Diagram:

Figure 2: Use-Case Diagram.

13
 CHAPTER 3: METHODOLOGY

Figure 3: User Use-Case Diagram.

UC01:
Table 3: User Use-Case
Use-Case Name: Book Event.
Primary Actor: Registered User.
Actor Action: The user goes to the event section,
chooses the event they want to attend,
fills in the event details, and validates
their reservation.
Pre-Condition: The user needs to have access to the
Event Handler platform and be logged in.
System Response: The system updates the user's event plan
with the selected vendors, validates the
reservations, and processes the event
selection. It also gives confirmation
information and may start a conversation
between the admin and user to make
additional arrangements.

UC02:

14
 CHAPTER 3: METHODOLOGY

Table 4: Registration Use-Case.

Use-Case Name: Registration.
Primary Actor: Customer
Actor Action:  The customer accesses the
(Basic Flow) registration page.
 The customer provides the
required information such as
username, and password.
 The customer submits the
registration form.
 If the information is valid, the
system creates a new user
account.
Pre-Condition: The user needs to have access to the
platform.
System Response: The user has successfully registered in the
system.

UC03:
Table 5: Confirm Payment Use-Case.
Use-Case Name: Confirm Payment
Primary Actor: Customer
Actor Action:  The customer surveys the
(Basic Flow) installment subtleties, guarantees
everything is right, and affirms
the installment.
 They confirm the installment sum,
strategy, and different subtleties
to guarantee exactness.
 In the case of everything is right,
they make a move to affirm the
installment, which sets off the
installment handling and finishes
the exchange.
Pre-Condition:  The customer has effectively
finished the checkout cycle.
 The customer has entered
legitimate installment data.
 The customer has an adequate
equilibrium or credit breaking
point to finish the installment.
System Response: The system refreshes the request status to
"paid" or "finished"..

UC04:

15
 CHAPTER 3: METHODOLOGY

Table 6: Manage Booking Use-Case.

Use-Case Name: Manage Booking
Primary Actor: Customer

Actor Action:  The customer sees and deals with

(Basic Flow) their booking subtleties, including
booking status.
Pre-Condition:  The customer is logged in to their
account or has provided valid
authentication credentials.
 The customer has made a booking
in the past or has an upcoming
booking.
 The customer has a valid booking
reference number or account login
credentials.
System Response:  The system verifies the customer's
authentication credentials and
ensures they have the necessary
permissions to access and modify
their booking.
 The system updates the customer's
account and booking history to
reflect any changes or
cancellations.

UC05:
Table 7: Customer Support Use-Case.
Use-Case Name: Contact Customer Support
Primary Actor: Customer
Actor Action:  The customer initiates contact
(Basic Flow) with customer support to request
assistance, resolve an issue, or ask
a question.
Pre-Condition:  The customer has a valid booking
reference number or account login
credentials
 The customer is contacting
customer support through an
approved channel (e.g. phone,
email, chat, social media).
System Response: The system provides access to customer
support channels.

16
 CHAPTER 3: METHODOLOGY

Figure 4: Vendor Use-Case Diagram.

UC06:
Table 8: Vendor Registration Use-Case.
Use-Case Name: Registration
Primary Actor: Vendor
Actor Action:  The vendor accesses the
(Basic Flow) registration page.
 The vendor provides the required
information such as username,
and password.
 The vendor submits the
registration form.
 If the information is valid, the
system creates a new vendor
account.
Pre-Condition:  The vendor needs to have access
to the Event Handler platform and
be logged in.
System Response: The vendor has successfully registered in
the system.

17
 CHAPTER 3: METHODOLOGY

UC07:
Table 9: List Services Use-Case.
Use-Case Name: List Services
Primary Actor: Vendor
Actor Action:  View Services
(Basic Flow)  This represents the action taken
by the vendors to achieve goal.
Pre-Condition:  The vendor has a valid account
with the system.
 The vendor has successfully
logged in to the system.
 The vendor has the necessary
permission and access rights to
view the services list
System Response: Display a list of services, including
service name, description, and pricing.

UC08:
Table 10: Display Portfolio Use-Case.
Use-Case Name: Display Portfolio
Primary Actor: Vendor
Actor Action: Showcase Product/Services
(Basic Flow)
Pre-Condition:  Vendor has valid account with the
system.
 Vendor has uploaded their
portfolio content.
 System has verified the vendor’s
identity and credentials.
System Response:  Display the vendor’s portfolio.
 Showcase Product/Services

UC09:
Table 11: Confirm Booking Use-Case.
Use-Case Name: Confirm Booking
Primary Actor: Vendor
Actor Action:
(Basic Flow)
Pre-Condition:  Vendor has valid account with the
system.
 Vendor has uploaded their
portfolio content.

18
 CHAPTER 3: METHODOLOGY

 System has verified the vendor’s

identity and credentials.
System Response:  Display the vendor’s portfolio.
 Showcase Product/Services

UC010:
Table 12: Manage Payments Use-Case.
Use-Case Name: Manage Payments
Primary Actor: Vendor
Actor Action:  Processing Transaction
(Basic Flow)  Handling Refunds
 Maintaining Payment Records
Pre-Condition:  Vendor has a valid account with
the payment processing system.
 Customer has made a payment or
requested a refund.
 The payment processing system is
operational and functioning
correctly.
System Response:  Display payment dashboard
 Automate payment processing
 Ensure secure and compliant
payment processing, adhering to
industry standards.

UC011:
Table 13: Feedback Use-Case.
Use-Case Name: Receive user feedback
Primary Actor: Vendor
Actor Action:  Collect and review customer
(Basic Flow) feedback.
 Reading and analyzing customer
reviews and ratings
 Using feedback to inform product
and service improvements.

Pre-Condition:  Vendor has a feedback collection
system in place (e.g. Feedback
box)
 Customers have used the vendor’s
products or services and have
experience to share.

19
 CHAPTER 3: METHODOLOGY

 Customer feedback is accessible,

readable, and understandable by
the vendor.
System Response:  Display customer feedback in a
centralized dashboard.
 Integrate feedback data with
other systems(e.g. Product
development, customer support.)

Figure 5: Admin Use-Case Diagram.

20
 CHAPTER 3: METHODOLOGY

UC012:
Table 14: Admin Use-Case.
Use-Case Name: User Accounts and Vendor accounts
Management.
Secondary Actor: Admin.
Actor Action: Enters the admin dashboard, checks user
and vendor accounts, modifies
permissions, takes care of account-
related concerns, and updates details..
Pre-Condition: The admin's access to the Event Handler
admin panel must be authorized.
System Response: The system presents an all-inclusive
perspective of user and vendor accounts,
enabling the administrator to adjust user
and vendor rights, update user and vendor
information (if necessary), and
effectively handle any account-related
problems.

UC013:
Table 15: Manage Dashboard Use-Case.
Use-Case Name: Manage dashboard and permissions.
Secondary Actor: Admin.
Actor Action: Enters the admin dashboard, checks user
and vendor accounts, modifies
permissions, takes care of account-related
concerns, and updates details..
Pre-Condition:  The Admin must be logged into
the admin panel of the event
website.
 The event website must have a
functional user management and
permissions module.
 The Admin should have the
necessary permissions to manage
users and their permissions.
System Response:  Users have the appropriate
permissions assigned or updated.
 The system logs the changes made
by the Admin.

21
 CHAPTER 3: METHODOLOGY

UC014:
Table 16: View and Modify Use-Case.
Use-Case Name: Admin Views and Confirms Changes
Secondary Actor: Admin.
Actor Action: Admin reviews the updated permissions
and roles to ensure they are correct.
Pre-Condition:  The Admin must be logged into
the admin panel of the event
website.
 The event website must have a
functional user management and
permissions module.
 The Admin should have the
necessary permissions to manage
users and their permissions.
System Response:  The system displays the updated
permissions and roles for the
selected user.

UC015:
Table 17: Monitoring Vendors Use-Case.
Use-Case Name: Admin Monitoring Vendors
Secondary Actor: Admin.
Actor Action: Admin reviews the updated permissions
and roles to ensure they are correct.
Pre-Condition:  The Admin is logged into the
event website with appropriate
privileges.
 Vendors are registered and have
active profiles on the event
website.
 The event website has a functional
monitoring system for tracking
vendor activities.
System Response:  The system authenticates the
Admin and grants access to the
Admin dashboard. The dashboard
displays an overview of vendor
activities, notifications, and alerts.

22
 CHAPTER 3: METHODOLOGY

UC016:
Table 18: Monitoring Customer Support Use-Case.
Use-Case Name: Admin Monitoring Customer Support.
Secondary Actor:  Administrator (Admin)
 Customer Support Agent (Agent)
 Customer (User)
Actor Action: The admin navigates to the customer
support section within the admin panel.
Pre-Condition:  The admin is logged into the
admin panel of the event website.
 The customer support system is
integrated into the event website.
 There are active customer support
or live chat sessions.
System Response:  The system continuously updates
the conversation view in real-
time, reflecting any new messages
sent by either the agent or the
customer..

23
 CHAPTER 3: METHODOLOGY

3.9 Sequence diagram:

Figure 6: Sequence Diagram.

24
 CHAPTER 3: METHODOLOGY

3.10 Class diagram:

Figure 7: Class Diagram.

25
 CHAPTER 3: METHODOLOGY

3.11 ERD Diagram:

Figure 8: ERD.

26
 CHAPTER 5: CONCLUSION

CHAPTER 4
DESIGN and IMPLEMENTATION

4.1 Design of Our Project:

 Visually Appealing Design: We will develop a design for the website that is
visually appealing and easy to use.
 Intuitive and responsive design: We will create a responsive, aesthetically
pleasing design that works well on a variety of devices, including desktops,
tablets, and smartphones. Make sure the interface is user-friendly and provides
simple navigation through the various stages of event planning, vendor
interactions, and problem-solving.
 Personalized Dashboards: Give event coordinators and suppliers customized
dashboards that show pertinent data, forthcoming events, assignments, and
alerts based on their roles and preferences.
 Aesthetic Elements and Themes: Provide event planners with a variety of
aesthetic themes or templates that cover different styles (modern, vintage,
minimalistic) to suit a range of event types and preferences.
 Prototyping and Testing: Before launching the platform, conduct
comprehensive phases of user testing and prototyping to ensure usability, gather
feedback, and refine the design. Address any issues with the user experience.
 User-Centric Design Iterations: Use behavior analysis and user feedback to
guide iterative design processes that continuously improve the interface to
increase user engagement and satisfaction.
 Secure login: Put in place a secure login system where users (vendors, event
planners) can create accounts and ensure that data is secure.
 Multi-channel integration: Provide website forms, direct messaging, or phone
contact for event planners to submit requirements or issues for diverse
accessibility.
 Centralized database: A centralized database should be created to store all the
user and vendors’ data and event specifics.
 Automated workflows: Put automated workflows into place to direct questions
to the appropriate vendors for rapid response. This will streamline the handling
of queries.
 Real-time notifications: Give users up-to-date information on how their event
planning is going, such as confirmations of booking, etc.
 Analytics and reporting: The system should provide analytic s and reporting
capabilities, allowing administrators to track event trends, service usage, user
preferences, and pinpoint areas that require improvement by integrating
analytics and reporting features.
 AI Algorithms: Use of different AI algorithms for user ease and fulfillment of
user requirements in a user-friendly and understandable manner.

4.2 Implementation requirement:

 Platform Selection: Selecting a flexible online platform that enables users
(vendors, event planners) to quickly report issues associated with events, and
administrators to effectively track and address these issues.
 User-friendly interface: Provide an easy-to-navigate interface that makes it
possible for vendors and event planners to quickly identify and resolve
problems.

26
 CHAPTER 5: CONCLUSION

 Variety of Event Categories: To make event planning and problem solving

easier, include a variety of event categories (such as weddings, parties, and
corporate gatherings).
 Capabilities for communication: Include tools for messaging or user support
to enable smooth communication between.
 Privacy and Confidentiality: Make sure that strict privacy protocols are in
place to protect data related to events and to preserve the privacy of vendors,
event planners, and sensitive event information.
 Customization Choices: Assist clients with making modified occasion plans
by telling their spending plan as indicated by their moderateness and afterward
we will give them custom fitted bundles which suits them and match their
prerequisites.
 Criticism and Survey Framework: Lay out an input framework so that,
following the occasion, occasion organizers can rank and remark on providers
or administrations to help with future preparation.
 AI Algorithms: AI Recommendation, Dynamic Budgeting Algorithms.

4.3 Tools and Technologies:

 Frontend Languages:
 ReactJS (Library): JavaScript library for building UI. If data changes
it can render and update effectively. ReactJS has high performance,
reusability and maintainability of code and it is SEO friendly.
 Tailwind CSS: It is Utility-first (utility classes like colors, margin
padding, and layout.CSS framework and it builds custom user interfaces
rapidly. It is also highly customizable, Responsive design. It has rapid
speed of development, easier to maintain, Consistent design. It is used
in creating single page applications, visually appealing landing pages,
custom designs.
 Redux Toolkit (State Management): Includes several libraries and
utilities that are commonly used together to manage application state
effectively. It reduces boilerplate (repeated code), simply async
operation such as fetching data from an API and enable efficient
querying and updating of normalized data.
 Backend Languages:
 NodeJS (runtime engine): open-source, cross-platform environment.
Light weight and efficient. It has high performance (non-blocking I/O
model) and provides real time communication. It is used in web servers,
APIs etc.
 ExpressJS (Framework): minimalistic web app framework for
NodeJS. Provides strong set of features for building web app, APIs. It is
known for its extensibility, flexibility and simplicity. Key features
include Middleware (logging, authentication, request handling, error
handling. It prioritizes performance and simplicity suitable for building
lightweight apps.
 Database Management:
 MongoDB: Open-source, NoSQL(non-relational) database
management system. It uses document-oriented data model. It stores
data in document format which is flexible instead of using rows and
tables. It is suitable for handling unstructured data. It is document-
oriented, schema-less design which include dynamic and flexible

27
 CHAPTER 5: CONCLUSION

schemas where we can update or change fields without affecting other

documents, it is powerful and expressive query language. It is used in
CMS, e-commerce platforms etc.
 MongoDB Compass (tool): Official graphical user interface (GUI),
provides admin and developer with a visual way to interact with
databases. Offers features such as visual schema exploration, query
building, document editing, and real-time performance monitoring,
making it easier to navigate and manipulate MongoDB data
 Tools:
 VsCode (Code Editor): lightweight and highly customizable source
code editor. It supports wide range of programming languages and
extensions and supports features such as debugging.
 Postman (API Testing): Used for testing, documenting and debugging
APIs and provides user-friendly interface for making HTTP requests,
organizing APIs.
 AI Algorithms:
 Tawk.to (Chabot for Customer Support): Live chat software that
let website owners to communicate to their visitors in real-time. Chat
widget is provided that can be easily integrated into websites, allowing
visitors to communicate with the website owners or support team. It
provides live chat, customization of widget, visitor monitoring and it is
multilingual which means it supports many languages.
 Google Gemini for AI Integration: Google provides many AI-related
services and tools that could possibly be integrated into event websites
for different purposes. It can be integrated using API.
 Payment Gateway:
 Stripe: Allows businesses to accept payments online. Provide set of
APIs and tools that enable developers to integrate payment processing
functionality. Stripe is secure, provides customizable checkout,
prevents fraud. It uses payment API, Checkout API, Billing API etc.
 different purposes. It can be integrated using API.
 Dynamic Search:
 Stripe: Allows businesses to accept payments online. Provide set of
APIs and tools that enable developers to integrate payment processing
functionality. Stripe is secure, provides customizable checkout,
prevents fraud. It uses payment API, Checkout API, Billing API etc.

4.4 Website Interface:

4.5 Testing Used in This Project:

 Functional Testing:
 Goal: Assesses the system's capabilities in relation to specified
requirements.
 Unit testing: verifies that separate parts (such as modules or functions)
perform as intended.

28
 CHAPTER 5: CONCLUSION

 Integration testing: Examines how integrated components interact with

one another to see if they work as a unit.
 System testing: Assesses all of the system's features to make sure it
satisfies requirements.

 User Acceptance Testing (UAT):

 Goal: Verifies that the system is ready from the perspective of the end
users.
 Alpha testing: Internal testing carried out by a small team to find
problems prior to release.
 Beta testing: A small number of outside users participate in beta testing
in order to evaluate usability in real-world scenarios and gather
feedback.
 Performance testing:
 Goal: Verify that the system operates effectively in a variety of
scenarios.
 Load testing: In order to avoid crashes or slowdowns during periods
of high usage, load testing measures the system's performance under
anticipated load levels.
 Stress testing: Determines breaking points in a system by straining it
beyond its typical operating capacity.
 Scalability testing: determines whether the system can accommodate
growing loads without degrading performance.
 Security Testing:
 Goal: Verifies data protection and finds vulnerabilities.
 Vulnerability assessment: Finds gaps in the security measures of the
system.
 Penetration testing: Evaluates the system's durability to actual threats
by simulating cyberattacks.
 Regression Testing:
 Goal: Confirms that recent modifications haven't negatively impacted
currently available functionalities.
 Automated Regression Testing: Retests features that have been
impacted by recent updates using automated scripts.
 Compatibility testing:
 Goal: Verifies that the platform works with various operating systems,
browsers, and devices.
 Testing Across Browsers: guarantees that the platform functions
consistently in a variety of web browsers.
 Testing for device compatibility: confirms functionality across
various devices (desktops, tablets, mobiles).

4.5.1 Testing Importance in Event Management Platforms:

 Functionality and Reliability: Provides smooth vendor relations, event
planning, and complaint handling.
 Satisfaction of Users: Ensures a user-friendly interface, which increases user
satisfaction and usage.

29
 CHAPTER 5: CONCLUSION

 Data security: Guards private information and sensitive event-related data.

 Performance and Scalability: Makes sure the system runs smoothly and has
the capacity to manage different event loads.
 Compliance and Reliability: Enhances credibility by adhering to legal
requirements and industry standards.

4.5.2 Test Cases:

Test Case Customer Registration

Test Case: Verification that a new customer can register successfully on
the website with valid details.
Testing Type: Functional Testing.
Test Data:  Name: Testing
 Email: [email protected]
 Password: Password123
 Confirm Password: Password123
Predicted Outcome: The customer should be able to register successfully.
Steps: Steps to carry out the test. See step formatting rules below.

1. Navigate to the registration page of the website.

2. Enter "Testing" in the "Name" field.
3. Enter "[email protected]" in the "Email" field.
4. Enter "Password123!" in the "Password" field.
5. Enter "Password123!" in the "Confirm Password"
field.
6. Choose image.
7.
8. Click on the "Register" button.
9. Observe the outcome.

Status: Pass

Table 4.1: TC 01.

Test Case User Login

Test Case: Verify that a registered user can log in successfully with valid
credentials.
Testing Type: Functional Testing.
Test Data:  Email: [email protected]
 Password: ValidPassword123!
Predicted Outcome: The user should be able to log in successfully and be
redirected to the home page.
Steps: Steps to carry out the test. See step formatting rules below.

1. Navigate to the login page of the website.

30
 CHAPTER 5: CONCLUSION

2. Enter "[email protected]" in the "Email" field.

3. Enter "ValidPassword123!" in the "Password" field.
4. Click on the "Login" button.
5. Observe the outcome.

Status: Pass
Table 4.2: TC 02.

Test Case User Login Fails Due to Incorrect Password.

Test Case: Verify that login fails with an incorrect password.
Testing Type: Negative Testing.
Test Data:  Email: [email protected]
 Password: IncorrectPassword!!
Predicted Outcome: The system display an error message indicating that the
password is incorrect.
Steps: Steps to carry out the test. See step formatting rules below.

1. Navigate to the login page of the website.

2. Enter "[email protected]" in the "Email" field.
3. Enter "IncorrectPassword!" in the "Password" field.
4. Click on the "Login" button.
5. Observe the outcome.

Status: Pass/Fail.

Table 4.3: TC 03.

Test Case User Login Fails Due to Incorrect Email.

Test Case: Verify that login fails with an unregistered email address.
Testing Type: Negative Testing.
Test Data:  Email: [email protected]
 Password: AnyPassword123!
Predicted Outcome: The system display an error message indicating that the email
address is not registered.
Steps: Steps to carry out the test. See step formatting rules below.

1. Navigate to the login page of the website.

2. Enter "[email protected]" in the
"Email" field.
3. Enter "AnyPassword123!" in the "Password" field.
4. Click on the "Login" button.

31
 CHAPTER 5: CONCLUSION

5. Observe the outcome.

Status: Pass/Fail.

Table 4.4: TC 04

Test Case User Login Fails Due to empty fields.

Test Case: Verify that login fails if mandatory fields are left empty.
Testing Type: Negative Testing.
Test Data: Leave "Email" and "Password" fields empty.
Predicted Outcome: The system display error messages indicating that the
mandatory fields cannot be left empty
Steps: Steps to carry out the test. See step formatting rules below.

1. Navigate to the login page of the website.

2. Leave the "Email" field empty.
3. Leave the "Password" field empty.
4. Click on the "Login" button.
5. Observe the outcome.

Status: Pass/Fail.
Table 4.5: TC 05

Test Case User Logout.

Test Case: Verify that a user can log out successfully.
Testing Type: Functional Testing.
Test Data: Use the credentials from log in first.
Predicted Outcome: The user should be able to log out successfully and be
redirected to the login page or home page.
Steps: Steps to carry out the test. See step formatting rules below.

1. Click on the "Logout" button.

2. Observe the outcome.

Status: Pass/Fail.
Table 4.6: TC 06

Test Case Event Creation

Test Case: Confirm that the creation of an event with the necessary
information (name, date, venue, description) is possible.
Testing Type: Functional Testing.

32
 CHAPTER 5: CONCLUSION

Test Data: Choosing a specific date.

Predicted Outcome: The event is successfully created, its details saved, and it shows
up in the dashboard.

Steps: 1. Login.
2. Create Event
3. Enter "Test Event" in the Name field. Test event can be
anything like e.g. birthday.
4. For the event, provide a precise date.
5. Put "Test Venue" in the Venue field.
6. Use the following description to add it: "This is a test
event for verification purposes.”
7. The event can be created by clicking the "Save" or
"Create" button. Check to see if the system confirms
the creation of the event or shows a success message.
8. Access the event list view or dashboard by navigating.
9. Verify that the "Test Event," the newly created event,
is present in the dashboard's event list.

Status: Pass (all steps executed successfully

Table 4.7: TC 07

Test Case Registration of Vendors

Test Case: Verify that vendors can register by giving the required
information.
Testing Type: Functional Testing.
Test Data: Contact Details: [Please supply a working phone number and
email address for testing] , e.g. "Catering, Decorations" is the
services provided.
Predicted Outcome: The vendor profile is available for use in future event planning,
and vendor details are saved.
Steps: Steps to carry out the test. See step formatting rules below.

1. Open the website and navigate to the Vendor

Registration Page.
2. Please enter a email address.
3. State "Catering, Decorations, Photography" or any
other related services as the services provided.
4. Click the "Register" or "Submit" button to send in the
registration form.

Status: Pass
Table 4.8: TC 08

33
 CHAPTER 5: CONCLUSION

Test Case Workflow of Event Planning

Test Case: Examine every step of the process, from organizing the event
to choosing and scheduling the vendors.
Testing Type: User Acceptance Testing (UAT).
Test Data: Event Specifics: Name: "Test Event", Venue: "Test Venue",
Date: [Select a date], Description: "Testing event planning
workflow."
Details of the vendor: Service Provider: "Test Vendor Inc.";
Service Type: "Catering, Decorations"; Contact: [Enter a
working phone number and email address].
Predicted Outcome: Individuals can effortlessly progress through the stages
without running into any problems.
Steps: Steps to carry out the test. See step formatting rules below.

1. Organizing an Event.
2. Choosing a Vendor.
3. Reservation Procedure.
4. Verification.

Status: Pass
Table 4.9: TC 09

Test Case Expanding Event Size (Scalability Testing)

Test Case: Plan events that get bigger and more complicated (more
vendors, longer guest lists, etc.).
Testing Type: Performance Testing.
Test Data: Event 1: Simple affair with one vendor and a limited guest
list (perhaps 50).
Event 2: Multiple vendors (2 or 3), moderate complexity
(e.g., 200 attendees).
Event 3: Lots of vendors, a wide range of services, and high
complexity (such as 500+ attendees).
Predicted Outcome: The system keeps up its performance even with more event
data, without any errors or slowdowns.

Steps: Steps to carry out the test. See step formatting rules below.

1. Getting ready: Make sure the system is prepared for

testing its scalability. Create test scenarios that
correspond to the various event complexities that are
indicated in the test data.
2. Organizing an Event:
3. First, plan an event with just one vendor and a limited
number of attendees. Move on to Event 2: Plan a
somewhat complicated event that will have more
participants and vendors. Create Event 3, which will

34
 CHAPTER 5: CONCLUSION

be the most intricate with a large number of

participants and a wide range of vendors offering
various services, at the end.
4. Track the Performance of the System: Throughout
the test, keep an eye on system performance metrics,
paying particular attention to response time, resource
usage, and any mistakes made when creating events.
5. Observation and Interpretation: As events become
more complex, make sure the system doesn't slow
down, malfunction, or become unresponsive. Examine
performance metrics to find any areas that need to be
optimized, bottlenecks, or performance degradation.

Status: Pass
Table 4.10: TC 10

Test Case Control of Access

Test Case: Confirm that users can only access the features that are
relevant to their role (vendor, admin, or event planner).
Testing Type: Security Testing.
Test Data: User Positions:
Administrator: Complete control over all features and
capabilities.
Event Planner: The ability to create, manage, and view
vendor details for events.
Vendor: Limited access to event planner functionalities, but
view and manage their profile.
Predicted Outcome: Proper enforcement of access permissions according to user
roles.

Steps: 1. Login with Different User Roles.

2. Admin Access Test.
3. Event Planner (user) Access Test.
4. Test of Vendor Access.

Status: Pass
Table 4.10: TC 10

Test Case Consistency in the User Interface (UI)

Test Case: Verify that layouts and UI components are consistent
throughout the platform's various sections.
Testing Type: Usability Testing.
Test Data: UI Components to Confirm:

 Buttons.

35
 CHAPTER 5: CONCLUSION

 Forms /Input fields.

 Menus/Navigation.
 Typefaces and Typography.
 Themes/Colors.
 Spacing/Layout.

Predicted Outcome: The usability and consistency of UI elements (buttons, menus,

and forms) are maintained.

Steps: 1. Verify the navigation: Explore the various sections

of the platform, including the profile settings, vendor
management, event creation, dashboard, and so on.
Examine and contrast how buttons, links, and other
menu and navigation element placement and styling
are consistent.
2. Consistency of Button: Examine the different buttons
(such as "Save," "Submit," and "Cancel") that are used
in the various sections. Make sure that button
placement, size, color, and design are all the same.
3. Fields for Input and Forms: Check for uniformity in
input field alignment, labeling, and placeholder
placements on forms. Verify that input field styling
and behavior (such as focus states and error handling)
are consistent.
4. Fonts and Typography: Make sure that the font
styles (font-family, size, and weight) are all the same
across the platform. Check the readability and text
alignment in each section.
5. Consistency in Theme and Color: Verify whether
the themes and color schemes are the same throughout
the different pages and sections. Make sure that
elements such as buttons, headers, and backgrounds
are consistently used in the primary and secondary
colors.
6. Layout and Spacing: Verify consistency between
sections' padding, margins, grid systems, and layout
structures. Make sure there is a consistent, eye-
catching distance between each element.

Status: Pass
Table 4.11: TC 11

Test Case Cross-Browser Compatibility

Test Case: Confirm that the platform works with various browsers
(Chrome, Firefox, Safari).
Testing Type: Compatibility Testing.

36
 CHAPTER 5: CONCLUSION

Test Data: Browsers To Test:

 Mozilla Firefox
 Internet Explorer
 Google Chrome
Predicted Outcome: The platform operates consistently with no issues related to
layout or functional inequality.

Steps: 1. Accessing the Platform: Check that all features and

functionalities are operating as intended by opening
the platform in Google Chrome. Conduct a basic
walkthrough to confirm the design, navigation, and
essential features
2. In Firefox, repeat: Use Mozilla Firefox to access the
platform.
3. Verify that the features, functionalities, and layout
match what you see in Chrome. Look for any layout
problems, like misaligned components or
malfunctioning features.
4. Functional Examination: Check that each browser
is capable of performing essential tasks like creating
events, choosing vendors, authenticating users, etc.
Make sure that all browsers behave the same way
when it comes to forms, buttons, input fields, and
interactions.
5. Testing for responsive designs: Use developer tools
to emulate different devices or resize the browser
window to test responsiveness. Check to see if the
platform works and is still usable on different screen
sizes.
6. Testing Particular to a Browser (if applicable):
Test those features in each browser separately if there
are known problems or improvements unique to that
browser.

Status: Pass

Table 4.12: TC 12

Test Case Mobile Responsiveness and device Compatibility

Test Case: Verify that the platform works well and is responsive on a
range of mobile screen sizes.
Testing Type: Compatibility Testing.
Test Data: Mobile Devices TO Test:
Android Smartphones(different screen sizes with various
models)

37
 CHAPTER 5: CONCLUSION

Predicted Outcome: Mobile users can effortlessly access and utilize the platform
without any layout distortions.

Steps: 1. Platform of Access for Mobile Devices: Launch the

platform on various smartphone models (Android)
with different screen sizes.
2. Fundamental Functionality Testing: Use each
mobile device to browse the main features of the
platform, such as vendor selection, event creation, and
login. Check that there are no problems with accessing
or using any of the main features.
3. Verify responsive design: To simulate various screen
sizes, resize the desktop browser window or use
mobile emulators. Check to see if the content and
layout of the platform adapt to different screen sizes
without causing any distortion.
4. Communication and Directions Examination: Try
out the touch features, like swiping through content,
scrolling, and tapping buttons. Make sure there are no
broken links or buttons that are too small to be
touched, and that the navigation and usability are
seamless.
5. Validation of Forms and Input: Verify the usability
and input simplicity of form fields and interactions on
mobile devices. Verify the usability and appropriate
size of the buttons, dropdown menus, and input fields.
6. Verification of Media Content: Examine the
rendering and screen-fitting of media content (videos,
images). Make sure the media components on smaller
screens don't jiggle or distort.

Status: Pass

Table 4.13: TC 13

Test Case Updates on Features - Editing Events

Test Case: Modify an already-existing event to make sure that updates
don't interfere with features that were previously operational.
Testing Type: Regression Testing.
Test Data: Existing Event Data:

 Event information that has already been created and is

known, such as the name, date, location, description,
and so forth.
 information that has been updated for editing (date,
location, description, etc.).

38
 CHAPTER 5: CONCLUSION

Predicted Outcome: Modifications are stored without creating problems for other
event-related features.

Steps: 1. Editing Access Events: Open the platform and

navigate to the event editing feature.
2. Edit the Event Information: Add the updated data to
any appropriate fields in the event's description, date,
location, or other relevant information.
3. Conserve Modifications: Make sure the system
validates that the update was successful before saving
the modified event.
4. View Event Details: Verify that the event list or
dashboard appropriately displays the updated event
details.
5. Validation of functionality: Test features that are
connected to the event, such as reservations for
vendors, attendance tracking, or alerts. Verify whether
the updated event is accurately reflected in the search
results.
6. Testing for Regression: Regression testing should be
done to make sure the update hasn't affected any
previously functionalities that weren't directly related
to the edited event. Test unrelated to the edited event
other event creations, vendor bookings, user
interactions, etc.

Status: Pass

Table 4.14: TC 14

39
 CHAPTER 5: CONCLUSION

CHAPTER 5
CONCLUSION
5.1 Conclusion:
The consummation of the EventBliss project denotes a progressive defining moment in
the field of occasion the board. With cautious preparation, smart innovation decisions,
and a client centered outlook, this stage addresses the association of inventiveness and
utility, prepared to totally change how occasions are arranged.Generally, EventBliss is
a wonder of React.js innovation, handily consolidating a complex frontend experience.
This ensures a powerful mix of structure and capability and gives organizers, sellers,
and directors with a simple to-utilize interface when joined with major areas of strength
for a foundation. The complete utilitarian necessities for every partner, which
incorporate sellers with full profiles and booking capacities, directors with instruments
for control and the executives, and clients with a simple to-utilize occasion arranging
venture, show serious areas of strength for a to satisfying the shifted needs of clients.
EventBliss gives a very exhaustive testing process that covers useful, execution,
security, and convenience perspectives to guarantee a reliable, secure, areas of strength
for and. It is proof of the stage's obligation to giving an immaculate, viable, and easy to
understand insight.In synopsis, EventBliss is something beyond an occasion the board
apparatus; it's an illustration of imagination, collaboration, and client strengthening. It's
a unique environment that rethinks the standards for occasion the board, with organizers
making the plans, merchants displaying, and chairmen overseeing. This stage focuses
on versatility, security, and unfaltering client fulfillment to meet as well as outperform
industry benchmarks and lay out another highest quality level in the field of occasion
association. With the possibility to assume a vital part in the progress of multitudinous
important occasions, EventBliss holds out trust for while occasion arranging will be
related with viability, imagination, and faultless execution. The joining of computer
based intelligence calculations for artificial intelligence proposal, picture
acknowledgment, and dynamic planning in our task changes occasion arranging,
presenting customized ideas, imagined decisions, and streamlined planning for a
consistent and keen client experience, setting new benchmarks in the business.

5.2 User’s Benefits by accessing our website:

 User-Friendly interface.
 Easily Accessible (available in mobile, tablet, computer etc.)
 Diverse Event Categories (birthday, wedding, game night etc.)
 Customization (theme e.g. bridal shower theme, minimum & maximum
amount)
 Streamlined Booking Process.
 User Reviews and Feedbacks.
 Personalized Recommendation (user preferences and suggestions).
 Control Over Plans.
 Packages in discounted and reasonable price through our platform.
 Filters and drop down options.

5.3 Filters:
 Event Planning Dashboard: Users can filter events based on particular
parameters like deadlines or guest count, or they can apply filters to
view specific event statuses (upcoming, in progress, completed).

40
 CHAPTER 5: CONCLUSION

 Vendor Profiles: You can use filters on vendor profiles to arrange

vendors according to their specializations, ratings, costs, or dates of
availability.
 Event Categories: Users can use filters to identify particular
subcategories or themes (such as venue type, food, or photography,
decoration) within each event category that suit their tastes.
 User Preferences: Based on their previous interactions, users can set
preferences or customize filters, resulting in more individualized
experiences and personalized recommendations.

5.4 Limitations:
 Internet access 24/7.
 Shop owner (vendor) can accept/reject user reservation request on
his/her convenience.

5.5 Uniqueness of Our Website:

 Personalized event planning.
 Intuitive user interface.
 Continuous innovation (regular updates, new features)
 Engaging community and support.
 AI Algorithms (AI Recommendation, Image Recognition, Dynamic
Budgeting Algorithms).

41
 REFERENCES
[1] K. Pinjari and K. Nur, "Smart event management system," International Journal of
Computer Science Trends and Technology, vol. 4, no. 2, pp. 161-164, 2016.
[2] A. B. Mnaouer, A. Aendenroomer, and L. Hismanto, "An event chain notification and
management system using SMS," in 2004 IEEE International Conference on Industrial
Technology, 2004. IEEE ICIT'04., 2004, vol. 2: IEEE, pp. 813-818.
[3] A. E. Yalini, "Web Based Wedding Hall Management System For Loyolas Wedding Hall,
Jaffna," 2017.
[4] W. H. P. Chandrasiri, "Wedding Organizer–wedding planning web application," 2021.
[5] M. R. L. Perez, A. C. Lagman, and R. T. Adao, "Event Management Solution Using Web
Application Platform," presented at the Proceedings of the 2017 International
Conference on Information Technology, Singapore, Singapore, 2017. [Online].
Available: https://doi.org/10.1145/3176653.3176677.
[6] K. RAJESWARI and A. RAMAMANI, "Online Event Management System."
[7] D. A. Shah, H. Vasudavan, and N. F. Razali, "Event Management Systems (EMS),"
Journal of Applied Technology and Innovation (e-ISSN: 2600-7304), vol. 7, no. 2, p. 45,
2023.
[8] S. Nithila, D. Madushyani, W. Perera, M. Nivethan, and G. Fernando, "Your Dream
Virtual Wedding Planning System," Scientific Research Journal I (III) ISSN, pp. 2201-
2796, 2013.
[9] D. Sugathapala, "“My Wedima” Wedding Planning Web Application," 2021.
[10] E. Maiyana, "Penyewaan Online Wedding Organizer Berbasis Web," Jurnal Sains dan
Informatika: Research of Science and Informatic, vol. 5, no. 1, pp. 24-30, 2019.
[11] P. E. Bézier, "Example of an existing system in the motor industry: the Unisurf system,"
Proceedings of the Royal Society of London. A. Mathematical and Physical Sciences,
vol. 321, no. 1545, pp. 207-218, 1971.
[12] B. Fitzgerald, "The use of systems development methodologies in practice: a field
study," Information Systems Journal, vol. 7, no. 3, pp. 201-212, 1997.

28