Abstract

Event management system is a convenient method to book event and views event in and
around the user’s interests and in the desired time. These event maybe of any type including
concerts, art show, marriage, baby shower, etc. This project enables the user to access all the
details regarding the event and make bookings.

Event management system has users with user status and admin with admin status. The
registered users can visit the website and view the events and book the event through contact.
The admin can create, edit, delete the events. The project is based on CRUD operation. This
project is developed in PHP and MySQLi. The project provides the basic functionality
required to book event. It allows the users to select an event from the list of events. It allows
users to search the events that is needed for the users. It is error free, secure, reliable and fast
management system. It can assist users to concentrate on their other activities rather to
concentrate on record keeping. Thus it will help the company in better utilization of
resources. The company can maintain computerized records without redundant entries.

The aim of this project is to fulfill the requirement of the users and and save their time. The
project describes how to manage for good performance and better services for the client.
Acknowledgement
I would like to express my gratitude and appreciation to all those who gave me the possibility
to complete this project. Special thanks is due to my supervisor Mr. Ujjwal Bhusal whose
help, simulating suggestions and encouragement helped me in all time of fabrication process
and in writing this project. I also sincerely thanks for the time spent proofreading and
correction my many mistakes.

I specially acknowledge him for his advice, supervision and the vital contribution as and
when required during this project. His involvement has triggered and nourished intellectual
maturity that will help me for a long time to come.
Table of Contents

Chapter 1: Introduction...................................................................................................................................................
1.1 Introduction.........................................................................................................................1
1.2 Statement of Problem..........................................................................................................2
1.3 Objective....................................................................................................................................3
1.4 Scope and Limitation................................................................................................................3
1.5 Report Organization ................................................................................................................5
Chapter 2: Literature Review.........................................................................................................................................
2.1 Background Study.....................................................................................................................6
2.2 Literature Review......................................................................................................................8
Chapter 3: System Analysis and Design.........................................................................................................................
3.1 System Analysis.......................................................................................................................11
3.1.1 Requirement Analysis......................................................................................................11
3.1.2 Feasibility Study:..............................................................................................................13
3.1.3 Data modeling (ER-Diagram):........................................................................................15
3.1.4 Process Modeling(DFD)...................................................................................................15
3.2 System Design..........................................................................................................................16
3.2.2 Ui interface........................................................................................................................17
3.2.3 Physical DFD....................................................................................................................24
Chapter 4: Implementation and Testing ........................................................................................................................
4.1. Implementation ......................................................................................................................25
4.1.1. Tools Used (CASE tools, Programming languages, Database platforms) ..................25
4.1.2. Implementation Details of Modules (Description of procedures/functions)................31
4.2. Testing.....................................................................................................................................32
4.2.1. Test Cases for Unit Testing ............................................................................................32
Chapter 5: Results(Outcome)..........................................................................................................................................
5.1. Lesson Learnt / Outcome.......................................................................................................36
5.2. Conclusion..............................................................................................................................36
5.3. Future Recommendations......................................................................................................36
Reference..........................................................................................................................................................................
Bibliography.....................................................................................................................................................................
List of Figures

Figure 1: Problems..............................................................................................................................2
Figure 2: Solution................................................................................................................................2
Figure 3: Waterfall Model................................................................................................................13
Figure 4: Use Case Diagram.............................................................................................................15
Figure 5: ER-Diagram......................................................................................................................15
Figure 6: Process Modeling..............................................................................................................16
Figure 7: Architect Design................................................................................................................16
Figure 8: Register Page.....................................................................................................................17
Figure 9: Login Page.........................................................................................................................17
Figure 10: Amin Event......................................................................................................................18
Figure 11: Dashboard.......................................................................................................................18
Figure 12: Bookings..........................................................................................................................19
Figure 13: Admin Blogs....................................................................................................................19
Figure 14: User..................................................................................................................................20
Figure 15: Messages..........................................................................................................................20
Figure 16: Admin Logout.................................................................................................................21
Figure 17: Home................................................................................................................................21
Figure 18: About...............................................................................................................................22
Figure 19: Events..............................................................................................................................22
Figure 20 Contact:............................................................................................................................23
Figure 21: Blogs.................................................................................................................................23
Figure 22: User Logout.....................................................................................................................24
Figure 23: Physical DFD...................................................................................................................24
Figure 24: Admin Header.................................................................................................................37
Figure 25: Gantt Chart.....................................................................................................................37
Figure 26: Admin Event...................................................................................................................38
Figure 27: Admin Page.....................................................................................................................38
Figure 28: Admin Bookings..............................................................................................................39
Figure 29: Admn Blogs.....................................................................................................................39
Figure 30: Admin Contact................................................................................................................40
Figure 31: Admin User.....................................................................................................................40
Figure 32: Admin CSS......................................................................................................................41
Figure 33: Header.............................................................................................................................42
Figure 34: Footer...............................................................................................................................42
Figure 35: About...............................................................................................................................43
Figure 36: Event................................................................................................................................43
Figure 37: Blogs.................................................................................................................................44
Figure 38: Contact............................................................................................................................44
Figure 39: CSS...................................................................................................................................45
Figure 40: Login................................................................................................................................46
Figure 41: Logout..............................................................................................................................46
Figure 42: Register............................................................................................................................47
List of Tables

Table 1: Tools Used...............................................................................................................26

Table 2: Programming Language........................................................................................30
Table 3: Admin login with correct data...............................................................................32
Table 4: Admin Login with incorrect data..........................................................................33
Table 5: User Login with correct data.................................................................................33
Table 6: User Login with incorrect data..............................................................................34
Table 7: Searching with valid data.......................................................................................34
Table 8: Searching with invalid data...................................................................................35
Chapter 1: Introduction
1.1 Introduction
An event can be described as a public assembly for the purpose of celebration, education,
marketing or reunion. Events can be classified based on their size, type and context. An event
can be a social / life cycle event like a birthday party, engagement, wedding etc. or an
education and career event like an education fair, job fair, workshop, seminar, debate,
contest, competition etc.

The term “Management” characterizes the process of and the personnel leading and directing
all or part of an organization through the deployment and manipulation of resources.
According to the Oxford English Dictionary, the word “manage” comes from the Italian
maneggiare (to handle). Management has to do with power by position, whereas leadership
involves power by influence.

Event Management is the process of analyzing, planning, marketing, producing and

evaluating an event. It is a different way of promoting a product, service or idea. If an event
is managed efficiently and effectively, it can be used as a very powerful promotional tool to
launch or market a product or service. It requires certain core values to be deployed to every
element, process and decision to justify professional approach and achieve effective and
efficient results. It can be delivered by an individual or a group of individuals or a company
who specializes in planning and organizing events.

1.2 Statement of Problem

Event involves bringing people together within a time frame in a particular place. The major
problem is that it does not provide up to date status and accurate data regarding each event
and how information about the event is been communicated. The manual way of conveying
messages bring about certain restrictions such as non-availability of the proposed receiver
omission of vital details from the dispatcher etc. Searching for the location of the company is

1
also a hassle. Many people don’t even know the location of the company. So website is made
so that people don’t need to look for the location to book event which makes the user easy
and less time consuming.
Figure 1: Problems

Figure 2: Solution

1.3 Objective
The aim of this project is to design and implement a web based event management system.
To achieve this some specific objectives includes the following:
 To understand the concept of event management
 To study the different types of events
 To analyse the role of creativity in event management process

1.4 Scope and Limitation

Scope:
 Save time
 Save money
 Any user can excess this system
 Easy to search the event

Limitations:

 This system is used for online purpose only.

 User may have some dis-satisfaction regarding the event.

Methodology

2
In its most common sense, methodology is the study of research methods. However, the term
can also refer to the methods themselves or to the philosophical discussion of associated
background assumptions. A method is a structured procedure for bringing about a certain
goal. In the context of research, this goal is usually to discover new knowledge or to verify
pre-existing knowledge claims. This normally involves various steps, like choosing
a sample, collecting data from this sample, and interpreting this data. [1]

Waterfall Model
The waterfall model is a breakdown of project activities into linear sequential phases, where
each phase depends on the deliverables of the previous one and corresponds to a
specialization of tasks. The approach is typical for certain areas of engineering design.
In software development, it tends to be among the less iterative and flexible approaches, as
progress flows in largely one direction ("downwards" like a waterfall) through the phases of
conception, initiation, analysis, design, construction, testing, deployment and maintenance.
[2]

Figure 3: Waterfall model

1. Requirement gathering and analysis

In this stage, you should gather comprehensive information about what this project requires.
You can gather this information in a variety of ways, from interviews to questionnaires to
interactive brainstorming. By the end of this phase, the project requirements should be clear,
and you should have a requirements document that has been distributed to your team.

3
2. System design
Using the established requirements, your team designs the system. No coding takes place
during this phase, but the team establishes specs such as programming language or hardware
requirements.
3. Implementation
Coding takes place in this phase. Programmers take information from the previous stage and
create a functional product. They typically implement code in small pieces, which are
integrated at the end of this phase or the beginning of the next.
4. Testing
Once all coding is done, testing of the product can begin. Testers methodically find and
report any problems. If serious issues arise, your project may need to return to phase one for
reevaluation.
5. Deployment of System
In this phase, the product is complete, and your team submits the deliverables to be deployed
or released.
6. Maintenance
The product has been delivered to the client and is being used. As issues arise, your team
may need to create patches and updates may to address them. Again, big issues may
necessitate a return to phase one.
[3]

1.5 Report Organization

The pages from certificate page to numbered in roman from page number 1. The page
number should be inserted at the bottom, aligned center. The paper size corresponds to A4.
The margin must be set as Top = 1, Bottom = 1; Right = 1; Left = 1.25. All paragraphs must
be justified and have a spacing of 1.5 and the content of the document should be in Times
New Roman Font. The font size in the paragraph is 12. Font size for the headings is 16, 14 is
for section heading, 12 is for the sub-section heading. All the headings are bold faced.
There's Five chapters which have different steps of developing the main projects(Event
management). We have introduction with background related to event management along
with it’s problem statements, objective, scope and limitation and report organization in

4
chapter 1. where as in chapter 2, we have background study and literature review of the
project. Similarly in chapter 3, we have system analysis and Architectural Design. In System
analysis, it includes requirement analysis, feasibility analysis, Data modeling (ER-
DIAGRAM) and Process modeling. Where requirements analysis includes functional
requirements and non-functional requirements. In Feasibility analysis, it includes Technical,
operational economic and schedule. Architectural Design includes Database Schema design,
interface design and physical DFD. In chapter 4, we have implementation and Testing.
Where implementation includes Tools used and Implementation details of modules. Testing
which includes unit testing and system testing. As chapter 5 is the final chapter which consist
of lesson learnt(outcome), conclusion and future recommendations of the project.

Chapter 2: Literature Review

2.1 Background Study
The earliest recorded events and gatherings promoted peace and friendship between tribes
and clans, and the first known event planner was Cleopatra. She hosted elaborate, lavish,
sumptuous meetings in pursuit of potential lovers. Cleopatra even went as far as entering one
meeting by drifting down the Nile River on a boat filled with candles and perfume in order to
impress Mark Anthony. However, Cleopatra’s events would not have been possible without
her servants and free labor. Communication was very limited, and messages were often hand
delivered which usually took weeks, if not months, to be delivered.

Luxurious events and parties continued with medieval French Royalty. Wealthy aristocratic
women were in charge of event management, the most notable being Madame Pompadour,
the mistress to King Louis XV of France and Marie Antoine. Parties were themed with
costumes and popular musicians of the time.

The Industrial Revolution created the need for events and connecting to expand beyond
parties for the elite and royal families. Thus, industrialization provided a stronger economy
by increasing manufacturing and generating business growth, and it ultimately became
necessary for people to set up meetings and events in order to collaborate and grow their
businesses. People were making more money, which meant that they could spend more on

5
hosting events. The expansion of transportation provided options to increase the number of
events and meetings, as well as an array of location options. New modes of transportation
such as trains permitted a feasible manner for people to travel to and from events, all in a
timely manner.

The introduction of mobile phones and the internet also had an enormous impact on event
planning. With the use of these electronics, communication could now happen at any time
during the day, from anywhere in the world. Individuals can now create, locate, register, and
document an event by using one small portable device.

Then vs Now
Registration
Then: Prior to the 1990s and 2000s, event organizers had to use hand-written registration
processes and all documents were physically mailed. It could take days to reach it’s final
destination and it was easy for documents to become lost.
Now: Documents can be emailed or uploaded to a dropbox instantly and registration forms
can be filled out online.
Locating
Then: Before the internet, attendees had to pull out a physical map to find the location of an
event, which may have been difficult and stressful.
Now: One simply needs to type an address into Google Maps to receive turn by turn
directions and even obtain a new route if they get lost or make a wrong turn.
Attendees
Then: Curious who’s attending an event? Back then, placing a telephone call to your friends
or asking them directly in-person was the only solution.
Now: Through social media and event organization websites, attendees can see virtually who
is interested in or attending an event.

6
Advertising and Finding Events
Then: Before the internet, flyers, posters, and word-of-mouth were popular ways to advertise
events.
Now: People can search for events utilizing websites such as City Event. Users can type in
their location and find hundreds of events they may not have even know existed! The most
considerable change technology has afforded is the availability for an individual or
organization to have more control over event management. Software and websites allow
people to construct advertisements for events with user-friendly formats that are slick and
professional. Ticket sales and registration are organized in one spot, and in the fast-paced
world of the internet, time is limited and valuable. Event management websites and apps
such as City Event save people time while providing easy options for creating events.

2.2 Literature Review

Event management entails the application of management in the creation and development of
large-scale events (Emmers & Wolff, 2008) [1]. The process of coordinating and planning
events is usually regarded to as event planning, and it includes a variety of things discussed
in the paper (Martin-Flatin, Jakobson, & Lewis, 2007) [2]. In regards to the above
information, I work as an event manager at an event planning company. The company serves
as a one-stop shop that offers everything for its customers such as wedding cakes, fresh
flowers, wedding flavors, tables, chairs, draping, lighting, linens among other items. In
achieving its objectives, the company has incorporated an array of stakeholders such as
wedding coordinators, photographers, catering personnel, entertainment person among
others. The company offers a gamut of event planning services in an effort of providing
every event the full attention that it deserves and gives the best services to its customers
(Corrado, 2011) [3].

However, the company is faced with is increased competition from other similar industries.
The event planning industry has grown enormously over the last decade, and it is thus,
important for the company to develop strategies for reducing the associated competition

7
(Constantinides, 2006) [4]. According to Allen & Gale (2004) direct competition that the
many companies face such as my company exists in cases where companies produce similar
goods and products meant to target similar customers or market segment. Enterprises and
businesses are strongly affected by completion. The nature and range of services and goods
that they sell as well as the prices that they charge on the commodities is greatly influenced
by the level of completion in the particular industry (Tjosvold, Johnson, Johnson, & Sun,
2006) [5]. For an enterprise to be successful, it is thus, paramount for it to recognize the need
to adapt to the ever-changing global business environment to be able to get the competitive
edge over its rivals (Allon & Federgruen, 2007) [6]. In this regards, the paper presents a
literature review addressing the issue of increased competition currently confronted by the
organization.

Nowadays, the event industry has played a vital role in our society. People have come up
with a lot of occasions for organizing events such as educational events, birthdays,
international conferences, company parties etc. (Bladen & Charles, 2012) [7]. Generally
speaking, events are also a part of human beings’ social life because they get to know and
talk with different people with different backgrounds. However, in order to organize a good
and successful event, it requires a thorough and detailed planning process (Patrick & Maggie,
2010) [8]. Event managers and event coordinators need to collaborate in order to formulate
the most viable plan for events. In order to make events successful and well organized, all of
the stages in the entire planning process also need to be in harmony and be correlated with
one another. Risk management has been of great importance during the entire planning
process. Under no circumstances should risk management be underestimated (Wagen &
Lynn, 2001) [9]. Additionally, evaluation process helps event organizers and event managers
to realize which aspects should be improved and need further development. There are two
main parts in this thesis: the theoretical and the empirical part. The empirical part focused on
elaborating on the Annual International NIBS Conference in Lahti on May 21-23, 2014(Getz
2007) [10]. Regarding the research methods, deductive approach was utilized in this thesis.
Both quantitative and qualitative were also used in this thesis to analyze the collected data.

8
Furthermore, the process of data collection for the empirical part came directly from
interviews, emails, observations, materials provided by event organizers and surveys(Walters
& Rashid, 2009) [11]. Eventually, organizing a good and successful event always requires
thorough planning processes and effort. The Annual International NIBS Conference in Lahti
was a success because most of the guests and visitors were satisfied with the Conference
itself. The satisfaction level was calculated by evaluating the feedback and grade point
averages. However, the organizers of the NIBS Conference in Lahti, Finland should pay
attention to the time-management and marketing aspects (website design). Besides, risk
management is of great significance, which needs to be studied more. Visitors’ impressions
are an interesting aspect which facilitates the evaluation process(Shone & Parry, 2004) [12].
Key words: event management, Lahti, NIBS, conference, international, even managers, event
co-ordinators, planning process.

SolutionDots Systems has developed a solution for all of your problems and name it as Event
Management System. Event Management System is a system that will reduce your work
burden along with your budget best thing is through EMS it becomes very easy to handle all
matters of attendee management as well as event marketing. It gives you complete relaxation
regarding the event and make you able to think about the growth of your company and other
important matters. No doubt this a brilliant development of SolutionDots System. Let me
share some important feature of Event Management System to make it clear that how your
business life changes with the presence of EMS.

First and most important thing is Reduce Budget. Seriously it will reduce your budget the
question is how? So answer is in your hands, it will manage all your event registration,
ticketing, marketing etc. and you don’t have to hire extra manpower for this purpose, no need
to take some building on rent as booking center because everything will be online also there
is no need to pay a lot for marketing because EMS will manage all your marketing too.

Event Management System will provide online payment facility and make you able to collect
payment from all over the world without any limitation of boundaries. It sends automatic
email notifications to the attendees and make them feel that event manager cares for them
and their presence is really important. EMS will Improve Attendee Experience & Drive

9
Attendee. Once someone register for the event, Event Management System will start its work
to share brief details with attendee and will also offer them support to make their experience
excellent. It can Customized Attendee Notifications according to their desire and make them
able to feel that we respect their desire. EMS will Simplified Reporting like it control all of
your financial data, billing, invoices payments etc. All data and reports updated in EMS
could be exported in your desired format with Export Reports feature. Event Management
System store all records of your events in a single Database System, so it becomes very easy
to search any record if needed. Now here is a feature which will improve the strength of your
attendees, EMS will focus on Powerful Marketing of your events on social media interfaces
and catches more customers. With the help of SolutionDots System’s Event Management
System the attendee can keep an eye on the history of event. Scheduling of Resources means
that EMS will schedule all important resources for your event for example projectors,
conference rooms, presenters etc. EMS will also manage the wait list for over sold events.

Chapter 3: System Analysis and Design

3.1 System Analysis
System analysis is a process of analyzing the needs and requirements of the system being
developed. It analyzes various system components to determine whether the final product
will provide the expected result.
3.1.1 Requirement Analysis
Requirement analysis is one of the most important aspects of system analysis as it used to
determine the needs for the system being developed and what the system is expected to do
that will differentiate it from the current system in place.
I. Functional requirement
Registration: To enter into this site user has to register himself first. Requirement of
registration are first name, last name, user name, email id, password, confirm
password.
User login: the system provides facility to login into the system
Enter username and password
User profile page
Select the event: the user can select the event and also select payment method.
Logout: the system provides the facility to logout from the site

10
 Input: select logout option
Output: logout from the system
Processing: User will logout
Online package: online various payment packages will available to see.
II. Non-functional Requirement
Performance requirement: the system need to be reliable
 If unable to process the request then appropriate error messages.
 Web pages are loaded within few seconds.

Safety requirement: the details need to be maintained properly

 User must be authenticated.
 The database must be kept backed up.
Security requirement: after entering the password and user id the user can access
his/her profile.
 The details of user must be safe and secure
 Sharing of details.

List of cases:
Following are the use case:
Registration: to enter this site user has to register himself/herself first. Requirements
of registration are name, email-id, password, confirm password.
Login: the system provides facility to login into the system. Email-id and password.
User profile page.
Event selection: customer/user will select event by seeing at time slots available and
suitable packages.
Manager profile: produce detailed proposals for events (for example timelines,
suppliers, legal obligation, staffing and budgets).
Logout: the system provides the facility to logout from the site.
Input: select logout option
Output: logout from the system
Processing: User will logout.

11
System use case diagram

Figure 4: Use Case Diagram

3.1.2 Feasibility Study:

After doing the project Event Management System, study and analysing all the existing or
required functionalities of the system, the next task is to do the feasibility study for the
project. All projects are feasible – given unlimited resources and infinite time.
Feasibility study includes consideration of all the possible ways to provide a solution to the
given problem. The proposed solution should satisfy all the user requirements and should be

12
flexible enough so that future changes can be easily done based on the future upcoming
requirements.
a) Economical Feasibility
This is a very important aspect to be considered while developing a project. We
decided the technology based on minimum possible cost factor.
 All hardware and software cost has to be borne by the organization.
 Overall we have estimated that the benefits the organization is going to receive
from the proposed system will surely overcome the initial costs and the later on
running cost for system.

b) Technical Feasibility
This include the study of function, performance and constraints that may
affect the ability to achieve an acceptable system. For this feasibility study, we
studied complete functionality to be provided in the system, as described in the
System Requirement Specification (SRS) and checked if everything was possible
using different type of fronted and backend plaformst.

c) Operational Feasibility
No doubt the proposed system is fully GUI based that is very user friendly and
all inputs to be taken all self-explanatory even to a layman. Besides, a proper training
has been conducted to let know the essence of the system to the users so that they feel
comfortable with new system. As far our study is concerned the clients are
comfortable and happy as the system has cut down their loads and doing.

d) Schedule Feasibility
Schedule Feasibility is defined as the probability of a project to be completed
within its scheduled time limits, by a planned due date. If a project has a high
probability to be completed on-time, then its schedule feasibility is appraised as high.
In many cases a project will be unsuccessful if it takes longer than it was estimated:
some external environmental conditions may change, hence a project can lose its

13
 benefits expediency and profitability. If a work to be accomplished at a project does
not fit the timeframes demanded by its customers, then a schedule is unfeasible

3.1.3 Data modeling (ER-Diagram):

Figure 5: ER-Diagram

14
3.1.4 Process Modeling(DFD)

15
Figure 6: Process Modeling

16
3.2 System Design
3.2.1 Architecture Design

Figure 7: Process Modeling

Figure 7: Architect Design

17
3.2.2 Ui interface

Figure 8: Register Page

Figure 9: Login Page

18
Figure 10: Dashboard

Figure 12: Bookings

Figure
Figure 11: 14:
AminUser
Event

Figure 13: Admin Blogs

19
 Figure 15: Messages

Figure 16: Admin Logout

20
21
Figure 18: Events

Figure 8: About

22
Figure 20: Contact

Figure 21: Blogs

23
 Figure 22: User Logout

3.2.3 Logical DFD

Figure 23: Physical DFD

24
Chapter 4: Implementation and Testing

4.1. Implementation
4.1.1. Tools Used (CASE tools, Programming languages, Database platforms)

Used for Tools and technologies

Analysis tools

Design tools

Programming tools

Prototype tools

Maintenance tools

Diagram tools

25
 Process modeling tools

Process management
tools
Documentation tools

Configuration
management tools

Change control tools

Web development tools

Quality Assurance tools

Table 1: Tools Used

Visual Paradigm (VP-UML) is a UML CASE Tool supporting UML

2, SysML and Business Process Modeling Notation (BPMN) from
the Object Management Group (OMG). In addition to the modeling
support, it provides report generation and code engineering capabilities
including code generation. It can reverse engineer diagrams from code,
and provide round-trip engineering for various programming
languages.[4]

XMind is a mind mapping and brainstorming software, developed by

XMind Ltd. In addition to the management elements, the software can be
26
used to capture ideas, clarify thinking, manage complex information, and promote team
collaboration. As of April 2013, XMind was selected as the most popular mind mapping
software on Lifehacker. [5]

Microsoft Word is a word processing software developed

by Microsoft. It was first released on October 25, 1983, under the
name Multi-Tool Word for Xenix systems. Word for Windows is
available stand-alone or as part of the Microsoft Office suite. Word
contains rudimentary desktop publishing capabilities and is the
most widely used word processing program on the market. Word
files are commonly used as the format for sending text documents via e-mail because almost
every user with a computer can read a Word document by using the Word application, a
Word viewer or a word processor that imports the Word format. [6]

Visual Studio Code, also commonly referred to as VS Code, is a source-code

editor made by Microsoft for Windows, Linux and macOS. Features include
support for debugging, syntax highlighting, intelligent code
completion, snippets, code refactoring, and embedded Git. Users can change
the theme, keyboard shortcuts, preferences, and install extensions that add additional
functionality. [7]

XAMPP is a free and open-source cross-platform web server

solution stack package developed by Apache Friends,
consisting mainly of the Apache HTTP Server, MariaDB
database, and interpreters for scripts written in the PHP and Perl programming languages.
Since most actual web server deployments use the same components as XAMPP, it makes
transitioning from a local test server to a live server possible.
XAMPP’s ease of deployment means a WAMP or LAMP stack can be installed quickly and
simply on an operating system by a developer, with the advantage that common add-in

27
applications such as WordPress and Joomla can also be installed with similar ease using
Bitnami. [8]

StarUML is the successor of an object oriented modelling software

called Plastic. Plastic 1.0 was published in 1997 to support the OMT notation.
The version 1.1 published in 1998 dropped the OMT to support in favour of
UML. The last version under this brand was called Agora Plastic 2005 and
was published by the Korean company Plastic Software Inc, Seoul. It was an
internationalized product, compliant with UML 1.4,and claiming to support the Object
Management Group's MDA approach. [9]

Google Chrome is a cross-platform web browser developed by Google. It

was first released in 2008 for Microsoft Windows, built with free
software components from Apple WebKit and Mozilla Firefox. It was
later ported to Linux, macOS, iOS, and Android, where it is the default
browser. The browser is also the main component of ChromeOS, where it serves as the
platform for web applications.
Most of Chrome's source code comes from Google's free and open-source
software project Chromium, but Chrome is licensed as proprietary freeware. WebKit was the
original rendering engine, but Google eventually forked it to create the Blink engine; all
Chrome variants except iOS now use Blink. [10]

Mozilla Firefox, or simply Firefox, is a free and open-source web

browser developed by the Mozilla Foundation and its subsidiary,
the Mozilla Corporation. It uses the Gecko rendering engine to display
web pages, which implements current and anticipated web standards. In
2017, Firefox began incorporating new technology under the code name Quantum to
promote parallelism and a more intuitive user interface. Firefox is available for Windows
7 and later versions, macOS, and Linux. Its unofficial ports are available for
various Unix and Unix-like operating systems,
including FreeBSD, OpenBSD, NetBSD, illumos, and Solaris Unix. It is also available

28
for Android and iOS. However, as with all other iOS web browsers, the iOS version uses
the WebKit layout engine instead of Gecko due to platform requirements. An optimized
version is also available on the Amazon Fire TV, as one of the two main browsers available
with Amazon's Silk Browser. [11]

Balsamiq Cloud is a web-based user interface design tool for

creating wireframes (sometimes called mockups or low-fidelity
prototypes). You can use it to generate digital sketches of your idea
or concept for an application or website, to facilitate discussion and understanding before any
code is written. The completed wireframes can be used for user testing, clarifying your
vision, getting feedback from stakeholders, or getting approval to start development. [12]

A storyboard is a graphic organizer that

consists of illustrations or images displayed
in sequence for the purpose of pre-
visualizing a motion picture, animation, motion graphic or interactive media sequence. The
storyboarding process, in the form it is known today, was developed at Watt Disney
Productions during the early 1930s, after several years of similar processes being in use at
Walt Disney and other animation studios. [13]

Project Libre is a process management tools with both free open-

source and an upcoming cloud version. Project Libre is in beta testing. PorjectLibre desktop
is a free and open-source project management software intended as a standalone replacement
for Microsoft project. Project Libre is written in jave programming language. Project Libre is
certified to run on Linux, MacOS and Microsoft windows. [14]

Used for Programming tools

29
 Programming Languages

Table 2: Programming Language

HTML stands for hypertext markup language. HTML is the

standard markup language for documents designed to be displayed in
a web browser. It can be assisted by technologies such as Cascading
Style Sheets (CSS) and scripting languages such as JavaScript. [15]

Cascading Style Sheets (CSS) is a style sheet language used for

describing the presentation of a document written in a markup
language such as HTML or XML. CSS is a cornerstone technology of
the World Wide Web, alongside HTML and JavaScript. [16]

JavaScript, often abbreviated JS, is a programming language that is

one of the core technologies of the World Wide Web,
alongside HTML and CSS. As of 2022, 98% of websites use
JavaScript on the client side for webpage behavior, often incorporating
third-party libraries.[13] All major web browsers have a
dedicated JavaScript engine to execute the code on user’s devices.
JavaScript is a high-level, often just-in-time compiled language that
conforms to the ECMAScript standard. It has dynamic typing, prototype-based object-
orientation, and first-class functions. It is multi-paradigm, supporting event-
driven, functional, and imperative programming styles. It has application programming

30
interfaces (APIs) for working with text, dates, regular expressions, standard data structures,
and the Document Object Model (DOM). [17]

PHP is a general-purpose scripting language geared toward web

development. It was originally created by Danish-
Canadian programmer Rasmus Lerdorf in 1994. The PHP reference
implementation is now produced by The PHP Group. PHP originally stood
for Personal Home Page, but it now stands for the recursive initialism PHP: Hypertext
Preprocessor. [18]

4.1.2. Implementation Details of Modules (Description of procedures/functions)

1. Event search
Users can search for any event by typing a key word and the system will match it with the
event table in the database if there is a match it displays else shows no items found.
2. User login
Users can send login requests to the server with their email and password and the server will
check the user database and if any match id is found and password doesn’t matches error
message is shown if the email and password matches it directs you to homepage and stores.
3. Booking algorithm
After a user login, user can select a event and book the event. The event will be
sent to booking table and displayed in the profile of the user. User then also can remove the
booked event from their profile.
4. Create new user
User register can be done from the register page after the form is filled the data is checked if
the data is duplicate or valid if all the conditions match the user register is successful and the
data is sent to the database in users table and directed to the home page.

4.2. Testing
4.2.1. Test Cases for Unit Testing

31
Test case for admin login with correct data
In the following table admin login is checked using correct email and password when the
login is successful the site will redirect to dashboard and the test result was as expected and
successful.
Test Test Test Test data Expected Actual Pass/
case scenario steps result result Fail

1.a Check Enter Email- Login As Pass

admin URL [email protected] success expecte
login Enter m and d
with email Password: haha directed
valid and to
data. passwo dashboard
rd. .
Click
login
button.
Table 3: Admin login with correct data

Test case for admin login with incorrect data

The following table admin login is checked using incorrect email and password when the
login is attempted error message is shown and the site will stay in the same page the result
was as expected and successful.

Test Test Test Test data Expected result Actual Pass/Fail

case scenario steps result

1.b Check Enter Email- Login As Pass

admin URL [email protected] failed and expecte
login Enter m error d
with email Password: hehe message
valid and displayed
data. passwor .

32
 d.
Click
login
button.
Table 4: Admin Login with incorrect data

Test case for user login with correct data

The following table user login is checked using correct email and password when the login is
successful the site will redirect to homepage and the test result was as expected and
successful.

Test Test Test steps Test data Expected Actual Pass/Fail

case scenario result result

2. a Check Enter Email- Login As expected Pass

user URL [email protected] success
with Enter Password: user1 and
valid email and directed to
data. password. home page
Click
login
button.

Table 5: User Login with correct data

Test case for user login with incorrect data

The following table user login is checked using incorrect email and password when the login
is attempted error message is shown and the site will stay in the same page the result was as
expected and successful.

Tes Test Test steps Test data Expected Actual Pass/Fail

t scenario result result
case

33
 2. b Check Enter URL Email- Login As Pass
admin login Enter email [email protected] failed expected
with valid and Password: huhu and error
data. password. message
Click login displayed
button.

Table 6: User Login with incorrect data

Test case for searching with valid data

The following table search bar is tested marriage is searched in the search bar and page
redirected to another page showing products named marriage the result was successful and
expected.

Test Test Test steps Test data Expected Actual Pass/Fail

case scenario result result

3. a Search Login marriage Display As Pass

event Enter event event name expected
name in the marriage.
search bar.

Table 7: Searching with valid data

Test case for searching with invalid data

The following table search bar is tested iphone is searched in the search bar and page
redirected to another page there are no products named iphone so the result was no items
and it was as expected successful.
Test Test Test steps Test data Expected Actual Pass/Fail
case scenario result result

34
 3. b Search Login iphone No items As Pass
event with Enter event name in expected
invalid data the search bar.

Table 8: Searching with invalid data

Chapter 5: Result(Outcome)

5.1. Lesson Learnt / Outcome

The primary objective of this project was to create a working system that interacts with the
database to display content from database and allow editing or deleting existing content. The

35
lessons learnt was to designing the system completely before coding and background study
of similar kind of projects are equally important as other tasks.

5.2. Conclusion
Event Management System is user friendly and cost effective system, it is customized with
activities related to event management life-cycle. It provides a new edge to management
industry. City Event always keep your objectives and goals on top priority while developing
any plan of work.

5.3. Future Recommendations

I recommend booking event from event management company which helps us in many ways.
By booking event we can save our time. Event management company makes our event more
fun, attractive, memorable, efficient, organized and overall successful.

36
Appendices

Figure 249: Gantt Chart

Figure 26: 37
Admin Page
Figure 28: Admin Bookings

Figure 2912: Admn Blogs

38
Figure 30: Admin Contact

Figure 31: Admin User

39
Figure 32: Admin CSS

40
Figure 33: Header

Figure 34: Footer

41
Figure 35: About

Figure 36: Event

42
 Figure 37: Blogs

Figure 38: Contact

43
Figure 39: CSS

44
Figure 40: Logout

Figure 13: Login

45
Figure 42: Register

46
Reference
Wikipedia contributors. (2022b, August 21). Methodology. Wikipedia, The Free
Encyclopedia. https://en.wikipedia.org/w/index.php?title=Methodology&oldid=1105747084

Wikipedia contributors. (2022a, July 12). Waterfall model. Wikipedia, The Free
Encyclopedia. https://en.wikipedia.org/w/index.php?
title=Waterfall_model&oldid=1097696050

What the waterfall project management methodology can (and can’t) do for you. (2017,
August 23). Lucidchart.com. https://www.lucidchart.com/blog/waterfall-project-
management-methodology

Wikipedia contributors. (2022b, August 14). Visual Paradigm. Wikipedia, The Free
Encyclopedia.https://en.wikipedia.org/w/index.php?
title=Visual_Paradigm&oldid=1104313726

Wikipedia contributors. (2022a, May 31). XMind. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=XMind&oldid=1090756838

Wikipedia contributors. (2022e, August 27). Microsoft Word. Wikipedia, The Free
Encyclopedia. https://en.wikipedia.org/w/index.php?
title=Microsoft_Word&oldid=1107061291

Wikipedia contributors. (2022e, August 23). Microsoft Visual Studio. Wikipedia, The Free
Encyclopedia. https://en.wikipedia.org/w/index.php?
title=Microsoft_Visual_Studio&oldid=1106249509

Wikipedia contributors. (2022c, July 25). XAMPP. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=XAMPP&oldid=1100324213

Wikipedia contributors. (2022b, July 5). StarUML. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=StarUML&oldid=1096669928

47
Wikipedia contributors. (2022h, August 27). Google Chrome. Wikipedia, The Free
Encyclopedia. https://en.wikipedia.org/w/index.php?
title=Google_Chrome&oldid=1107043948

Wikipedia contributors. (2022h, August 25). Firefox. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=Firefox&oldid=1106637687

Wikipedia contributors. (2022a, May 17). Balsamiq. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=Balsamiq&oldid=1088325567

Wikipedia contributors. (2022c, June 19). Storyboard. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=Storyboard&oldid=1093943867

Wikipedia contributors. (2022c, June 5). ProjectLibre. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=ProjectLibre&oldid=1091705794

Wikipedia contributors. (2022h, August 8). HTML. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=HTML&oldid=1103220477

Wikipedia contributors. (2022j, August 20). CSS. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=CSS&oldid=1105562356

Wikipedia contributors. (2022l, August 22). JavaScript. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=JavaScript&oldid=1105988765

Wikipedia contributors. (2022o, August 25). PHP. Wikipedia, The Free Encyclopedia.
https://en.wikipedia.org/w/index.php?title=PHP&oldid=1106625428

48
Bibliography

[1] R. von Ammon, C. Emmersberger, T. Greiner, F. Springer and C. Wolff, Event-driven business
process management, 2008.

[2] J. Martin-Flatin, G. Jakobson and L. Lewis, Event correlation in integrated management: Lessons
learned and outlook, Journal of Network and Systems Management, 2007.

[3] C. Corrado, Event studies: A methodology review., 2011.

[4] E. Constantinides, The marketing mix revisited: towards the 21st century marketing, 2006.

[5] D. Tjosvold, R. Johnson, D. Johnson and H. Sun, Competitive motives and strategies:
Understanding constructive competition, 2006.

[6] G. Allon and A. Federgruen, Competition in service industries, 2007.

[7] Bladen, C. K. J. A. E. W. and N. , Events Management: An Introduction, 2012.

[8] D. Pelsmacker, P. G. M. V. d. and B. J. , Marketing Communications, a European Perspective,

2010.

[9] D. Wagen and L. , Event Management: For tourism, cultural, businessand sporting events,
2001.

[10] G. Event Studies: Theory, research and policy for planned events, 2007.

[11] R. W. and R. , Events Management, 2009.

[12] S. and P. , Successful Event Management, 2004.

[13] Bladen, Charles, Kennel, James, Abson, Emma, Wilde and Nick, Events Management: An
Introduction. Oxon: Routledge: Taylor and Francis, 2012.

49