S.

NO CONTENT PAGE NO

1 Abstract

2 Introduction

3 Event Manager

4 Event Management Process

5 Scope of the Project

6 Reports of Event Management System

7 Modules of Event Management System

8 Features of the Project Event Management

System

9 System Design of Event Management System

10 Flow Chart

11 Event Management System Source Code

12 Testing
13 Output

14 Future Work

15 Conclusion

16 Bibliography

1
 Abstract
Event management is the application of project management to the
creation and development of large or small scale events such as festivals,
ceremonies, formal parties, concerts, or conventions. The last few years
have seen a rapid growth in the event management industry. Considering
the existing system problems related to event management we are
developing an android application for event management. This application
will be accessible only for android. Application will mainly focus on
birthday party, marriage function and social events. The application will be
developed using android studio and back end will be managed in SQL
database. Application will have easy and feasible GUI for all type of users.
User need to Login at the initial phase, set his/her profile details including
location, choices, email-id, etc. User can modify or change His/her profile
at any stage. The core phase of the application will display list of events
based on the user profile details. This event will further contain description
about event, its exact location, ticket rates (if any), date and time. These
details will be firstly verified by the administrator to fulfill the security
protocols. In this paper we present an android mobile phone application to
make it easier for a layman to plan an event in a hassle-free manner. This
application will assist him/her in planning a successful and fun event.

2
INTRODUCTION

Event management is a process of organizing a professional and

focused event, for a particular target audience. It involves visualizing
concepts, planning, budgeting, organizing and executing events such as
wedding, musical concerts, corporate seminars, exhibitions, birthday
celebrations, theme parties, etc.

Event Management is a multi-million dollar industry, growing

rapidly, with events hosted regularly. Surprisingly, there is no formalized
research conducted to access the growth of this industry. The industry
includes fields such as the MICE (Meetings, Incentives and Events),
exhibitions, conferences and seminars as well as live music and sporting
events. On the profession side, event management is a glamorous and
exciting profession that demands a lot of hard work and dynamism.

The logistics side of the industry is paid less than the

sales/sponsorship side, though some may say that these are two different
industries.

Event management is the application of project management to the

creation and development of large scale events.

The process of planning and coordinating the events is usually

referred to as event planning and which can include budgeting, scheduling,
scheduling, site selection, acquiring necessary permits, coordinating
transportation and parking, arranging for speakers or entertainers, arranging
décor, event security, catering, coordinating with third party vendors, and
emergency plans.

3
 The events industry now includes events of all size from the
Olympics down to business breakfast meetings.

Many industries, charitable organization, and interest groups hold

events in order to market themselves, build business relationships, and
interest groups hold events in order to market themselves, build business
relationship, raise money, or celebrate achievement.

An event refers to a social gathering or activity, such as a festival,(

for example a musical festival), a ceremony(for example a marring ) and a
Party(for example a birthday party).

There are mainly 3 types of event management:

 Corporate Event Management

 Product Launch Management
 Special Event Management

4
EVENT MANAGER

The Event Manager is the person who plans and executes the event.
Event managers and their teams are often behind-the-scenes running the
event.

Event managers may also be involved in more than just the planning
and execution of the event, but also brand building, marketing and
communication strategy.

The event manager is an expert at the creative, technical and logistical

elements that help an event succeed.

This includes event design, audiovisual production, scriptwriting,

logistics, budgeting, negotiation and, of course, client service. It is a
multidimensional profession.

EVENT MANAGEMENT PROCESS

There are 2 stages of event management process namely, Event

planning and Event control.

 Event planning: To plan an event we must consider the

following area of an event, viz, feasibility, promotion, site
choice/design, staging, Shutdown, site map, event proposal.
 Event Control: To control an event we must look on the
following area logistics, negotiations, costing & cash flow,
event manual, I.T, decision making and change, risk
management.

5
SCOPE OF THE PROJECT

The objective of this application is to develop a system that

effectively manages all the data related to the various events that take place
in an organization.

The purpose is to maintain a centralized database of all event related

information. The goal is to support various functions and processes
necessary to manage the data efficiently.

Objective of Project on Event Management System:

The main objective of the Project on Event Management System is to

manage the details of Event, User, Ticket, Booking, and Organizer.

It manager all the information about Event, Login, Organizer, Event.

The project is totally built at administrative end and thus only the
administrator is guaranteed the access.

The purpose of the project is to build an application program to reduce

the manual work for managing the event, User, Login, Ticket. It tracks all
the details about the Ticket, Booking, Organizer.

6
Functionalities provided by Event Management System are as follows:

 Provides the searching the facilities based on various factors. Such as

Event, Ticket, Booking, Organizer
 Event Management System also manage the Login details online for
Booking details, Organizer details, Event.
 It tracks all the information of User, Login, Booking etc
 Manage the information of User
 Shows the information and description of the Event, Ticket
 To increase efficiency of managing the Event, User
 It deals with monitoring the information and transactions of Booking.
 Manage the information of Event
 Editing, adding and updating of Records is improved which results in
proper resource management of Event data.
 Manage the information of Booking
 Integration of all records of Organizer.

7
Scope of the Project Event Management System

It may help collecting perfect management in details. In a very short

time, the collection will be obvious, simple and sensible.

It will help an to know the management of passed year perfectly and

vividly. It also helps current all works relative to Event Management
System. It will be also reduced the cost of collecting the management &
collection procedure will go on smoothly.

Our project aims at Business process automation, i.e. we have tried to

computerize various processes of Event Management System.

 In computer system the person has to fill various forms & number of
copies of the forms can be easily generated at a time.
 In computer system, it is not necessary to create the manifest but we
can directly print it, which saves our time.
 To assist the staff in capturing the effort spent on their respective
working areas.
 To utilize resources in an efficient manner by increasing their
productivity through automation.
 The system generates types of information that can be used for
various purposes.
 It satisfy the user requirement
 Be easy to understand by the user and operator
 Be easy to operate
 Have a good user interface
 Be expandable
 Delivered on schedule within the budget.
8
Reports of Event Management System:

 It generates the report on Event, User, Login

 Provide filter reports on Ticket, Booking, Organizer
 You can easily export PDF for the Event, Login, Booking
 Application also provides excel for User, Ticket, Organizer
 You can also export the report into csv format for Event, User,
Organizer

Modules of Event Management System:

 Event Management Module: Used for managing the Event details.

 Organizer Module: Used for managing the details of Organizer
 Login Module: Used for managing the details of Login
 User Management Module: Used for managing the information and
details of the user.
 Ticket Module: Used for managing Ticket details
 Booking Module: Used for managing the Booking information
 Login Module: Used for managing the login details
 Used Module: Used for managing the users of the system

9
Features of the Project Event Management System:

 Product and Component based.

 Creating & Changing Issues at ease.
 Query Issue List to any depth.
 Reporting & Charting in more comprehensive way.
 User Accounts to control the access and maintain security.
 Simple Status & Resolutions.
 Multi-level Priorities & Severities.
 Targets & Milestones for guiding the programmers.
 Attachments & Additional Comments for more information.
 Robust database back-end.
 Various level of reports available with a lot of filter criteria’s.
 It contain better storage capacity.
 Accuracy in work.
 Easy & fast retrieval of information.
 Well designed reports.
 Decrease the load of the person involve in existing manual system.
 Access of any information individually.
 Work becomes very speedy.
 Easy to update information.

10
System Design of Event Management System

In this phase, a logical system is built which fulfils the given

requirements. Design phase of software development deals with
transforming performed in the following in the following two steps:

1.Primary Design Phase:

In this phase, the system is designed at block level. The blocks are created
on the basis of analysis done in the problem identification phase. Different
blocks are created for different functions emphasis is put on minimizing the
information flow between blocks. Thus, all activities which require more
interaction are kept in one block.

2. Secondary Design Phase:

In the secondary phase the detailed design of every block is performed.

Project planning:

Software Project plan can be viewed as the following:

1. Within the organization: How the project is to be implemented?

What are various constraints (time, cost, staff)? What is market
strategy?
2. With respect to the customer: Weekly or timely meetings with
the customer with presentation on status reports. Customers
feedback is also taken and further modification and development
are done. Project milestones and deliverables are also presented to
the customer.

11
For a successful software project the following steps can be followed:

 Select a Project
o Identifying project’s aims and objectives
o Understanding requirements and specification
o Methods of analysis, design and implementation
o Testing techniques
o Documentation
 Project milestones and deliverables
 Budget allocation
o Exceeding limits within control
 Project Estimates
o Cost
o Time
o Size of code

12
Conclusion of the project Event Management System:

Our project is only a humble venture to satisfy the needs to

manage their project work. Several friendly coding have also adopted.
This package shall prove to be a powerful package in satisfying all
the requirements of the school. The objective of software planning is
to provide a frame work that enables the manager to make reasonable
estimates made within a limited time frame at the beginning of the
software project and should be updated regularly as the project
progresses.

At the end it is concluded that we have made effort on following

points…

 A description of the background and context of the project and its

relation to work already in the area.
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the
actions that can be done on these things.
 We understand the problem domain and produce a model of the
system, which describes operations that can be performed on the
system.
 We included features and operations in detail, including screen
layouts.
 We designed user interface and security issues related to system.
 Finally the system is implemented and tested according to test cases.
13
Future Scope of the Project:

 In a nutshell, it can be summarized that the future scope of the project

circles around maintaining information regarding:
 We can add printer in future.
 We can give more advance software for Event Management System
including more facilities
 We will host the platform on online servers to make it accessible
worldwide
 Integrate multiple load balancers to distribute the loads of the system
 Create the master and slave database structure to reduce the overload
of the database queries
 Implement the backup mechanism for taking backup of codebase and
database on regular basis on different servers

The about mentioned points are the enhancements which can be done
to increase the applicability and usage of this project. Here we can maintain
the records of Event and User. Also, as it can be seen that now-a-days the
players are versatile, i.e. So there is a scope for introducing a method to
maintain the Event Management System. Enhancement can be done to
maintain all the Event, User, Ticket, Booking, Organizer.

14
 We have left all the options open so that if there is any other future
requirement in the system by the user for the enhancement of the system
then it is possible to implement them. In the last we would like to thanks all
the persons involved in the development of the system directly or
indirectly. We hope that the project will serve its purpose for which it is
developing there underlining success of process.

An Event Management System (EMS) is a software solution

designed to streamline the planning, organizing, and managing of events,
ranging from conferences to weddings, concerts, trade shows, or corporate
events. Here's an outline of the essential content and features that an Event
Management System typically offers:

15
1. User Management

 User Registration & Profiles: Allows event organizers, attendees,

vendors, and staff to create personalized accounts.
 Roles & Permissions: Different roles such as admin, organizer,
attendee, speaker, and sponsor, with varying levels of access to
system features.

2. Event Creation & Planning

 Event Setup: Enables organizers to create events with details like the
event name, date, location, and theme.
 Agenda Creation: Facilitates the development of schedules,
including sessions, workshops, and speaker timelines.
 Venue Selection: Provides options to choose or book event venues
with seating arrangements and other logistical requirements.

3. Registration & Ticketing

 Online Registration: Simplifies attendee registration through a

customizable online form.
 Ticket Sales: Ability to sell tickets with different pricing tiers (early
bird, VIP, regular, etc.).
 Payment Integration: Supports payment gateways for ticket
purchases and donations.
 Attendee Check-in: QR code-based or manual check-in system at the
event venue.

16
4. Event Marketing

 Promotional Tools: Tools to create and distribute marketing

materials such as invitations, posters, and newsletters.
 Email Campaigns: Automated email marketing to send invitations,
reminders, and updates to attendees.
 Social Media Integration: Features to promote events via social
media platforms.
 Event Website: Customizable event landing page or website that
includes all relevant details.

5. Communication & Collaboration

 Real-time Notifications: Push notifications and email updates for

attendees about event changes, sessions, etc.
 Chat and Messaging: Messaging systems to facilitate
communication between attendees, organizers, speakers, and
sponsors.
 Feedback & Surveys: Post-event surveys for gathering feedback to
improve future events.

17
6. Agenda & Session Management

 Session Scheduling: Organizes event sessions by time, date, and

location.
 Speaker Management: Handles speaker registrations, bios, session
proposals, and availability.
 Session Tracking: Allows attendees to plan and track sessions they
wish to attend.

7. Vendor & Sponsor Management

 Vendor Registration: Platforms to allow vendors and exhibitors to

register and book booths.
 Sponsorship Management: Manage sponsors, their packages,
benefits, and visibility.


8. Event Logistics & On-site Management

 Task Management: Assigns tasks to the event team, with deadlines

and priority levels.
 Staff Scheduling: Organizes staff schedules to ensure proper event
coverage.
 Resource Allocation: Manages logistics such as equipment, rooms,
or catering services.
 Real-time Updates: Informs staff and vendors of on-site changes as
they happen.
18
9. Post-Event Analysis

 Attendance Tracking: Tracks who attended, what sessions they

participated in, and their interactions.
 Reports & Analytics: Provides insights into ticket sales, attendee
demographics, session popularity, and more.
 Post-Event Engagement: Continues engagement with attendees
through follow-up emails, videos, or additional resources

10. Integration with Other Systems

 CRM Integration: Syncs with Customer Relationship Management

(CRM) software for managing leads and contacts.
 Calendar Integration: Syncs event schedules with calendars like
Google Calendar or Outlook.
 Third-Party Software Integration: Integrates with other tools like
live streaming platforms, virtual conferencing systems, and more.

11. Mobile App (Optional)

 Event App: Allows attendees to view schedules, speakers, and venue

maps directly on their mobile devices.
 Interactive Features: Enables networking through messaging, live
polls, or Q&A during sessions.

19
Benefits of an Event Management System:

 Efficiency: Automates repetitive tasks, reducing the time spent on

manual processes.
 Organization: Centralizes all event-related information, making it
easier for teams to collaborate.
 Customization: Offers flexibility to tailor the system to the specific
needs of the event.
 Data-Driven Insights: Provides valuable data and analytics to
measure success and improve future events.
 Cost-Effective: Reduces the need for paper-based processes, manual
data entry, and human error.

These are just some of the primary components of an Event

Management System. Depending on the scope and requirements of the
event, the system can be customized with additional features or
functionalities.

20
FLOW CHART

21
22
23
24
EVENT MANAGEMENT SYSTEM SOURCE CODE

# Event Management System

# Features :

# 1. Create An Event

# 2. View Events

# 3. Book Ticket

# 4. View Ticket

# 5. Condition Check If Customer Already Buy Same Event Ticket

# 6. Condition Check if All Tickets are sold Out.

# 7. Show Overall Event Summary

import pickle #Python pickle module is used for serializing and de-
serializing a Python object structure

import os

import pathlib

Book a Ticket Class

class Ticket:

name = ''
25
 email = ''

event = ''

reference = 200000

def bookTicket(self):

self.name= input("Enter Customer Name: ")

self.email = input("Enter Customer Email: ")

file = pathlib.Path("events.data")

if file.exists():

infile = open('events.data', 'rb')

eventdetails = pickle.load(infile)

self.reference = input("Enter Reference Code(10000 - 50000) : ")

while True:

if int(self.reference) <= 10000:

print("Warning: Please Enter Valid Reference Code")

self.reference = input("Enter Reference Code(10000 - 50000) :

26
")

else:

break

for event in eventdetails:

print("Available Event Code : " + event.eventcode + " Event Name : " +

event.eventname)

infile.close()

self.event = input("Enter Event Code: ")

def check(self):

file = pathlib.Path("tickets.data")

if file.exists():

infile = open('tickets.data', 'rb')

ticketdetails = pickle.load(infile)

for ticket in ticketdetails:

if ticket.email == self.email and ticket.event == self.event:

return True

infile.close()

27
def gettotalticketcount(self):

file = pathlib.Path("events.data")

if file.exists():

infile = open('events.data', 'rb')

eventdetails = pickle.load(infile)

for event in eventdetails:

if event.eventcode == self.event:

return int(event.eventTotalAvaibleSeat)

infile.close

else:

return 0

def getBookedSeatCount(self):

file = pathlib.Path("tickets.data")

28
counter= 0

if file.exists():

infile = open('tickets.data', 'rb')

ticketdetails = pickle.load(infile)

for ticket in ticketdetails:

if ticket.event == self.event:

counter = counter + 1

return int(counter)

return 0

Create Event Class

class Event:

eventname = ''

eventcode = ''

eventTotalAvaibleSeat = 10

def createEvent(self):

self.eventname= input("Enter Event Name: ")

self.eventcode = input("Enter Event Code: ")

29
 self.eventTotalAvaibleSeat = input("Enter Event Total Availble Seats:
")

print("\n\n ------> Event Created!")

Main Program Modules

# Book Ticket and Check Condition

def bookEventTicket():

ticket = Ticket()

ticket.bookTicket()

if ticket.check():

print("Warning : You Already Book A Seat")

elif ticket.getBookedSeatCount() >= ticket.gettotalticketcount():

print("Warning : All Ticket Sold Out")

else:

print("Sucess : Ticket Booked!")

saveTicketDetiails(ticket)

# Save Ticket Detials to File

30
def saveTicketDetiails(ticket):

file = pathlib.Path("tickets.data")

if file.exists():

infile = open('tickets.data', 'rb')

oldlist = pickle.load(infile)

oldlist.append(ticket)

infile.close()

os.remove('tickets.data')

else:

oldlist = [ticket]

outfile = open('tempTicket.data', 'wb')

pickle.dump(oldlist, outfile)

outfile.close()

31
os.rename('tempTicket.data', 'tickets.data')

# Display Saved Ticket Details

def getTicketDetails():

file = pathlib.Path("tickets.data")

if file.exists ():

infile = open('tickets.data','rb')

ticketdetails = pickle.load(infile)

print("---------------TICKET DETAILS---------------------")

print("T-Ref C-Name C-Email E-Code")

for ticket in ticketdetails :

print(ticket.reference,"\t",ticket.name,"\t", ticket.email,
"\t",ticket.event)

infile.close()

print("--------------------------------------------------")

32
 input('Press Enter To Main Menu')

else :

print("NO TICKET RECORDS FOUND")

# Create Event Module

def createEvent():

event = Event()

event.createEvent()

saveEventDetails(event)

# Save Event Details to File

def saveEventDetails(event):

file = pathlib.Path("events.data")

if file.exists():

infile = open('events.data', 'rb')

oldlist = pickle.load(infile)

oldlist.append(event)
33
 infile.close()

os.remove('events.data')

else:

oldlist = [event]

outfile = open('tempevents.data', 'wb')

pickle.dump(oldlist, outfile)

outfile.close()

os.rename('tempevents.data', 'events.data')

# Display All Event Details

def getEventsDetails():

file = pathlib.Path("events.data")

if file.exists ():

infile = open('events.data','rb')

eventdetails = pickle.load(infile)

print("---------------EVENT DETAILS---------------------")

print("E-Name E-Code E-Total-Seats")

for event in eventdetails :

34
 print(event.eventname,"\t", event.eventcode,
"\t",event.eventTotalAvaibleSeat)

infile.close()

print("--------------------------------------------------")

input('Press Enter To Main Menu')

else :

print("NO EVENTS RECORDS FOUND")

# Display Reports About Events

def getEventsSummary():

filetickets = pathlib.Path("tickets.data")

if filetickets.exists():

infiletickets = open('tickets.data', 'rb')

ticketdetails = pickle.load(infiletickets)

fileEvents = pathlib.Path("events.data")

if fileEvents.exists ():

infileEvents = open('events.data','rb')

eventdetails = pickle.load(infileEvents)

35
 print("---------------REPORTS---------------------")

for event in eventdetails :

print("\n\nEvent Name : " + event.eventname + " | Total Seats : " +

event.eventTotalAvaibleSeat + " \n")

for ticket in ticketdetails:

if event.eventcode == ticket.event:

print(ticket.reference, "\t", ticket.name, "\t", ticket.email)

infileEvents.close()

infiletickets.close()

print("--------------------------------------------------")

input('Press Enter To Main Menu')

else :

print("NO EVENTS RECORDS FOUND")

Start Program

ch=''

36
num=0

while ch != 8:

print("\t\t\t\t-----------------------")

print("\t\t\t\tEVENT MANAGEMENT SYSTEM")

print("\t\t\t\t-----------------------")

print("\tMAIN MENU")

print("\t1. BOOK TICKET")

print("\t2. VIEW TICKET")

print("\t3. CREATE EVENTS")

print("\t4. VIEW EVENTS")

print("\t5. SHOW SUMMARY")

print("\tSelect Your Option (1-5) ")

ch = input()

37
if ch == '1':

bookEventTicket()

elif ch == '2':

getTicketDetails()

elif ch == '3':

createEvent()

elif ch == '4':

getEventsDetails()

elif ch == '5':

getEventsSummary()

38
TESTING

1. Types of Testing for an Event Management System

a. Functional Testing

 User Registration and Login

o Test registration process with different types of input (valid, invalid, empty
fields).
o Verify the login functionality with valid and invalid credentials.
o Password recovery and resetting.
 Event Creation
o Test the creation of an event, ensuring fields like event name, date, venue,
and description are correctly saved.
o Verify that only authorized users (e.g., event organizers) can create or
modify events.

 Event Registration
o Test the registration process for attendees.
o Verify that attendee data is being saved correctly, and the event capacity is
managed.
 Ticket Purchase and Payment
o Test the process of ticket purchasing and payment options (if integrated with
a payment gateway).
o Verify the status of the ticket (e.g., reserved, paid).
 Notifications
o Check if event reminders, registration confirmations, and other notifications
are sent to users correctly.

39
b. Non-Functional Testing

 Performance Testing
o Test how the system handles a large number of events and attendees
(stress testing).
o Check response time under high load, such as during a high volume of
registrations.
 Security Testing
o Ensure that sensitive data (user information, payment details) is
encrypted and secure.
o Test for potential vulnerabilities like SQL injection, XSS, etc.
 Usability Testing
o Test the user interface for ease of use.
o Ensure the system is accessible to users with disabilities (WCAG
compliance).
 Compatibility Testing
o Verify that the system works across different devices and browsers.

2. Test Cases for Event Management System

Here are some sample test cases:

Test Case 1: User Registration

 Objective: Verify that the user can register successfully.

 Steps:
1. Open the registration page.
2. Enter valid user details (name, email, password, etc.).
3. Click the "Register" button.
 Expected Result: The system should successfully register the user and display
a confirmation message.

40
Test Case 2: User Login

 Objective: Verify that the user can log in with correct credentials.
 Steps:
1. Open the login page.
2. Enter a valid email and password.
3. Click "Login."
 Expected Result: The user should be redirected to the dashboard or event
listing page.

Test Case 3: Event Creation

 Objective: Verify that an event can be created successfully.

 Steps:
1. Log in as an event organizer.
2. Navigate to the event creation page.
3. Fill in event details (name, date, venue, description, etc.).
4. Click the "Create Event" button.
 Expected Result: The event should be created, and a confirmation message
should appear.

Test Case 4: Event Registration

 Objective: Verify that users can register for an event.

 Steps:
1. Browse available events as an attendee.
2. Select an event.
3. Click the "Register" button.
4. Enter attendee information.
5. Click "Submit."
 Expected Result: The system should successfully register the user for the
event.

41
Test Case 5: Payment Processing

 Objective: Verify that payment processing works correctly for ticket

purchasing.
 Steps:
1. Select an event with a ticket purchase option.
2. Choose a payment method (e.g., credit card, PayPal).
3. Complete the payment.
 Expected Result: The system should process the payment and confirm the
ticket purchase.

3. Automated Testing (Optional)

If your EMS project is large and complex, consider automating some of the testing
procedures:

 Tools for Automated Testing:

o Selenium: For automating web-based tests.
o Junit: For backend testing (if the system has a Java backend).
o Postman: For testing API endpoints, if the system exposes APIs for
event management, registration, etc.

4. Edge Case Testing

Test for edge cases where unexpected or extreme inputs might cause issues:

 Invalid email format during registration.

 Attempting to register for a full event.
 Trying to register for an event after it has ended.
 Handling of special characters in event names and descriptions.

42
5. Error Handling Testing

Ensure that the system gracefully handles errors and displays appropriate error
messages:

 What happens when a user tries to access a non-existing event?

 Error messages for failed payments or registration.
 Timeouts and failed network connections.

6. End-to-End Testing

Once all the individual components are tested, ensure that the entire flow works
together smoothly:

 Test the process from user registration to event creation, event registration,
payment, and ticket confirmation.
 Test on different devices, browsers, and screen sizes.

43
OUTPUT

44
45
46
47
48
49
FUTURE WORK

Manage different organizer profile that you have created for

different types of events. You can also share each one of them with your
contacts on various platforms. Keep a record for each and every attendee
that shows at the event. Search by id or scan via QR code that is sent to the
attendees when their register.

The above mentioned points are the enhancements which can be

done to increase the applicability and usage of the project. Here we can
maintain the records of Event and User. Also, as it can be seen that now-a-
days the players are versatile, i.e. so there is a scope for introducing a
method to maintain the Event Management System. Enhancement can be
done to maintain all the Event, User, Ticket, Booking, Organizer.

We have left all the options open so that if there is any other future
requirement in the system by the user for the enhancement of the system
then it is possible to implement them. In the last we would like to thanks all
the persons involved in the development of the system directly or
indirectly. We hope that the project will serve its purpose for which it is
develop were by underlining success of propose.

50
CONCLUSION

In this paper, The project “Event Management System” has been

designed and tested. Integrating features of all the software components
used have developed it. With the help of growing technology the project
has been successfully implemented. Project will definitely reduce the
human effort and make the task of user, customer and administrator easier.
It is efficient to use easy to work on it. Thus keeping in mind the
advantages and application.

We are developing an Event Management software which as total

management control of customer and effective service of different event.

51
Bibliography and References

 Google for problem solving

 http://www.javaworld.com/javaworld/jw-01-1998/jw-01-
Credentialreview.html
 Database Programming with JDBC and java by O’Reilly
 Head First Java 2nd Edition
 http://www.jdbc-tutorial.com/
 Java and Software Design Concepts by Apress
 https://www.tutorialspoint.com/java/
 http://www.javatpoint.com/java-tutorial
 http://docs.oracle.com/javase/tutorial/
 htttp://www.wampserver.com/en/
 http://www.JSP.net/
 http://www.tutorialspoint.com/mysql/
 httpd.apache.org/docs/2.0/misc/tutorials.html

52