Submitted to

UTKAL UNIVERSITY, VANIVIHAR

Guided By Presented by
Swarupa Senapati (15130V174039)
Mr. P.K Nath, AGM, NALCO
Sunaina Sahoo (15130V174036)
Susmita Pradhan (15130V174037)
Rajendra Behera (15130V174025)
 INTRODUCTION

 We are doing our project on Event Management System. There is the need for
efficient management of a network based system for handling client for
celebrating event, and other functions.

 This project is an endeavor to provide a solution for Event Management .

 The proposed system enables the administrator to keep track of clients

registration , orders(Bookings), maintaining records of the client and service
providers registration. we can view how our application handle the client .

 We can also view the reports generated by him and can also send feedbacks
instantly.
 OBJECTIVES

 Our website is EVENT MANAGEMENT SYSTEM for different types

of events .

 Such as Birthday party, Ring ceremony, wedding and annual functions.

 The client can easily book events and get updates of upcoming events.

 Client can payment paid by credit card or cash.

 Our organization provide many facilities which is Photo Gallery, Sound

system, Assembly hall, Cartoon characters ,Caterers, etc….
 Why we chose Event Management System project ?

 When we prepare for project first we analyze the market requirement

 According to research of market we thought to build a web based application

,which is easily bind event service providers in a chain and those who need
service to celebrate any kind of functions .

 And finally we implement the ideas and named the project Event
Management System.
 REQUIREMENT SPECIFICATION
SOFTWARE REQUIREMENT SPECIFICIATIONS

• OPERATING SYSTEM : WINDOWS 8 .

• LANGUAGE (FRONT END) :C#, . Net 4.0
• SERVER : SQL Server
• WEB TECHNOLOGY :HTML,JAVASCRIPT, CSS.
• DATABASE (BACK END) : SQL Server 2012
• BROWSER : Google Chrome.

HARDWARE REQUIREMENTS SPECIFICATIONS

• PROCESSOR : INTEL 2.0 GHz OR ABOVE

• HARDDISK : 100 GB
• RAM : 512 MB
 PROJECT DESIGN
 This phase transforms the customers requirements as described in the SRS
document into a form that is to be implemented using a programming
language.
 It facilitates the procedural detail necessary for implementation of the system
recommended in the Initial study and Feasibility study.
 This System design process is also referred as Data modelling.

 PRIMARY DESIGN:
Different modules required to implement the design.
Control relationship among the module.
Interface between the module.

 DETAILED DESIGN:
The data structures of the individual module.
Algorithms required to implement the module
 PROJECT MODULES
 The user classes can be divided into three categories..

1. Admin (system)
2. The user
3. The service provider

 Admin:- The admin is protected by user id and password. He can keep track of the customer
and service provider basic information and accordingly can update the system on a regular
basis. As far as the admin is concerned, he has the only task to maintain the system without
any interference with the user and the service provider.

 User:- The user is a client who can register himself in the system and hence gets his/her id
and password ,then he can choose options like selecting the event type and the service
provider. Later she/he can remove himself from the system or can be there for later use.

 Service provider:-The service provider, which is the third module can register himself in the
system hence can be selected by the clients for the intended service.
 DATA FLOW DIAGRAM

 A DFD is a hierarchical graphical model of a system that shows the different

processing activities or functions that the system performs and the data interchange
among those functions.
 DFD model represents only the data flow aspects.

 It does not show sequence of execution of the different functions

and the conditions based on which a function may or may not be
executed..
 It completely ignores the aspects such as control flow and some specific algorithm
used by the functions
DFD (level 0) or CONTEXT DIAGRAM
LEVEL 1 DFD
LEVEL 2 DFD
USE CASE DIAGRAM
FLOW CHART
E-R DIAGRAM
CLASS DIAGRAM
 SCREEN SHOTS
HOME PAGE

This is our home page in Event Management System which is the common layout in every
pages i.e this page will be shown in every pages.
In this page , if a client want to book any event then he/she will be click to
online reserve.
GALLERY PAGE

This page will be show the different type of functions like birth day
party , marriage anniversary , annual function etc…
ORDER DETAILS PAGE

In this page , a client give detailed information about ordered

events.
SERVICE REGISTER PAGE

Service provider will be register here.

CONTACT PAGE
PROFILE PAGE

In this page shows the detailed information who is register there.

LOGIN PAGE

In this page , admin login here using reg no and password.

REGISTER PAGE

Here client will be give the detailed information about ordering the events.
CONCLUSION

 With great privilege and pleasure we submit here with full satisfaction the project entitled
EVENT MANAGEMENT SYSTEM.

 The project was successfully completed within the time span allotted. Every effort has been
made to present the system in more users-friendly manner.

 We hope all the disadvantages of the existing system have been overcome using the present
system of EVENT MANAGEMENT SYSTEM ,which has been successfully implemented at client's
location.

 All the modules are tested separately and put together to form the main system. Finally the
system is tested with real data and everything worked successfully. Thus the system has
fulfilled the entire objective identified.

 The system has been developed in an attractive dialogs fashion and the entire user interface
is attractive and user friendly .

 So user with minimum knowledge about the computers and the system can easily work with
the system.
FUTURE SCOPE

We can 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
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.
 BIBILOGRAPHY

1. Microsoft Visual C# .NET 2010 MARK SHMIDT

2. SQL Server 2008 Black Book
PATRICK DALTON
PAUL WHITEHEAD Websites
3. http://www.tutorials.com