1Sanket Arun Bucche 2Professor name

1PG Student, 2Assistant Professor

1,2Department of Computer Application

1,2G.H.Raisoni University, Amravati, India

Abstract : 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).
CHAPTER 1
INTRODUCTION 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.
• 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.

CHAPTER 2
SYSTEM ANALYSIS
2.1 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 provide
tracking 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.
2.2 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

2.3 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, place, and number of
guest, date, food type, food and total bill of event. We can also take feedback from
customers.
2.3.1 FEATURES
• Customer Registration/Login.
• Admin Login.
• Event Selection (user can select type of event).
• Event equipment selection.
• Food package selection.
2.3.2 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.
• Time consuming process.

CHAPTER 3
 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.
3.1 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
3.2 SOFTWARE REQUIREMENTS
• Operating System supports Windows 10
• C SHARP(C#)
• SQL Server 2017
• Microsoft Visual Studio 2017
3.3 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.
3.4 MICROSOFT VISUAL STUDIO 2017
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It
is used to develop computer programs, as well as websites, web apps, web services and
mobile apps. Visual Studio uses Microsoft software development platforms such as Windows
API, Windows Forms, Windows Presentation Foundation, Windows Store and Microsoft
Silver light. It can produce both native code and managed code.
Visual Studio includes a code editor supporting IntelliSense (the code completion
component) as well as code refactoring. The integrated debugger works as a source-level
debugger and a machine-level debugger. Other built-in tools include a code profiler, designer
for building GUI applications, web designer, class designer, and database schema designer. It
accepts plug-ins that enhances the functionality at almost every level-including adding
support for source control systems.
Visual studio supports 36 different programming languages and allows the code editor and
debugger to support (to varying degrees) nearly any programming languages, provided a
language- specific service exists. Built-in languages include C, C++, Visual Basic .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.
CHAPTER 4
SYSTEM DESIGN
Design is the first step in development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization. Once the software requirement have been analyzed and specified the software
design involves three technical activities-Design, Coding, Implementation, Testing that are
required to build and verify the software. The design activities are of main importance in this
phase, because in these activities decisions ultimately affecting the success of the software
implementation and its ease of maintenance are made. This decision has the final bearing
upon reliability and maintainability of the system. Design is only way to accurately transfer
the customer’s requirements into finished software or system .Design is the place where
quality is fostered in development. Software design is the process through which
requirements are translated into a representation of software. Software requirement is
conducted in two steps. Preliminary design is concerned with the transformation of
requirements into data.

4.1 DATABASE DESIGN

Database design is the organization of data according to a database model. The designer
determines what data must be stored and how the data elements interrelate. With this
information, they can begin to fit the data to the database model.

Database design is the organization of data according to a database model. The designer
determines what data must be stored and how the data elements interrelate. With this
information, they can begin to fit the data to the database model. Database design involves
classifying data and identifying interrelationships.
A database is an organized mechanism that has the capability of storing information through
which a user can retrieve stored information in an effective and efficient manner. The data is
the purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements are gathered
together and a database is designed which will meet these requirements as clearly as possible.
This step is called Information Level Design and it is taken independent of any individual
DBMS.
In the second step, this Information level design is transferred into a design for the
specific DBMS that will be used to implement the system in question. This step is called
Physical Level Design, concerned with the characteristics of the specific DBMS that will be
used. A database design runs parallel with the system design. The organization of the data in
the database is aimed to achieve the following two major objectives.
• Data Integrity
• Data independence

Normalization is the process of decomposing the attributes in an application, which

results in a set of tables with very simple structure. The purpose of normalization is to
make tables as simple as possible. Normalization is carried out in this system for the
 following reasons.
• To structure the data so that there is no repetition of data , this
helps in
• Saving.
• To permit simple retrieval of data in response to query and
report request.
• To simplify the maintenance of the data through updates,
insertions,
• Deletions.
• To reduce the need to restructure or reorganize data which new
application
• Requirements arise.

4.1.1 SCHEMA DIAGRAM

In a schema diagram, all database tables are designated with unique columns and special
features, e.g., primary/foreign keys or not null, etc. Formats and symbols for expression are
universally understood, eliminating the possibility of confusion. The table relationships also
are expressed via a parent table’s primary key lines when joined with the child table’s
corresponding foreign keys.
Schema diagrams have an important function because they force database developers to
transpose ideas to paper. This provides an overview of the entire database, while facilitating
future database administrator work.

Figure 4.1 Schema Diagram

4.1.2 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

Figure 4.2 E R Diagram

4.1.3 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 4.3 Zero-Level DFD

CHAPTER 5
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.

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.

5.1 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.
• 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.
 Figure 5.1 Reuse Oriented Model

5.2 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 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

CHAPTER 6
TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality
of components, sub-assemblies, assemblies and/or a finished product it is the process of
exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
6.1 UNIT TESTING
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches
and internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests
perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.
6.2 INTEGRATION TESTING
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components
were individually satisfaction, as shown by successfully unit testing, the combination of
components is correct and consistent. Integration testing is specifically aimed at exposing
the problems that arise from the combination of components.
6.3 SYSTEM TESTING
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
6.4 VALIDATION TESTING
Validation testing is a concern which overlaps with integration testing ensuring that the
application fulfils its specification, is a major criterion of integration testing. Validations
testing also overlaps to a large extend with system testing, where the application is tested
with respect to its typical working environment.
Consequently for many processes no clear division between validation and system testing can
be made validation testing.

Specific tests can be performed in either or both stages include the following:
• Regression Testing
• Recovery Testing
• Security Testing
• Stress Testing
• Performance Testing
6.5 ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

CHAPTER 7
SNAP SHOTS
7.1 LOGIN PAGE

Snapshot 1: Login Portal

• This Page is used for Login purpose both for Admin and also for the
new or for the customer who have registered already

7.2 CUSTOMER HOME PAGE

Snapshot 2: Customer Home Page
• This page is used Exclusively for the Customer where he can do
various tasks like booking an event, view the available venue, and give feedback
about the experience.
7.3 BOOK EVENT PAGE
Snapshot: 3 Book Event Page
 • This page is used for the customer where he can book an event of his
own kind and can see the available facilities.
7.4 VIEW EVENT VENUE PAGE
Snapshot: 4 View Event Venue Page
• This page is used to view the venues available for the event.
7.5 FEEDBACK PAGE
Snapshot: 5 Feedback Page
• This page is used to give the feedback of their experience about the
booking process.

7.6 ADMIN HOME PAGE

Snapshot: 6 Admin Home Page
• This is the page where the admin can edit the events and venues and
view the feedback of the customer.

7.7 BOOKING HISTORY PAGE

Snapshot: 7 Booking History Page

• This page is used to view the booking history of the customer.

7.8ADD VENUE PAGE
Snapshot: 8 Add Venue Page
• This page is used to for the admin to add or edit the venues and its
related data.
7.9 VIEW FEEDBACK PAGE
Snapshot: 9 View Feedbacks Page
• This page is used to view the feedbacks of the customers.
CONCLUSION
In this project we have created one application which is easy to access and user friendly. The
application keeps a backup of the events data which includes the details of all the events.
Event management is a glamorous and exciting profession which demands a lot of hard work
and dynamism. As the name suggests, it means conceptualizing, planning, organizing and
finally executing an event. The event could be of any type-marriage, birthday parties,
farewell, anniversary etc. It offers enormous scope for ambitious young people.
Event management is an area that is growing rapidly, and is expected to have a better growth
rate in the next decade.
• The system will not give online help but used to access the data offline.
• It reduces the work load of the Organizer or the manager who manages
an event.
 FUTURE ENHANCEMENT
Previously, data used to be inserted manually to book an event. But, currently the project
supports to fetch all the data related to events. The future is quite bright for the system. It has
to reach all the computer devices. It can also be used to access through Internet.
• Event management is a process of organizing a professional and
focused event for a particular target audience.
• It involves visualizing concepts, budgeting, planning, organizing and
executing events like musical concerts, marriages, fashion shows, seminars,
exhibitions, theme parties, product launches, etc.
• Event management is becoming a very popular profession there are not
too many options for a degree course however, you can go in for a diploma course for
the same. Amongst the most common courses are the 6 months training course in
event management.
• The reputed and popular institutes providing these courses generally tie
up with event management.

REFERENCES
• Chapter 5 that is Testing part is taken from textbook Software
Engineering by author IAN SOMMERVILLE, of 7th Edition.
• Web references.
• www.wikipedia.com
• www.google.com
• www.mysql.tutorials.org