ADOCUE
Project Report
on
“Event Management System”
DEVELOPED BY :
Name-PATEL ARYA MAULIKKUMAR ER-
22171341073
Diploma Computer Engineering
Sem: 5th
page 1
ADOCUE
Certificate
This is to certify that the following set of students
of Diploma in Computer Engineering 5th Semester
Name:Patel Arya Maulikkumar Enrollment
No:22171341073
Have completed documentation and design of the project on
"Event management syatem” for the fulfillment of the
requirement of a major project as defined by “The Institute
of Technology” in the academic year 2023.
( Signature of Project Guide )
( Signature of H.O.D)
page 2
CHAPTER-1
PROBLEM IDENTIFICATION DEFINITION &
MODIFICATION
1. ABSTRACT OF THE PROJECT AND OVERVIEW OF THE PROBLEM
2. EXISTING SYSTEM
3. PROJECT PROFILE
4. TECHNOLOGY OVERVIEW
CHAPTER-2
SYSTEM REQUIREMENT SPECIFICATION
1. REQUIREMENT GATHERING AND ANALYSIS
2. FEASIBILITY STUDY
CHAPTER-3
PROBLEM SOLUTION OUTLINE
1. MODULES DESCRIPTION
2. DATA DICTIONARY
3. ENTITY-RELATIONSHIP DIAGRAM
4. DATA FLOW DIAGRAM
5. ACTIVITY DIAGRAM
6. USE CASE DIAGRAM
CHAPTER
1.Example Of Pages
page 3
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, birthday celebrations, theme parties,
etc. Event management is the application of project management to the creation and
development of large scale events. The process of planning and coordinating the event is
usually referred to as event planning and which can include budgeting, scheduling, site
selection, acquiring necessary permits, coordinating transportation and parking, arranging for
speakers or entertainers, arranging decor, event security, catering, coordinating with third
party vendors, and emergency plans. An event refers to a social gathering or activity, such as
a festival,( for example a musical festival), a ceremony( for example a marriage ) and a
party(for example a birthday party).
This project is based on event management system. It is used to manage all the activity
related to event. In any event any services providers work simultaneously and it is very hard
to mange this providers. It is also important for event organizer that he has all the contacts
details of these service providers so that he can contact them any time to plan an event at
given time. To manage all these activity the proposed system is developed. To get success in
the event management business, user should have strong network of service providers like
sound system services, lighting providers, canteen services, stage construction and so on.
1.1 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.
page 4
CHAPTER-1
ABSTRACT
Book My Event is an online website for online event management system
booking on date and time basis, in order to better facilitate meetings family
functions and cultural events etc. This website helps any authorized person to
book the halls from internet and it also shows the availability of a particular
hall at the chosen time and date. This website also handles various device
booking such as food catering, audio system, lightening, video recording etc.
this project is aimed to help users manage various events throughout the year.
It serves same as the functionality of an event manager. This project provides
most of the functionality required for an event. Our main aim of this project is
to provide an ideal solution to book events
EXISTING SYSTEM
This existing system is not providing secure registration and profile
management of all the users properly. This system is not providing on-
line help.
This system doesn’t providetracking of users activities and their progress.
This manual system gives us very less security for saving data and some
data may be lost due to mismanagement. This system is not providing
proper events information. The system is giving manual information
through the event management executer. In present system Event
Company has to do all management work manually. They keep all
payment information on papers. The present system will help to check
the past expenses on any event.
page 5
PROPOSED SYSTEM
Event Management System is an event management software project that
serves the functionality of an event manager. The system allows only
registered users to login and new users are allowed to register on the
application. This is a desktop application but web application of the same
application is also available. The project provides most of the basic
functionality required for an event. It allows the user to select from a list
of event types. Once the user enters an event type (e.g. Marriage,
Birthday parties etc), the system then allows the user to select the date
and time of event, place and the event equipment’s. All this data is
logged in the database and the user is setting up his username and
password while registering. The data is then sent to the administrator
(website owner) and they may interact with the client as per his
requirements and his contact data stored in the database
OBJECTIVES OF PROPOSED SYSTEM
The main objective of the project on Event Management System is to
manage the details of Event, Activity, Organizers, Attendees, and
Conductors. It manages all the information about Event, Payments, and
Conductors. 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 activity, Payment, Organizers. In event management
system which is developed in C#, we can manage all events using this
project. In this project we can add venue data like name, address, phone,
capacity, preferred for events and fees. Also we can book event type,
page 6
place, and number of guest, date, food type, food and total bill of event.
We can also take feedback from customers.
FEATURES
Customer Registration/Login.
Admin Login.
Event Selection (user can select type of event).
Event equipment selection.
Food package selection.
ADVANTAGES
The system is useful as it calculates an exact cost for all the resources
required during the event.
The user gets all the resources at a single place instead of wandering
around for these.
This system is effective and saves time and cost of the users.
Insert, delete and updating of records is improved which results in proper
resource management of Event data.
Manages the information of event activity
.
DISADVANTAGES
Lot of paper work required.
Man power was more.
Key Components of overview
page 7
1. Planning: Identifying the purpose, objectives, and scope of the
event. This includes setting a timeline, budget, and target
audience.
2. Budgeting: Estimating costs for all aspects of the event,
including venue, catering, entertainment, marketing, and more.
It also involves managing expenses and ensuring the event
remains within budget.
3. Venue Selection: Choosing an appropriate location based on
the event type, size, and logistical needs. This includes
negotiating contracts and understanding venue policies.
4. Logistics: Coordinating all logistical aspects such as
transportation, accommodation, equipment rentals, and on-site
management.
5. Marketing and Promotion: Developing a marketing strategy to
promote the event, using tools like social media, email
marketing, and traditional advertising to attract attendees.
6. Coordination: Working with vendors, suppliers, and staff to
ensure everything runs smoothly before, during, and after the
event.
7. Execution: Overseeing the event on the day, managing
schedules, troubleshooting issues, and ensuring that everything
aligns with the plan.
8. Post-Event Evaluation: Assessing the event's success through
feedback from attendees and stakeholders, reviewing what
worked and what didn’t, and compiling reports for future
improvements.
Skills Required
Organizational Skills: Keeping track of multiple elements and
timelines.
Communication: Effectively interacting with clients, vendors,
and attendees.
Problem-Solving: Quickly addressing any issues that arise.
Negotiation: Securing the best deals with vendors and venues.
Creativity: Designing unique experiences that meet client
goals.
page 8
Types of Events
Corporate Events: Meetings, conferences, seminars,
and team-building activities.
Social Events: Weddings, parties, and family gatherings.
Public Events: Festivals, concerts, and community
gatherings.
Trends in Event Management
Sustainability: Focusing on eco-friendly practices and reducing
waste.
Technology Integration: Using apps, virtual reality, and live
streaming to enhance attendee experiences.
Personalization: Tailoring experiences to meet individual
attendee preferences.
page 9
CHAPTER-2
SYSTEM REQUIREMENT SPECIFICATION
The System Requirements Specification is produced at the culmination of
the analysis task. The function and performance allocated to software as
part of system engineering are refined by establishing a complete
information description, a detailed functional and behavioral description,
an indication of performance requirements and design constraints,
appropriate validation criteria, and other data pertinent to requirements.
HARDWARE REQUIREMENTS
Processor: Any new generation processor
RAM: Reasonable for the processor
Hard Disk Drive: More than 512 MB
Key Board: Standard Keyboard
Monitor: Any color monitor
Display Adapters: Super Video Graphics Array(VGA)
Mouse: Optical mouse
SOFTWARE REQUIREMENTS
Operating System supports Windows 10
C SHARP(C#)
SQL Server 2017
Microsoft Visual Studio 2017
page 10
SQL (STANDARDIZED QUERY LANGUAGE)
Microsoft SQL Server is a set of components that work together to meet
the data storage and analysis needs of the largest web sites and enterprise
data processing systems.
SQL Server 2005 Express Edition is free, easy-to-use, and
redistributable version of SQL Server 2005 that offers developers a
robust database for building reliable applications.
SQL Server Express can make use of only 1 GB of RAM. In addition it
has a database size limit of 4 GB, which limit its use for larger business
applications.
SQL Server 2005 Express Edition is primarily targeted to developers
looking to embed a redistributed database engine in their application.
This developers no longer need to develop their own data repository and
can rely on the powerful set of features, performance and the well define
T-SQL programming language offered by SQL Server Express.
Microsoft SQL Server 2000 data is stored in databases. The data in a
database is organized into the logical components visible to users. A
database is also physically implemented as two or more files on disk.
.NET, C#, F#, JavaScript, Typescript, XML, XSLT, HTML, and CSS.
Support for other languages such as Python, Ruby, Node.js, and M among
others is available via plug-ins.
Feasibility Study
Executive Summary
page 11
Event Overview: Briefly describe the event, including its
purpose, type (e.g., conference, festival, wedding), and target
audience.
Objectives: State the primary goals of the event (e.g.,
networking, fundraising, entertainment).
Market Research
Target Audience:
o Define demographic details (age, gender, location).
o Identify psychographics (interests, preferences).
Competitor Analysis:
o Research similar events in the area.
o Analyze their attendance, pricing, strengths, and weaknesses.
Demand Assessment:
o Conduct surveys or interviews to gauge interest.
o Use social media polls or focus groups for qualitative insights.
Technical Feasibility
Location:
o Evaluate potential venues based on size, facilities, accessibility,
and cost.
Logistics:
o Assess transportation options and parking availability.
o Plan for on-site needs like catering, security, and first aid.
Technology:
o Identify requirements for sound, lighting, and audiovisual
equipment.
o Consider ticketing solutions and event management software.
Financial Feasibility
Budgeting:
page 12
o Create a detailed budget including all potential costs (venue
rental, catering, marketing, permits).
Revenue Sources:
o Estimate ticket sales, sponsorships, vendor fees, and merchandise
sales.
Break-even Analysis:
o Calculate the minimum number of attendees needed to cover
costs.
Operational Feasibility
Staffing:
o Determine the number of staff and volunteers needed.
o Define roles and responsibilities (event coordinator, marketing
team, on-site staff).
Timeline:
o Develop a timeline with key milestones (planning phases,
promotional activities).
Regulatory Requirements:
o Research necessary permits, insurance, and health regulations.
Marketing Strategy
Promotion Plan:
o Outline marketing channels (social media, email, local media).
o Plan partnerships with local businesses or influencers.
Branding:
o Develop a cohesive brand identity (logo, theme, messaging).
Risk Analysis
Identify Risks:
o Consider factors such as weather, venue issues, and low ticket
sales.
page 13
Mitigation Strategies:
o Develop contingency plans for each identified risk.
Conclusion and Recommendations
Summary of Findings:
o Recap the feasibility results based on market, financial, and
operational analyses.
Recommendations:
o Provide clear advice on whether to proceed, modify, or abandon
the event concept.
Additional Considerations
Feedback Mechanism: Plan for post-event surveys to gather insights for
future improvements.
CHAPTER-3
IMPLEMENTATION
Implementation is the stage of the project where theoretical design is turned
into a working system. At this stage the main workload and the major impact on
the existing system shifts to the user department. If the implementation is not
carefully planned and controlled, it can cause chaos and confusion.
page 14
Implementation phase is less creative than design phase. Implementation
includes all those activities that take place to convert from the old system to
new system. The new system may be totally new, replacing an existing manual
on an automated system. It may be a major modification to an existing system.
In either case, proper implementation is essential to provide liable system to
meet the organizational requirements.
The implementation requires the following tasks.
Careful planning.
Investigation of the system and constraints.
Design of methods to achieve the changeover.
Evaluation of changeover method.
REUSE ORIENTED MODEL
The reuse-oriented model, also called reuse-oriented development
(ROD), is a method of software development in which a program is
refined by producing a sequence of prototypes called models, each of
which is automatically derived from the preceding one according to a
sequence of defined rules.
The reuse-oriented model can reduce the overall cost of software
development compared with more tedious manual methods. It can also
save time because each phase of the process builds on the previous phase
which has already been refined. When carefully carried out, ROD can
minimize the likelihood of errors or bugs making their way into the final
product.
page 15
The reuse-oriented model is not always practical in its pure form because
a full repertoire of reusable components may not be available. In such
instances, some new program components must be designed. If not
thoughtfully done, ROD can lead to compromises in perceived
requirements, resulting in a product that does not fully meet the needs of
its intended users.
Modules Description
The system after careful analysis has been identified to be presented with the
following modules. Event Management System is a two modules project. The
modules in the project are: Customer Module and Administrator Module
.
Customer module: Beside login and logout, Customer module includes
features such as new customers has to register before logging in .After
page 16
login customers can book event , give feedback and view venues.
Customer can select the type of event, place, food type and equipments .
Figure 5.1.1 Customer Module
Administrator Module: This module handles adding venues, viewing the
booked events and admin can view the feedback given by the customer. Admin can
update, delete and reset the venue.
Figure 5.1.2 Administrator Module
DATA DICTIONARY
page 17
Entity: Event
Description: Represents an event to be managed in the system.
Attributes:
o Event_ID (Primary Key): Unique identifier for the event.
o Event_Name: Name of the event (e.g., "Annual Conference").
o Event_Type: Type of the event (e.g., "Conference",
"Wedding", "Concert").
o Start_Date: The start date and time of the event.
o End_Date: The end date and time of the event.
o Venue_ID (Foreign Key): Reference to the venue where the
event is being held.
o Description: A brief description of the event.
o Status: Current status of the event (e.g., "Scheduled",
"Completed", "Cancelled").
o Organizer_ID (Foreign Key): Reference to the organizer
managing the event.
Entity: Venue
Description: Represents the location or venue where an event is held.
Attributes:
o Venue_ID (Primary Key): Unique identifier for the venue.
page 18
o Venue_Name: Name of the venue (e.g., "Grand Ballroom").
o Venue_Type: Type of venue (e.g., "Hotel", "Convention
Center").
o Capacity: The maximum number of attendees the venue can
accommodate.
o Location: Physical address of the venue.
o Availability: Indicates if the venue is available (e.g.,
"Available", "Booked").
Entity: Attendee
Description: Represents an individual attending an event.
Attributes:
o Attendee_ID (Primary Key): Unique identifier for the
attendee.
o First_Name: First name of the attendee.
o Last_Name: Last name of the attendee.
o Email: Email address of the attendee.
o Phone_Number: Contact number of the attendee.
o Event_ID (Foreign Key): Reference to the event the attendee is
attending.
o Ticket_Type: The type of ticket (e.g., "VIP", "Regular",
"Student").
o Registration_Date: Date the attendee registered for the event.
page 19
Entity: Organizer
Description: Represents the person or organization responsible for
organizing the event.
Attributes:
o Organizer_ID (Primary Key): Unique identifier for the
organizer.
o Name: Name of the organizer (e.g., "XYZ Events
Management").
o Contact_Info: Contact information (e.g., email, phone
number).
o Event_ID (Foreign Key): Reference to the events organized by
this organizer.
Entity: Speaker
Description: Represents the speakers or presenters in the event.
Attributes:
o Speaker_ID (Primary Key): Unique identifier for the speaker.
o First_Name: First name of the speaker.
o Last_Name: Last name of the speaker.
o Biography: A brief biography or introduction of the speaker.
o Event_ID (Foreign Key): Reference to the event the speaker is
associated with.
page 20
o Session_ID (Foreign Key): Reference to the session the speaker
is conducting.
Entity: Session
Description: Represents individual sessions during the event (e.g.,
workshops, keynotes).
Attributes:
o Session_ID (Primary Key): Unique identifier for the session.
o Session_Title: Title of the session.
o Speaker_ID (Foreign Key): Reference to the speaker
conducting the session.
o Start_Time: Start time of the session.
o End_Time: End time of the session.
o Room_Number: The room or hall number where the session is
being held.
o Event_ID (Foreign Key): Reference to the event in which the
session is happening.
Entity: Ticket
Description: Represents a ticket purchased for the event.
Attributes:
o Ticket_ID (Primary Key): Unique identifier for the ticket.
o Ticket_Type: Type of ticket (e.g., "VIP", "Regular").
o Price: The price of the ticket.
page 21
o Attendee_ID (Foreign Key): Reference to the attendee who
purchased the ticket.
o Event_ID (Foreign Key): Reference to the event the ticket is
for.
o Purchase_Date: Date when the ticket was purchased.
o Status: Ticket status (e.g., "Paid", "Cancelled").
Entity: Payment
Description: Represents a payment transaction for the event.
Attributes:
o Payment_ID (Primary Key): Unique identifier for the
payment.
o Attendee_ID (Foreign Key): Reference to the attendee making
the payment.
o Ticket_ID (Foreign Key): Reference to the ticket associated
with the payment.
o Amount: Amount paid.
o Payment_Date: Date when the payment was made.
o Payment_Method: Method of payment (e.g., "Credit Card",
"Cash").
o Payment_Status: Status of the payment (e.g., "Completed",
"Pending").
Entity: Sponsor
page 22
Description: Represents the organizations sponsoring the event.
Attributes:
o Sponsor_ID (Primary Key): Unique identifier for the sponsor.
o Sponsor_Name: Name of the sponsor.
o Contact_Info: Contact information for the sponsor.
o Amount_Contributed: Amount the sponsor has contributed to
the event.
o Event_ID (Foreign Key): Reference to the event sponsored.
Entity: Event Feedback
Description: Represents feedback provided by attendees about the
event.
Attributes:
o Feedback_ID (Primary Key): Unique identifier for the
feedback.
o Attendee_ID (Foreign Key): Reference to the attendee
providing the feedback.
o Event_ID (Foreign Key): Reference to the event being
reviewed.
o Rating: Rating given by the attendee (e.g., 1-5 stars).
o Comments: Text feedback from the attendee.
o Submission_Date: Date when the feedback was submitted.
Relationships between Entities:
page 23
Event has one-to-many relationships with Attendee, Session, Ticket,
Sponsor, and Event Feedback.
Attendee can register for one or more Events, and each Attendee has
one or more Tickets.
Organizer manages one or more Events.
Speaker can be associated with one or more Sessions, which are part
of an Event.
Session can be associated with one Speaker and can be scheduled in a
specific Room within the event.
page 24
CHAPTER-4
DATA FLOW DIAGRAM
A data-flow diagram (DFD) is a way of representing a flow of a data of a
process or a system (usually an information system). The DFD also provides
information about the outputs and inputs of each entity and the process itself. A
data-flow diagram has no control flow there are no decision rules and no loops.
Specific operations based on the data can be represented by a flowchart.
Figure simple Zero-Level DFD
page 25
page 26
First Davel DFD Diyagram for user
Email & Check
USER Password 1.0 Login User
Login View Login
Successfully Login Information
Select Select time
2.0 Time &
venue
View venue Order Confirm date
date
Make Select Payment
Payment 3.0 Mode Payment
Confirm
View Payment Payment
Payment
Record
Select Report Feedback form
Type 4.0 form
Report
FLOW CHART
page 27
page 28
ENTITY RELATIONSHIP DIAGRAM
An Entity Relationship Diagram (ERD) is a graphical tool to express the overall
structure of a database. It is based on a perception of a real world which
consists of a set of basic objects. An entity is a person, place, thong or event of
interest to the organization and about which data are captured, stored or
processed. The attributes are various kinds of data that describes an entity. An
association of several entities in an Entity-Relationship model is called
relationship
page 29
Activity diayagram
login
Ragister event
Spcify requirement
Send mail
Send mail to event
organizaer
reject
Admin
issuesrequested
Send mail/sms to organizers
about status of event
page 30
Use case diayagram
page 31
CHAPTER-5
CONCLUSION
An Online Event Management System (OEMS) plays a crucial role in the
efficient planning, organization, and execution of virtual or hybrid events.
With the increasing shift towards online platforms, especially in the post-
pandemic era, this system provides the necessary tools to handle various
aspects of event management from registration to post-event analysis.
Key Benefits of an Online Event Management System:
1. Streamlined Event Planning: OEMS automates many of the
traditionally manual tasks such as event registration, ticketing,
scheduling, and attendee management. This reduces the time and
effort required by organizers and allows them to focus on other
important aspects of event execution.
2. Enhanced Attendee Experience: The system offers a seamless and
engaging experience for attendees. From easy online registration and
instant access to event details to personalized schedules and real-time
updates, attendees benefit from a smoother journey from start to
finish.
3. Cost and Time Efficiency: By leveraging digital platforms for event
management, organizers save on logistical costs (e.g., printing
materials, venue rentals) and reduce the time spent on manual
processes. This allows for more efficient resource allocation.
4. Real-Time Communication and Engagement: Through integrated
communication tools, organizers can interact with attendees, speakers,
sponsors, and other stakeholders in real-time. Features such as live
chats, webinars, Q&A sessions, and polls help keep attendees engaged
throughout the event.
page 32
5. Data and Analytics: OEMS provides valuable data and insights, such as
registration trends, payment processing, attendee behavior, and post-
event feedback. These analytics enable organizers to measure event
success, improve decision-making, and plan future events more
effectively.
6. Flexibility and Scalability: Online event platforms can scale to
accommodate events of varying sizes, from small webinars to large
virtual conferences. The flexibility of the system allows it to be
customized for different event formats, including live streaming, on-
demand content, networking sessions, and more.
7. Global Reach: With an online format, events are no longer limited by
geographical boundaries. This makes it easier for organizers to attract
a global audience, increase participation, and expand brand visibility,
as anyone with internet access can join.
8. Increased Sponsorship Opportunities: Online events offer greater
visibility to sponsors. OEMS can integrate virtual sponsor booths,
branding placements, and other promotional features that help
sponsors connect with attendees in meaningful ways.
Challenges and Considerations:
Technology Dependency: Online events rely heavily on technology,
which can lead to challenges like connectivity issues or platform
limitations. Organizers must ensure their chosen platform supports all
event requirements and provides a smooth experience for both hosts
and attendees.
Engagement and Networking: While online events offer convenience,
they can sometimes lack the personal interactions and networking
opportunities of in-person events. It’s important for OEMS to include
features that facilitate virtual networking, such as chat rooms,
matchmaking, and one-on-one video calls.
Security and Privacy: Ensuring data security and protecting attendees'
privacy are critical when hosting events online. Event organizers must
page 33
use secure platforms and adhere to privacy regulations to build trust
with their audience.
Final Thoughts:
An Online Event Management System is an essential tool for anyone
organizing virtual or hybrid events in today’s digital-first world. It offers
numerous benefits, such as improving operational efficiency, enhancing the
attendee experience, and providing actionable data insights. By leveraging
these systems, event organizers can ensure smoother planning, better
engagement, and more successful events, while also adapting to the growing
demand for online and remote experiences.
Ultimately, an OEMS enhances the scalability, reach, and impact of events,
making them more accessible, cost-effective, and efficient, while helping
organizers and attendees navigate the increasingly digital landscape of
modern events.
FUTURE DEVLOPMENT
The Future Scope of Online Event Management Systems (OEMS) includes
several key advancements that will enhance event planning and attendee
engagement:
1. AI Integration: Personalized recommendations, AI-driven
matchmaking for networking, and automated customer support.
2. VR/AR Experiences: Immersive environments and virtual venues for
a more engaging attendee experience.
3. Advanced Networking: AI-powered attendee matchmaking, virtual
business cards, and interactive breakout rooms.
4. Gamification: Interactive games, challenges, and reward systems to
increase attendee participation.
5. Third-Party Integrations: Seamless integration with CRM,
marketing tools, and cross-platform services.
page 34
6. Blockchain: Secure ticketing, smart contracts, and transparent
transactions.
7. 5G & Enhanced Streaming: High-quality streaming, real-time
collaboration, and low-latency communications.
8. Security: Multi-factor authentication, encrypted communications,
and identity verification for secure participation.
9. Sustainability: Green events with virtual alternatives and carbon
offset programs.
10.Post-Event Engagement: On-demand content access and continued
attendee interaction.
11.Hybrid Event Support: Seamless integration of physical and virtual
event components, with multilingual support.
page 35