This document presents an online event management system created by a group of students. It provides a high-level overview of the system's features and capabilities including allowing users to book and cancel events, view event details, make payments, and update their profile information securely from any device. It aims to simplify the event management process and save users' time compared to existing manual systems. Class diagrams are shown to explain the system's functional requirements and architecture. Non-functional requirements around performance, reliability, availability, security, maintainability and portability are also addressed.

1. GROUP-11
ONLINE EVENT
MANAGEMENT SYSTEM

2.  PRESENTED BY
VAMSI KRISHNA – 15MIS0024
SRAVAN KUMAR -15MIS0040
RAMA KRISHNA - 15MIS0185
DINESH.B.S - 15MIS0198
NAVEENCHANDER - 15MIS0315
DINESH.C - 15MIS0435

4. ABSTRACT
 Our main aim of this project is to make and
provide an ideal software solution to book – events
,to cancel events, to protect user data and to save
the valuable time of the user .
 To fulfill the requirements of user.
 To make the user experience of using this
software is a pleasure one.

5.  Our OEMS is a software which provides each
and every information of the event like event
calendaring, venue scheduling, providing
details of manager and volunteer. It can be
accessible from any place.
 It helps to build good communication
between user and manager by providing full
details of manager and knowing full details
of user.
 It makes easy for user to access any event.

6.  It can provide an option for users to
update information.
 Protect the DB of the user by requiring a
correct and registered username and
password.
 It can add and delete the information of
new and old clients easily.
 It can add new supplier contacts with which
future communication is expected.
 It protects and hides the user details from
many other external and internal threats.

7.  In the existing system , the person has on
visit the particular office for enquiry.
 The existing system’s process is quite
complex and manual one.
 The Event management system has to
keep records of events manually.

8.  It consumes lot of time of user.
 Paper work results in a lot of space to keep the data.
 Lack of security.
 It have Chance of happening human errors.

9. 1.It is easy to use and fast to implement.
2.it is a web based and easy to access their information
anywhere on any device.
3.It helps to control problems that are usually happened
in any event.
4. Quick and easy registration for the participants.
5. Automatic conformation emails .
6.Online data submission is secured dual time .
7.Real time reports.
8.Saves time.
9.It helps for checking appointment of particular venue.
10.It also to check and know the target audience.
11.User friendly.

10.  REGISTRATION
 LOG IN
 SELECTING EVENT
 PAYMENT OF EVENT
 CANCELLING EVENT
 FORGOT PASSWORD
 LOG OUT
For explaining the functions and methods
of the functional requirements, we have
drawn class diagrams of each functional
requirement.

11. Class diagram for Registration:
Attributes: First name,last name,email id,phone number ,username
Methods: Get user name,get mail id,get phone number,set password.
Diagram:

12. Class diagram for LOG IN:
Attributes: User name, password , log in
Methods: Valid ,invalid
Diagram:

13. Class diagram for SELECTING EVENT:
Attributes: User id, password ,name, location.
Methods: Search event, check availability,select event.
Diagram:

14. Class diagram for PAYMENT OF EVENT:
Attributes: Customer details, booking info.
Methods: Online Payment ,receiving OTP, conformation of
successful Payment.
Diagram:

15. Class diagram for CANCELLATION OF EVENT :
Attributes: User details,Refund policies.
Methods: charges, refund balance.
Diagram:

16. Class diagram for FORGOT PASSWORD:
Attributes: Recovery mail id, mobile verification, recovery question.
Methods: change password
Diagram:

17. Class Diagram For Overall Event Management
System :

18. The Non- Functional requirements describes
the constraints under which specific features
of the system to be achieved.
Some Non-Functional requirements are :
 Performance
 Reliability
 Availability
 Security
 Maintainability
 Portability

19. Performance :
Response time
The software the responds very quickly in a very short period to
save the user’s time.
Capacity
It have the capability of accessing and handling to over 1500 user’s
at a time.
Software interfaces
System shall interface with an Oracle or Access database.
Hardware interfaces
System shall run on Microsoft window as well as android.

20. Reliability:
The reliability of total project depends on the reliability of
various components. The important component of reliability of the
system is providing backup for the database which is
continuously maintained and updated to reflect the most recent
changes also the system be functioning inside a container. Thus the
overall stability of the system depends on the stability of the
container and its underlying operating system.

21. AVAILABILITY :
The system should available at all times, meaning the
user can access it using a web browser , only restricted
by the down time of the server on which the system
runs . we will provide the working time of the software is
24x7 in a week.
SECURITY:
After entering the user name and password the user can accesshis profile
and details of user must be safe and secure. It provides high level security
for the database of user.

22. MAINTAINABILITY :
Software is developed in pythonbecause it is object oriented
programminglanguageandshall be easy to maintainandany
modificationto databaseis done onlyby admin.It helpsfor
maintainingthedatabaseandtheapplicationserver takes careof the
site. Also the software design is being done with modularity in
mind so that maintainability can be done efficiently.
PORTABILITY :
The code and supporting modules of the system will be well
documented and easy to understand. Online User Documentation
and Help System Requirements.

23. THANK YOU