Tribhuvan University

Faculty Of Humanities & Social Sciences

EVENT MANAGEMENT

A PROJECT REPORT
Submitted to
Department of computer application

Nepathya College

In partial fulfillment of the requirements for the Bachelor’s in Computer

Application

Submitted by
Sandip Paudel

Contents
Chapter 1....................................................................................................................................................2
Introduction................................................................................................................................................2
1.1. Overview.....................................................................................................................................2
1.2. Statement of Problem..................................................................................................................3
1.3. Objectives....................................................................................................................................3
1.4. Scopes.........................................................................................................................................3
Chapter 2....................................................................................................................................................4
REQUIREMENT ANALYSIS..................................................................................................................4
2. Background Study..............................................................................................................................4
2.1. Literature Review.............................................................................................................................4
i. HamroBazar.com................................................................................................................................4
ii. Aduera................................................................................................................................................4
Requirements Determination.................................................................................................................5
2.2. Functional requirements..............................................................................................................5
2.3. Non functional requirements.......................................................................................................5
2.4. Feasibility Analysis:.........................................................................................................................5
2.4.1. Technical feasibility:................................................................................................................5
2.4.2. Operational feasibility:............................................................................................................5
2.4.3. Economic feasibility:...............................................................................................................6
2.4.4. Schedule Feasibility:................................................................................................................6
2.5. Tools and Technologies...................................................................................................................6
2.5.1. Implementation tools................................................................................................................6
Chapter 3....................................................................................................................................................7
METHODOLOGY..................................................................................................................................7

Chapter 1

Introduction

1.1.Overview

An event may be considered as a display of some events in which some guests or participants
are invited for a particular time span. Events can be classified as different types like
cultural celebrations, Business events like conferences and product launch and
promotions, wedding ceremony, college events and so on. Coming to an Event
management System it may be regarded as a platform to manage events for event
managers and portal for participants. Ethically managing an event involves
identification of budget, analysis of cost and post event analysis and feedbacks. Our
project is an online event management system or rather a portal in the form of a website,
a portal that will help in the functionality of an event organizer as well as participants
and stakeholders of the event. The project gives most of the basic requirements for an
event .It provides the user a choice to select from list of event categorized under
different genre. To understand use of this online portal consider the flow of actions that
 takes place : By this application user can register the students for participating, after
registering user can login, after login one can track event details like participant’s name,
contact details, postal address, venue, date and time of the event, expenditures and
revenue of events etc. Registration data is directly accessed and checked by event
manager to arrange things accordingly with the help of site administrator. It will surely
help the organizers and marketing team of the event to promote the events digitally and
increase the registrations and participations .

1.2. Statement of Problem

• Obsolete Content:
In their current website, most of the contents are outdated because it is a static site and the
content cannot be changed without changing the code. So, it is not possible to change the
content without the help of developer nor is it practical to call the developer every new day to
upload event or some details regarding other information in the website. So the content
becomes obsolete.
• No interactivity with the users:
The current website do not allow interactivity to the visitors of the website. If any visitors want
to know anything more about the site then they can send any message from current site.
• Poor UI:
In the current website the user interface is not good. Poor user interface makes a bad
impression about the present event and as a result it decrease the chance of customer being
involved in the event.and use of books for long run.

1.3. Objectives

1. Visitors/Customers can send messages and enquiries to the Event management

from web application.
2. The Admin can add, edit, and delete user, event progress bar, events etc.
3. Improvement in performance of web application.
4. Admin can login and manage the overall content of the web application
5. Improved User interface.

1.4.Scopes
1. Allow admin to manage booking of event.

2. Allow admin to add a new event.

3. Allow admin to given event to the proper and legal customers.

4. Allow the users to view information of available event.

5. Allow the users to book a event.

Chapter 2

REQUIREMENT ANALYSIS

2. Background Study

 During our research and study we as volunteers and event organizers in college
events observed and tracked the problems and hustles generally faced by any
event manager. The most difficult task is keeping records physically and setting
registrations. After facing these issues we tried to convert things digitally and
online so that things can be accessed remotely by different stakeholders in the
event according to their positions and posts in particular events.
 We also went through talks and interviews from some professional event
managers and realized from their disposed information that most of the existing
systems mentioned below in survey are insufficient to overcome problems
faced by event managers and are incapable to serve organizers. They are doing
good on consumer side.

 i.e good for one who is coming to participate and enjoy the events but lack in
fulfilling organizers need. Also most ofthem lack communication channel
between managers and participants.

2.1. Literature Review

Requirements Determination

In system engineering and software engineering, requirements analysis focuses on the tasks
that determine the needs or conditions to meet the new or altered products or project, taking
account of possibly conflicting requirements of the various stakeholders, analyzing,
documenting, validating and managing software or system requirements.

2.2. Functional requirements

Functional requirement defines a function of a system or it’s component, where a function

is described as a specification of behavior between outputs and inputs. The functional
requirements of Event management web applicationare:
 Admin can add/remove new users.
 Admin can add, edit and delete the content of the web application
 Visitors are able to send message, place order, see events, give feedback through
the web application
2.3. Non functional requirements

Non-functional Requirements are often called “quality attributes” of a system. Other

terms for non-functional requirements are “qualities”, “quality goals”, “quality of
service requirements”, “constraints” and “non-behavioral requirements”. Non-
functional requirements are:
 Security: Data like personal details of admin must remain confidential. To
keep all these data, system doesn’t reveal the personal data to any other user.
 Accuracy: The information on user are significantly accurate.
 Availability: The system is available 24 hours so that general public can
access and use the system.

 Performance: The performance of the application is good and the user

interface is user-friendly. Anyone who can understand English and have
knowledge of web application can use the system.
 User Satisfaction: The system is designed to satisfy the user’s needs and
requirements.
2.4. Feasibility Analysis:

Feasibility analysis is used to assess the strengths and weaknesses of a proposed

project and present directions of activities which will improve a project and
achieve desired results. The nature and components of feasibility studies depend
primarily on the areas in which analyzed projects are implemented. The
feasibility analysis of this project had been carried out. They are as follows:

2.4.1. Technical feasibility:

Technical Feasibility is defined as the feasibility that is concerned with

specifying equipment and software that will successfully satisfy the user
requirement. It encompasses the technical needs of the system. Therefore, our
proposed system considers the following:

 Backend is created using node js.

 CSS, Font Awesome is used on the client side to give user friendly
interface to communicate with the backend.
 Database is used to store and retrieve data.

2.4.2. Operational feasibility:

Operational feasibility refers to whether a system will be used effectively after it

has been developed. The Event management web application provides all the
basic needs that a user can use on a daily basis. The user-friendly interface
provided by the web application makes it easy for a user to utilize the services
provided by the web application. Admin can easily login with basic information
like email and password. They can easily navigate to different parts of
application through the menu provides on the home page, and they can easily
logout of the system.
2.4.3. Economic feasibility:

Economic Feasibility is used to determine financial resources of the project. It

measures all costs incurred in development of new system. The development of
our system is within the budget and this was achieved because most of the
technologies used are freely available. Only the customized products had to be
purchased.

2. The tools and technologies mostly used for the system are free
for non- commercial purpose.
3. Hardware used for the system is easily available to the market and are
affordable.
4. The system after it has come to operation requires additional devices for
upgrade.

2.4.4. Schedule Feasibility:

In this Gantt chart, there are different task performed and their schedule while
creating project. Similarly, the total time consumed to create the overall project
is also mentioned below:

1
 Table: GANTT CHART

2.5. Tools and Technologies

2.5.1. Implementation tools

Language Used

 For Frontend: react .

 For Backend: node js

Database Used

 Mongo db

Chapter 3

METHODOLOGY

Waterfall model will be used as in the SDLC process

2
i. Requirements: All the needs and necessities of projects will be gathered.
ii. Design: Prototype will be build for as a sample design of project.
iii. Coding: By using java program will be written for as to built project.
iv. Testing; System and unit test will be done.
v. Operations: Where we deploy the code to a production environment and provide
support.

Conclusion
This online event management system could be implemented at several places
requiring to manage different events. This system is able to manage online
events irrespective of their scale. There are several events management
systems in the market and are doing good job but this project provides several
other features that some event management system lacks. This event
management system is quick and handy. During the research it was observed
that events are major part of a human being and several events take place on
daily basis. Lots of paper work is involved and hence lots of time and money
is also wasted managing those events. There is need for managing evens
digitally to reduce time and effort hence this leads us to this project and make
this project more relevant in current time. Small scale events happening in a
locality are usually given less preference than events occurring on a large
scale hence small-scale events may be highly benefited by this project. This
project leaves a huge scope for different type of implementat.

3
 Future Recommendation

The users suggest that the future researches may improve the current project. More
features may also be added to the system through future researches to improve and
enhance the capabilities of the system. Future researches may also create a mobile
application on iOS or android due to which the system will be more easily accessible
and may accommodate and support more users that use different mobile platforms.
Also with more advancements and innovations in the field of themes and decorations
there should be some samples that should be present on managers portal so that client
can select it based on their budget and thinking. Also a new feature to keep in touch
with the vendors and facilitators should be inculcated and a vendor directory should
be maintained region wise.

References

 Google [2]Byjus [3]W3S

 IEEEjournals [5]TutorialsPoint [6]Stackoverflow
 https://www.slideshare.net/AAKASHPANCHAL2/e vent-management-system-
document
 Geeks for Geeks and soon.
 International Journal of Trend in Research and Development, Volume 3(6),
ISSN:2394-9333 [10]IJIRMPS | Volume 6, Issue 5, 2018 (SOIT – ADYPU)
 International Journal of Computer Science Trends and Technology (IJCST) –
Volume 4 Issue 2, Mar - Apr2016.