Event Management System

A Mini Project Report Submitted to

JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY, HYDERABAD

In Partial Fulfillment of the requirement for the Award of the Degree of

BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE AND ENGINEERING
Submitted by

B. SAI DEEPAK (Ht.no.:20N01A0513)

Under the Supervision of

Mrs. Keshetti Srimathi
Assistant Professor

Department of Computer Science and Engineering

SREE CHAITANYA COLLEGE OF ENGINEERING
(Affiliated to JNTUH, HYDERABAD)
THIMMAPUR, KARIMNAGAR, TELANAGANA-505 527
DECEMBER-2023
 SREE CHAITANYA COLLEGE OF ENGINEERING
(Affiliated to JNTUH, HYDERABAD)
THIMMAPUR, KARIMNAGAR, TELANGANA-505 527
Department of Computer Science and Engineering

CERTIFICATE

This is to certify that the mini project report entitled “Event Management System”
is being submitted by B. SAI DEEPAK bearing hall ticket number: 20N01A0513 for partial
fulfilment of the requirement for the award of the degree of Bachelor of Technology in
Computer Science and Engineering discipline to the Jawaharlal Nehru Technological
University, Hyderabad during the academic year 2023 - 2024 is a bonafide work carried out
by him under my guidance and supervision.

The result embodied in this report has not been submitted to any other University or
institution for the award of any degree of diploma.

Guide Head of the Department

Mrs. Keshetti Srimathi Dr. Khaja Ziauddin

Assistant Professor Associate Professor

Department of CSE Department of CSE

EXTERNAL EXAMINER
i
 CIN NUM: U80900TG2019PTC134293

Date:

TO WHOM SO EVER IT MAY CONCERN

This is to certify that B. SAI DEEPAK bearing hall ticket number: 20N01A0513,
IV-B. Tech-CSE, Sree Chaitanya College of Engineering, Karimnagar, has done his
project work / Internship on the subject name of “EVENT MANAGEMENT SYSTEM”

He has done the project / Internship under the guidance of Mr. Sudharsan Reddy
Asst. Manager, in MSR EDUSOFT PVT LTD, Hyderabad.

During the period of his project work with us, we found his conduct and character
are Good.

We wish all the best for his future endeavors.

Managing Director
(D.MAHESWARA REDDY)
 SREE CHAITANYA COLLEGE OF ENGINEERING
(Affiliated to JNTUH, HYDERABAD)
THIMMAPUR, KARIMNAGAR, TELANGANA-505 527
Department of Computer Science and Engineering

DECLARATION

I, B. SAI DEEPAK is student of Bachelor of Technology in Computer Science and

Engineering, during the academic year:2023 - 2024, hereby declare that the work presented in
this Project Work entitled Event Management System is the outcome of our own bonafide
work and is correct to the best of our knowledge and this work has been undertaken taking care
of Engineering Ethics and carried out under the supervision of Mrs. Keshetti Srimathi,
Assistant Professor.
It contains no material previously published or written by another person nor material which
has been accepted for the award of any other degree or diploma of the university or other
institute of higher learning, except where due acknowledgment has been made in the text.

B. SAI DEEPAK (HT.NO: 20N01A0513)

Date:

Place:

ii
 SREE CHAITANYA COLLEGE OF ENGINEERING
(Affiliated to JNTUH, HYDERABAD)
THIMMAPUR, KARIMNAGAR, TELANGANA-505 527
Department of Computer Science and Engineering

ACKNOWLEDGEMENTS

The Satisfaction that accomplishes the successful completion of any task would be incomplete
without the mention of the people who make it possible and whose constant guidance and
encouragement crown all the efforts with success.

I would like to express my sincere gratitude and indebtedness to my project supervisor

Mrs. Keshetti Srimathi, Assistant Professor, Department of Computer Science and
Engineering, Sree Chaitanya College of Engineering, LMD Colony, Karimnagar for his
valuable suggestions and interest throughout the course of this project.

I am also thankful to Head of the department Dr. Khaja Ziauddin Associate Professor &
HOD, Department of Computer Science and Engineering, Sree Chaitanya College of
Engineering, LMD Colony, Karimnagar for providing excellent infrastructure and a nice
atmosphere for completing this project successfully.

I Sincerely extend out thanks to Dr. G. Venkateswarlu, Principal, Sree Chaitanya College
of Engineering, LMD Colony, Karimnagar, for providing all the facilities required for
completion of this Technical Seminar.

I convey my heartfelt thanks to the lab staff for allowing me to use the required equipment
whenever needed.

Finally, I would like to take this opportunity to thank my family for their support through the
work.

I sincerely acknowledge and thank all those who gave directly or indirectly their support in
completion of this work.

B. Sai Deepak (H.T. No: 20N01A0513)

iii
 ABSTRACT

The Event Management System (EMS) project is a tool that makes organizing events
easier. It helps plan and execute events by handling tasks like choosing a venue, managing
registrations, creating schedules, and allocating resources. With user-friendly interfaces for
both organizers and participants, EMS improves communication and collaboration. It provides
real-time updates, customizable event templates, and helps keep track of budgets. EMS is a
centralized platform that minimizes manual work, reduces errors, and optimizes resource use.
It's designed to be flexible for different types of events and includes features for analyzing and
improving future events.

iv
 TABLE OF CONTENTS
TITLE PAGE NO.

Certificate i
Declaration ii
Acknowledgments iii
Abstract iv
Table of Contents v-vi
List of Figures vii
List of Tables viii
CHAPTER 1 1-2
INTRODUCTION
1.1 Overview 1
1.2 Motivation 1
1.3 Existing System 1
1.4 Proposed System 2
1.5 Objective 2

CHAPTER 2 3
LITERATURE SURVEY
CHAPTER 3 4
PROBLEM DEFINITION
CHAPTER 4 5-8
SOFTWARE AND HARDWARE REQUIREMENTS
CHAPTER 5 9-33

DESIGN AND IMPLEMENTATION

5.1 Architecture of the Proposed System 11-12

5.1.1 Architecture 11-12
5.1.2 Module Description 13
5.1.3 System Workflow 14-15
5.1.4 Interaction among all Modules 16
5.2 System Design 17
5.2.1 ER Diagrams 17-18

v
 5.2.2 DFD Diagrams 19-20
5.2.3 UML Diagrams 21-24
5.3 Flow Chart 25-26
5.4 Sample Code 27-33
CHAPTER 6 34-37

TESTING
CHAPTER 7 38-39
RESULTS AND OUTPUT SCREENS
CHAPTER 8 40
CONCLUSION AND FUTURE SCOPE
REFERENCES 41

vi
 LIST OF FIGURES
FIG NO FIGURE NAME PAGE NO
5.1.1a Architecture of Proposed System 11
5.1.3a Event Management System Workflow 15
5.2.1a ER diagram for event management 18
5.2.2a Data flow diagram level 0 19
5.2.2b Data flow diagram level 1 20
5.2.3a Class diagram for event management 21
5.2.3b Use case diagram for event management 22
5.2.3c Sequence diagram for event management 23
5.2.3d Collaboration Diagram for Login 24
5.2.3e Collaboration Diagram for Employee Registration 24
7a Registration page of event management 38
7b view event page of event management 38
7c Event Details page of event management 39
7d Events booking page of event management 39

vii
 LIST OF TABLES
TABLE NO TABLE NAME PAGE NO

6a Test Case for login 36

6b Test Case for Check Event page 36
6c Test Case for Update page 37

viii
 CHAPTER-1

INTRODUCTION

1.1 OVERVIEW

An event management system (EMS) is a digital platform designed to simplify and streamline
the process of planning, organizing, and executing events. From creating event details and
managing registrations to promoting through various channels, an EMS covers the entire event
lifecycle. It offers tools for attendee and venue management, schedule planning, and seamless
communication with participants and sponsors. With features like mobile accessibility,
payment processing, and analytics, an EMS enhances efficiency and provides valuable insights.
Ultimately, it serves as a centralized hub for event organizers, facilitating a more organized,
efficient, and successful event experience.

1.1 MOTIVATTION

An Event Management System (EMS) serves as a dynamic catalyst, transforming the intricate
landscape of event planning into a seamless and efficient process. By leveraging cutting-edge
technology, it empowers organizers to navigate the complexities of scheduling, attendee
management, and promotion with unparalleled ease. The inherent flexibility and integration
capabilities not only enhance productivity but also ensure a more engaging and tailored
experience for both organizers and participants. With its comprehensive suite of tools, an EMS
becomes a motivational force, inspiring event planners to dream bigger, execute with precision,
and create memorable experiences that leave a lasting impact. In essence, it's not merely a
system; it's a driving force behind the realization of successful and extraordinary events.

1.2 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 event
management through internet. This system is not providing proper events information. The
system is giving manual information through the event management executer.

1
1.3 PROPOSED SYSTEM

The development of this new system contains the following activities, which try to automate
the entire process keeping in the view of database integration approach. This system maintains
employee’s personal, address, and contact details. This system will provide on line help and
search capabilities. User friendliness is provided in the application with various controls
provided by system rich user interface. Authentication is provided for this application only
registered users can access. event information files can be stored in centralized database which
can be maintained by the system. This system provides the employees to manage the events
systematically.

1.4 OBJECTIVE

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.

2
 CHAPTER-2

LITERATURE SURVEY

A literature survey for an event management system project involves reviewing existing
research, publications, and relevant materials related to event management, technology
integration, and similar systems. Here's a brief outline of potential topics to cover in a literature
survey for an Event Management System (EMS) project:

➢ The study conducted by Aswin Chandrasekharan, Nikhail Venkat, Aniruddha P.B, and
Siva Rama Krishnan Somayaji, titled "Barcode Enabled Event Management System
for Logistics and Consumables Management," presents an innovative approach to
enhancing the efficiency and security of event management processes. The focal point
of their research is the implementation of barcode technology for authentication,
specifically in the context of logistics and consumables management.
➢ The utilization of barcodes in the authentication process serves as a significant
advancement in event registration. Barcodes offer a quick and seamless method for
attendee registration, ensuring a swift and efficient check-in process. Unlike
traditional methods, such as manual entry or paper-based systems, the barcode-
enabled system significantly reduces the time required for registration, leading to a
streamlined and expedited check-in experience for event participants.
➢ One of the key advantages highlighted in the paper is the inherent security provided by
barcode authentication. Barcodes act as unique identifiers, enhancing the system's
security measures. The use of barcodes minimizes the risk of unauthorized access and
fraudulent activities, contributing to a more secure event environment. The
authentication process becomes not only faster but also more reliable, thereby
positively impacting the overall event management system.

3
 CHAPTER-3
PROBLEM DEFINITION

The problem definition for an Event Management System (EMS) project involves identifying
specific challenges or inefficiencies within current event planning practices that the system aims
to address. Here's a concise problem definition for an EMS project:

In traditional event management practices, organizers often encounter challenges related to

manual and time-consuming processes, fragmented communication, and limited analytical
insights. These inefficiencies can result in suboptimal planning, decreased attendee satisfaction,
and missed opportunities for engagement. The need for a centralized, user-friendly, and
technologically advanced Event Management System (EMS) is evident. This system should
streamline the entire event lifecycle, addressing issues such as cumbersome registration
processes, communication gaps, and the lack of real-time analytics. By tackling these
challenges, the EMS project seeks to revolutionize event planning, enhance organizational
efficiency, and deliver exceptional experiences for both organizers and attendees.

4
 CHAPTER-4

SOFTWARE AND HARDWARE REQUIREMENTS

FUNCTIONAL REQUIREMENTS

Functional requirements for a event management system typically include various features and
functionalities to ensure the smooth organization and management of events. Here is a list of
functional requirements that such a system might encompass:

User Authentication and Authorization: Allow different user roles (admin, organizer,
participant) to log in securely and access specific functionalities based on their roles.

Event Creation and Management: Enable authorized users to create, modify, and delete event
details such as event name, description, date, time, venue, and type of event (academic, cultural,
sports, etc.).

Registration and Ticketing: Provide a system for participants to register for events online,
purchase tickets (if applicable), and receive confirmations.

Payment Processing: Integration with payment gateways to facilitate secure online payment
for event tickets or other services (if any).

Dashboard and Event Listings: Display a user-friendly dashboard featuring upcoming events,
event categories, and filters for easy navigation and exploration.

Communication Tools: Implement features for organizers to communicate with participants

via email notifications, reminders, and updates about events.

Participant Management: Allow organizers to view and manage participant lists, including
tracking registrations, cancellations, and attendee check-ins during events.

Resource Management: Enable organizers to request and manage resources required for
events, such as venues, equipment, catering services, etc.

Scheduling and Calendar Integration: Provide a calendar view for users to check event
schedules, sync events with personal calendars, and avoid scheduling conflicts.

5
Feedback and Surveys: Incorporate mechanisms for collecting feedback from participants
post-event, through surveys or rating systems, to improve future events.

Reporting and Analytics: Generate reports and analytics on various aspects such as attendance
rates, ticket sales, popular events, etc., to help in decision-making and future planning.

Accessibility and Mobile Responsiveness: Ensure the system is accessible across different
devices (desktops, tablets, smartphones) and complies with accessibility standards for users
with disabilities.

Security Measures: Implement security protocols to safeguard user data, prevent unauthorized
access, and protect against cyber threats.

Admin Panel: Provide administrators with access to manage user accounts, permissions,
system settings, and oversee overall system functionality.

Integration with Social Media: Allow for easy sharing of event details on social media
platforms to increase event visibility and participation.

NON-FUNCTIONAL REQUIREMENTS

Performance Requirements:

Performance is measured in terms of the output provided by the application. Requirement

specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into required
environment. It rests largely with the users of the existing system to give the requirement
specifications because they are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the system can be designed

according to those requirements. It is very difficult to change the system once it has been
designed and on the other hand designing a system, which does not cater to the requirements of
the user, is of no use.

The requirement specification for any system can be broadly stated as given below:

• The system should be able to interface with the existing system

• The system should be accurate

6
• The system should be better than the existing system

Reliability :

In this system reliability means the mail which is send by the source must reach the target user
with any modification and accurate.

Security :

The web server and database server should be protected from hacking, virus etc

Portability :

The application will be developed using standard open source software (Except Oracle) like
Java, tomcat web server, Internet Explorer Browser etc these software will work both on
Windows and Linux o/s. Hence portability problems will not arise.

Availability :

This software will be available always.

Maintainability :

In this system the presentation layer is clearly separated from the service layer. So any
modification in future will be done with less efforts. The database will be running at the server.
Users access these forms by using the user-ids and the passwords.

7
SOFTWARE REQUIREMENTS:

Database : sqlite3
Frontend : HTML, CSS
Scripting language : Java Script
IDE : Pycharm
Technology : Python

HARDWARE REQUIREMENTS:

Processor : Intel P-IV based system

Processor Speed : 2.0. GHz
RAM : 1GB
Hard Disk : 40GB to 80G

8
 CHAPTER-5

DESIGN AND IMPLEMENTATION

Designing and implementing a college event management project involves several steps,
including defining requirements, creating a database schema, developing the backend and
frontend components, and testing the system. Below is a simplified outline to guide you through
the process:

Requirements Analysis:

Define the functionalities and features required for the event management system. Consider
features like event creation, participant registration, venue booking, user authentication, and
event reporting.

Database Design: Design the database schema to store information such as events, participants,
venues, and user details. Common tables might include:

• Events
• Participants
• Venues
• Users

Backend Development:

Choose a backend technology (e.g., Node.js, Django, Flask, Ruby on Rails) and develop the
server-side logic. This involves implementing CRUD (Create, Read, Update, Delete) operations
for entities like events, participants, and venues.

User Authentication:

Implement a secure user authentication system to manage roles and permissions. Users might
include administrators, event organizers, and participants.

Frontend Development:

Select a frontend framework (e.g., React, Angular, Vue.js) and create the user interface. Design
pages for event creation, participant registration, venue booking, and user authentication.

9
Integration:

Connect the frontend and backend components. Ensure that data flows smoothly between the
user interface and the server.

Event Creation:

Implement a feature for creating events. Allow organizers to set event details, including date,
time, venue, and description.

Participant Registration:

Create a registration system for participants. Allow them to sign up for events, provide
necessary information, and receive confirmation.

Venue Booking:

Implement a system for booking event venues. Ensure that organizers can check venue
availability and make reservations.

Reporting and Analytics:

Develop a reporting system for administrators to track event attendance, analyze participant
data, and gather insights.

Testing:

Conduct thorough testing of the entire system to identify and fix bugs. Test functionality,
security, and usability.

Deployment:

Deploy the application to a server or cloud platform. Ensure that it is secure, scalable, and can
handle potential traffic.

Documentation:

Document the project thoroughly, including user manuals, API documentation, and system
architecture.

User Training:

Provide training for users, especially administrators and event organizers, to ensure they can
effectively use the system.
10
Maintenance and Updates:

Regularly update and maintain the system to address bugs, security vulnerabilities, and user
feedback.

5.1 ARCHITECTURE OF THE PROPOSED SYSTEM

5.1.1 ARCHITECTURE

The system consists of three main components:

• Admin: The admin is responsible for managing the system, including creating events,
adding users, and managing the database.
• User: The user is the person who registers for events. Once registered, the user can view
a list of events, register for events, and view their registration information.
• Database: The database stores all of the information about the events, users, and
registrations.

Fig5.1.1a: Architecture of Proposed System

The system works as follows:

1. The user requests information about events.

2. The system sends the request to the database.
3. The database returns the information to the system.
4. The system displays the information to the user.
11
 5. If the user wants to register for an event, they can do so by clicking on the "Register"
button.
6. The system sends the registration information to the database.
7. The database stores the registration information.
8. The system displays a confirmation message to the user.

The event management system is a web-based application that can be accessed from any
computer with an internet connection. The system is designed to be easy to use and can be used
by people with no technical experience.

12
5.1.2 MODULE DESCRIPTION

The Modules involved are:

Event Management Module :

The employees who can use the application their personal information, contact information and
other information etc…

This module consist of events information. All the information like type of the event, incharge
of the event. These all information is maintained here.

Here in this module application is maintaining the total information of the event and the
resources. Like type of the resource, resource details and resource management.

Event Task Manager Module :

The module is having the information of the events and their task manager details. Events task
are maintained here, the total details of the events and incharge details maintained. In this
module the information of the event and their details like, what are the events are there and
from which event and to which event the movement is going on , which date , status of the event
etc.

Scheduling :

This module consists of events information. All the information like type of the event, in charge
of the event. These all information is maintained here.

Security & Authentication Module :

Security & Authentication module is main module which can provide security for entire
processing of the system by using username, password, login, password modifications etc.

Reports Module : In this module system can generate different type of the reports.

Payment Module: In this module user can pay the amount.

13
5.1.3 SYSTEM WORKFLOW

The system workflow in an event management system project typically involves the following
steps:

Event Planning:

The event planner creates an event proposal outlining the event's goals, target audience,
budget, and timeline.

The proposal is reviewed and approved by stakeholders.

A detailed event plan is created, including logistics, marketing, and budget allocation.

Event Promotion:

• The event is promoted through various channels, such as social media, email
marketing, and press releases.
• A registration process is set up to collect attendee information.
• Tickets are sold, if applicable.

Event Setup:

• The venue is booked and set up according to the event plan.

• Catering, entertainment, and other vendors are hired and confirmed.
• Audio/visual equipment is set up and tested.

Event Execution:

• The event is executed according to the plan.

• Attendees are welcomed and registered.
• The event program is delivered.
• Food and beverage service is provided.
• Networking opportunities are facilitated.

Event Evaluation:

• After the event, feedback is collected from attendees.

• The event budget is reconciled.
• A post-event report is generated, including key metrics and recommendations for
future events.

14
Fig5.1.3a: Event Management System Workflow

15
5.1.4 Interaction among all Modules
Customer Module:
• Add a sub-module for ticket sales and registration, which would allow customers to
purchase tickets and register for events online.
• Develop a system for tracking customer preferences and interests, so that you can send
them targeted marketing materials and recommendations for events they might enjoy.
• Create a loyalty program that rewards customers for attending events and spending
money on your platform.
Event Management:
• Develop a tool for creating and managing event schedules, including speaker
presentations, workshops, and networking events.
• Integrate with mapping and venue booking software to make it easy for customers to
find and book venues for their events.
• Add a live streaming or video recording feature so that people who can't attend events
in person can still participate.
Sponsors Management:
• Create a marketplace where sponsors can connect with event organizers and promote
their products and services.
• Develop a system for tracking the return on investment (ROI) for sponsors, so that they
can see how much value they are getting from their sponsorship.
• Offer different levels of sponsorship, with varying degrees of visibility and benefits.
Service Providers Management:
• Create a database of qualified service providers, such as caterers, decorators, and
entertainment providers.
• Develop a system for event organizers to request quotes and book services from service
providers.
• Allow service providers to manage their profiles and availability on your platform.

16
5.2 SYSTEM DESIGN
5.2.1 ER DIAGRAMS
Event: This entity represents an event that is being managed by the system. The attributes of
an event include event type, date, time, venue, and payment mode.

User: This entity represents a user of the system. The attributes of a user include user ID, name,
email, and phone number.

Payment: This entity represents a payment made for an event. The attributes of a payment
include payment ID, amount, date, and mode.

The relationships between the entities are as follows:

• One event can have many users. This means that an event can be attended by many
users.
• One user can attend many events. This means that a user can attend many different
events.
• One event can have many payments. This means that an event can have multiple
payments made for it.
• One payment can be for one event. This means that a payment can only be made for one
event.

The ER diagram also shows the cardinalities of the relationships. The cardinality of a
relationship is the number of instances of one entity that can be associated with a single instance
of another entity. The cardinalities in this diagram are as follows:

Event to User: Many-to-many (M:N) This means that many events can have many users, and
many users can attend many events.

Event to Payment: One-to-many (1:N) This means that one event can have many payments,
but each payment can only be for one event.

17
Fig5.2.1a: ER diagram for event management

18
5.2.2 DFD DIAGRAMS
A DFD is a graphical representation that depicts information flow and the transforms that are
applied as data move from input to output. The DFD may be used to represent a system or
software at any level of abstraction DFD’s may be partitioned into levels that represent
increasing information flow and functional details. The DFD provides a mechanism for
functional modeling as well asinformation flow modeling.

Level 0
The system starts with a client requesting an event, which is then entered into the system by an
admin. The event details are then stored in a database. The event planner can then view and
modify the event details in the database. The system also has a user access grant feature, which
allows the admin to grant access to the system to other users. Clients can only view and request
events, while admins have more privileges such as being able to grant access to other users.

Fig5.2.2a: Data flow diagram level 0

19
Level 1
This diagram outlines a user login and event management system. Users can browse and register
for events, while admins can add, delete, and update events. Payment information is stored in a
separate database.

Fig5.2.2b: Data flow diagram level 1

20
5.2.3 UML DIAGRAMS
The unified modeling language allows the software engineer to express an analysis model using
the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

Class Diagram :
The class diagram shows a set of classes, interfaces, collaborations and their relationships.

Fig5.2.3a: Class diagram for event management

21
Use case diagrams:

Use case diagram consists of actors, use cases and their relationships. These diagrams are
especially important in organizing and system modeling the behaviors of a system.

Fig5.2.3b: Use case diagram for event management

22
Sequence Diagram:

The Sequence diagram is an interaction diagram that emphasizes the time-

ordering of messages.

Fig5.2.3c: Sequence diagram for event management

23
Collaboration Diagram

The second interaction diagram is collaboration diagram. It shows the object organization as
shown below. Here in collaboration diagram the method call sequence is indicated by some
numbering technique as shown below.

Fig5.2.3d: Collaboration Diagram for Login

Fig5.2.3e: Collaboration Diagram for Employee Registration

24
5.3 Flow Chart

Start: The process begins with the user selecting an event.

New User?: The system checks if the user is already registered. If the user is not registered, the
system directs them to the registration page.
Registration: If the user is new, they will need to enter their information, such as their name,
email address, and password.
Already Registered?: If the user is already registered, they will be directed to the payment page.
Payment: The user will need to enter their payment information, such as their credit card
number.
Valid Password?: The system checks if the password entered is valid. If the password is
invalid, the user will be prompted to enter it again.
Confirmation: If the payment is successful, the user will be shown a confirmation page.
Success: The registration process is complete, and the user is registered for the event.
Login/Logout: If the user is already registered and logged in, they can skip the registration and
payment steps and go directly to the confirmation page.
25
Forgot Password?: If the user forgets their password, they can click on the "Forgot
Password?" link and enter their email address. The system will then send them a link to reset
their password.
The flowchart also includes some additional features, such as:
The ability for the user to cancel their registration
The ability for the system to send confirmation emails to the user
The ability for the system to track the number of registrations for each event
some common flowchart symbols include:
Ovals: Represent the start and end points of the process.
Rectangles: Represent actions or steps taken in the process.
Diamonds: Represent decision points where the flow of the process can branch based on a
condition.
Arrows: Indicate the direction of the flow between different parts of the process.
Parallelograms: Can represent data input or output points.

26
5.4 Sample Code
from django.shortcuts import render
from django.http import HttpResponse, HttpResponseRedirect
from scmapp.models import User, Admin, Event, Book_ground
import datetime
# Create your views here.
#User Registration / Login Page
def index(request):
return render(request,'registration.html')
#User Home Page
def user_home(request):
if 'uname' in request.session:
data = {'name':request.session.get('uname')}
if 'book_status' in request.session:
data['status'] = request.session['book_status']
return render(request,'user_home.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'registration.html',context=data)
#User Event Page
def user_event(request):
if 'uname' in request.session:
event = Event.objects.all()
data = {'event':event}
return render(request,'user_event.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'registration.html',context=data)
#User Ground Booking Page
def ground_booking(request):
if 'uname' in request.session:
data = {'date':datetime.date.today()}
return render(request,'ground_booking.html',context=data)

27
 else:
data = {'status':'You need to login first'}
return render(request,'registration.html',context=data)
#User Logout
def user_logout(request):
if 'uname' in request.session:
del request.session['uname']
if 'book_status' in request.session:
del request.session['book_status']
return render(request,'registration.html')
#Admin Login Page
def admin_login(request):
return render(request,'admin_login.html')
#Admin Home Page
def admin_home(request):
if 'aname' in request.session:
data = {'name':request.session.get('aname')}
return render(request,'admin_home.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'admin_login.html',context=data)
#Admin View Bookings
def admin_booking(request):
if 'aname' in request.session:
booking = Book_ground.objects.all()
data = {'booking':booking}
return render(request,'admin_booking.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'admin_login.html',context=data)
#Admin Manage Event Page
def admin_event(request):
if 'aname' in request.session:

28
 event = Event.objects.all()
data = {'event':event}
if 'event_status' in request.session:
data['status'] = request.session.get('event_status')
return render(request,'admin_event.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'admin_login.html',context=data)
#Admin Update Event Page
def update_event(request,id):
if 'aname' in request.session:
event = Event.objects.get(eid=id)
event.date = event.date.strftime('%Y-%m-%d')
event.time = event.time.strftime('%H:%M:%S')
data = {'event':event}
return render(request,'update_event.html',context=data)
else:
data = {'status':'You need to login first'}
return render(request,'admin_login.html',context=data)
#Admin Add Event Page
def add_event(request):
if 'aname' in request.session:
return render(request,'add_event.html')
else:
return HttpResponse('Something went wrong')
#Admin Logout
def admin_logout(request):
if 'aname' in request.session:
del request.session['aname']
if 'event_status' in request.session:
del request.session['event_status']
return render(request,'admin_login.html')
#BACKEND -> For User Registration

29
def test(request):
if request.method == 'POST':
name = request.POST.get('uname')
email = request.POST.get('email')
gender = request.POST.get('gender')
password = request.POST.get('password')
re_password = request.POST.get('repassword')
if(password == re_password):
user = User(name=name,email=email,gender=gender,password=password)
user.save()
request.session['uname'] = name
return user_home(request)
else:
data = {'status':"Password and Re-entered password must be same"}
return render(request,'registration.html',context=data)
else:
return HttpResponse("Something went wrong!!!!!")
#BACKEND -> For User Login
def login_user(request):
if request.method == 'POST':
name = request.POST.get('name')
password = request.POST.get('password')
try:
user = User.objects.get(name=name)
if user.password == password:
request.session['uname'] = name
return user_home(request)
else:
data = {'status':"Incorrect Password!!!"}
return render(request,'registration.html',context=data)
except Exception as e:
data = {'status':"User does not exists! You have to register first."}
return render(request,'registration.html',context=data)

30
 else:
return HttpResponse("Something went wrong!!!!!")
#BACKEND -> For Admin Login
def login_admin(request):
if request.method == 'POST':
name = request.POST.get('name')
password = request.POST.get('password')
try:
user = Admin.objects.get(name=name)
if user.password == password:
request.session['aname'] = name
# return HttpResponse('ffaf')
return admin_home(request)
else:
data = {'status':"Incorrect Password!!!"}
return render(request,'admin_login.html',context=data)
except Exception as e:
data = {'status':"Invalid Username"}
return render(request,'admin_login.html',context=data)
else:
return HttpResponse("Something went wrong faffsffa!!!!!")
#BACKEND -> For Ground Booking
def db_ground_booking(request):
if request.method == 'POST':
mobile = request.POST.get('mobile')
date = request.POST.get('date')
time = request.POST.get('time')
try:
book = Book_ground.objects.get(date=date)
data = {'status':'Please select other date'}
return render(request,'ground_booking.html',context=data)
except Exception as e:
user = User.objects.get(name=request.session['uname'])

31
 book =
Book_ground(uid=user.uid,name=user.name,mobile=mobile,date=date,time=time)
book.save()
request.session['book_status'] = "Booking successful"
return user_home(request)
else:
return HttpResponse("Something went wrong!!!!!")
#BACKEND -> For Update Event
def db_update_event(request,id):
if request.method == 'POST':
name = request.POST.get('name')
date = request.POST.get('date')
time = request.POST.get('time')
duration = request.POST.get('duration')
event = Event.objects.get(eid=id)
event.name = name
event.date = date
event.time = time
event.duration = duration
event.save()
request.session['event_status'] = 'Event updated successfuly'
return admin_event(request)
else:
return HttpResponse("Something went wrong!!!!!")
#BACKEND -> For Delete Events
def db_delete_event(request,id):
if request.method == 'GET':
event = Event.objects.get(eid=id)
event.delete()
request.session['event_status'] = 'Event deleted successfuly'
return admin_event(request)
else:
return HttpResponse("Something went wrong!!!!!")

32
#BACKEND -> For Add Event
def db_add_event(request):
if request.method == 'POST':
name = request.POST.get('name')
date = request.POST.get('date')
time = request.POST.get('time')
duration = request.POST.get('duration')
event = Event(name=name,date=date,time=time,duration=duration)
event.save()
request.session['event_status'] = 'Event added successfuly'
return admin_event(request)
else:
return HttpResponse("Something went wrong!!!!!")

33
 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 functionalities
of components, sub 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 tests. Each test type
addresses a specific testing requirement.
Types of Testing
Unit Testing
Unit testing focuses verification effort on the smallest unit of software design, the module. The
unit testing we have is white box oriented and some modules the steps are conducted in parallel.
Integration Testing
Testing is done for each module. After testing all the modules, the modules are integrated and
testing of the final system is done with the test data, specially designed to show that the system
will operate successfully in all its aspects conditions. Thus the system testing is a confirmation
that all is correct and an opportunity to show the user that the system works. The purpose of
integration testing is to verify functional, performance and reliability requirements placed on
major design items. These "design items", i.e. assemblages (or groups of units), are exercised
through their interfaces using black box testing, success and error cases being simulated via
appropriate parameter and data inputs. Simulated usage of shared data areas and inter-process
communication is tested and individual subsystems are exercised through their input interface.
Test cases are constructed to test that all components within assemblages interact correctly, for
example across procedure calls or process activations, and this is done after testing individual
modules, i.e. unit testing.
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.

34
White Box Testing
This type of testing ensures that
All independent paths have been exercised at least once
All logical decisions have been exercised on their true and false sides
All loops are executed at their boundaries and within their operational bounds
All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.
Basic Path Testing
Established technique of flow graph with Cyclometer complexity was used to derive test cases
for all the functions. The main steps in deriving test cases were:
Conditional Testing
In this part of the testing each of the conditions were tested to both true and false aspects. And
all the resulting paths were tested. So that each path that may be generate on particular condition
is traced to uncover any possible errors.
Data Flow Testing
This type of testing selects the path of the program according to the location of definition and
use of variables. This kind of testing was used only when some local variable were declared.
The definition-use chain method was used in this type of testing. These were particularly useful
in nested statements.
Loop Testing
In this type of testing all the loops are tested to all the limits possible. The following exercise
was adopted for all loops: All the loops were tested at their limits, just above them and just
below them. All the loops were skipped at least once. For nested loops test the inner most loop
first and then work outwards. For concatenated loops the values of dependent loops were set
with the help of connected loop. Unstructured loops were resolved into nested loops or
concatenated loops and tested as above. Each unit has been separately tested by the
development team itself and all the input have been validated.

35
Unit Testing Reports:
Test Case 1 ( Login)
Sl No. of test case : 1

Name of test : login test

Sample Input : Click on login that runs admin.jsp

Expected output : login GUI should display

Actual output : login GUI displayed as expected

Remarks : Test Successful

Table 6a: Test Case for login

Test Case 2(Check Event page)

Sl No. of test case : 2

Name of test : Check Event page test case

Clicking the Check Event page that runs

Sample Input :
CheckEvent.jsp

Expected output : All Event details are viewed.

Actual output : All Event details are viewed.

Remarks : Test case successful

Table 6b: Test Case for Check Event page

36
Test Case 3(Update page)

Sl No. of test case : 3

Name of test : Update page

Sample Input : Click on Update. Here it runs Update.jsp

Expected output : Update details with submit Update is allowed.

Actual output : Update details with submit Update is allowed.

Remarks : Test successful

Table 6c: Test Case for Update page

37
 CHAPTER -7
RESULT AND OUTPUT SCREENS

Event Management System

Fig7a: Registration page of event management

The above screen shows the details of Registration page.

Event management system

Fig7b: view event page of event management

The above screen is the main screen for this project.

38
It contains the details about the event management system. In this page it contains
events present and booking.

Events

Fig7c: Event Details page of event management

The above screen shows of list of events and their details.

Fig7d: Events booking page of event management

39
 CHAPTER -8
CONCLUSION AND FUTURE SCOPE

The “Event Management” was successfully designed and is tested for accuracy and quality.
During this project we have accomplished all the objectives and this project meets the needs of
the organization. The developed will be used in searching, retrieving and generating
information for the concerned requests.

GOALS ACHIVIED

✓ Reduced entry work

✓ Easy retrieval of information
✓ Reduced errors due to human intervention
✓ User friendly screens to enter the data
✓ Portable and flexible for further enhancement
✓ Web enabled.
✓ Fast finding of information request

40
 REFERENCES

[1]. Wikipedia, URL: http://www.wikipedia.org.

[2]. Answers.com, Online Dictionary, Encyclopedia and much more,

URL: http://www.answers.com

[3]. Google URL: http://www.google.co.in

[4]. Project Management URL: http://www.startwright.com/project.htm

41