Department Of Masters Of Comp.

Applications

Course Code: MCA 61

Project Work

Presentation For I-Review

On
EVENT MANAGEMENT SYSTEM

Project Guide Presented

By:
Dr. Niranjan Murthy Sk Jani
Muzaffar
1MS17MCA48
 1.Project Introduction

PROBLLEM DEFINITION

Event Management System is used to create a dedicated website to manage and organise events.
The accessibility of the system should facilitate communication between users, clients, and
managers. It will allow clients to request events be made. It should then allow site managers to
create an event that includes the host, type of event, time, place, cost, and staff list. End users
should be able to sign up to attend or help staff the event.
.
 2.HARDWARE AND SOFTWARE
Requirements

Hardware Requirements:
 Processor i3 or higher
 Ram 4gb or higher

Software Requirements:
 Windows 8 or higher or Any Linux based OS
 Django(web designing)
 SQLite3
 Any browser
SOFTWARE REQUIRNMENT
SPECIFIATIONS (SRS)
 INTRODUCTION

1.1 PURPOSE

Inception is the beginning phase of requirements engineering. It defines how does a software project get started
and what is the scope and nature of the problem to be solved. The goal of the inception phase is to identify
concurrence needs and conflict requirements among the stakeholders of a software project. To establish the
groundwork I have worked with the following factors related to the inception phases:

• Identifying stakeholders

• Asking the first questions

• Recognizing multiple viewpoints

• Working towards collaboration

1.1 PRODUCT SCOPE

This document will address a few key themes in terms of the Event Management System – A web based
authenticated interface of creating new events and a notification system for running and upcoming events.
 2.Overall Description

2.1 PRODECT PERSPECTIVE:

We set the first set of context-free questions focuses on the customer and other stakeholders, overall project
goals and benefits. The questions are mentioned above. These questions helped us to identify all stakeholders,
measurable benefit of the successful implementation and possible alternatives to custom software development.
Next set of question helped us to gain a better understanding of problem and allowed the customer to voice his
or her perception about the solution. The final set of question focused on the effectiveness of the communication
activity itself.
2.1 PRODECT FUNCTIONS:

• Error free system (Maximum 5% error may be considerable)

• Web-based interfaces

• Accessible via the Internet.

• Maintain a database of all information in this system.

• Allow valid users to login and logout.

• Restrict access to functionality of the system based upon user roles

• Allow administrators of the system to change user types and configure parameters of the system • Allow valid
users that log in to see notification

• Restrict access to functionality of the system based upon user roles. For example, only Administrators of the
system will be provided functionality to change user types and update database.
 2.3 USER CLASS and CHARACTERISTICS:

• This part is to identify various user classes that we anticipate will use the web application. User
classes will be differentiated based on the use, product functions and features, technical
expertise, security and privilege levels and educational level. The solution is intended to be used
by three main different user classes; system administrators, system operators and customers or
regular users.
No special knowledge or skills should be
assumed for the part of the regular users. Users are not expected to learn or remember a set of
commands in order to start using the application. The prototype application will be only a web
based and then for the product versions there will be a desktop versions, smart phones and smart
Tablets.

 2.3 ASSUMPTIONS and DEPENDENCIES:

• The factors that affect the requirements stated in the SRS. These factors are not design
constraints on the software but any changes to these factors can affect the requirements in the
SRS. For example, an assumption may be that a specific operating system will be available on
the hardware designated for the software product. If, in fact, the operating system is not
available, the SRS would then have to change accordingly.
 CONCLUSION

Inception phase helped us to establish basic understanding about Event Management System, identify the people
who will be benefited if Event Management System establishes, define the nature of the Event Management
System and establish a preliminary communication with stakeholders. .
 Department Of Masters Of Comp. Applications

Course Code: MCA 61

Project Work

Presentation For II-Review

On
EVENT MANAGEMENT SYSTEM

Project Guide Presented By:

Dr. Niranjan Murthy Sk Jani Muzaffar
1MS17MCA48
 Project Details

This system manages all the events which are conducted in college/University/Other.

This system automatically generate certificate and issue it/mail it

.
System very efficiently store, maintain and retrieve data from its
database and can be use for further analysis(data mining & OLAP).

This system provides latest notification to its user.

Time saving activity

 Purpose

Manual hours that need to spend in record keeping and generating reports.

The data in a centralised way which is available to all the event managers.

Easy to manage historical data in database.

Participants can register for any happening event from anywhere.

Event manager can keep records of participants.

Easily generate certificates for participants and winners.

Certificates automatically mail to particular participants.

 Scope
This web application includes the IT fields. Secure Administrative panel.

Normal users are the participants.

They have to register for the events.

Users will have following functions:

Easy communication with the manager

Event time

Get instant message about any change Updates easily

Will get winner certificate directly by downloading

Hibernate Benefits
 Feasibility Study
Product : It is a event management system. By using this system various users can login and

participate in different events. It eases registration process so it’s a user friendly product.

Operational Feasibility : Operation of the proposed system depend on its various users. These

various user-type mentioned below.

(1)Admin

(2)Manager

(3)Normal User (Participants)/Volunteer

Admin will make managers for different events. And allocate Login ID. Thereafter Normal User

enters their details i.e Name, Enrollment Number, Course, Branch, College and also select

events.

Then manager will check user entries and will allot registration id for authentication purpose.

Manager can also change date, time of the events. Here manager responsible to check team

size, details. And manager is responsible to restrict unauthorized people or wrong entries.
database. Participants can register for any happening event from anywhere. Event manager

can keep records of participants and system can easily inform them by message and emails.

Using this system, event managers can easily generate certificates for participants and

winners and it’s automatically mail to particular participants.

Social Feasibility : Proposed system would be acceptable by the other peoples. Because eTL is

better than ordinary registration process and management in the following issues :

1. Faster than other older systems

2. Database keeps records

3. Time saving

4. Onclick system (Save Lots of papers)

 Functional Requirements

R1 : Registration
Description : To enter into this site user has to register himself first. Requirements of registration are first
name, last name, user name, email-id, password, confirm password etc.
Input : User Details
Output : Filled Registration Details.
Processing : User details are checked with database. Password constraint is checked as per validation.

R2 : User Login
Description : The System provides facility to login into the system.
Input : Enter username and password
Output : User Profile page
Processing : The system will check the input of user and if valid then login is done. Otherwise user will be
asked to re-enter the username and password.
 Functional Requirements
R3 : Select the event

Description : The user can select the event and also select payment method.
Input : Main event , Sub event, Enrollment number, Add team member .
Output : Event selected Successfully ,also see all detail and delete also .
Processing : The system will add selected data into database.

R4 : Forgot Password

Description : The user can send reset link to the mail id to reset password.
Input : Email id
Output : Reset link send to Email id.
Processing : By reset link we can easily change the password and update store in database .
 Functional Requirements
R5 : Admin panel

Description : The Admin can add manager ,main event ,sub-event also.
Input : main event, sub-event, manager.
Output : Add successfully in database.
Processing : The system will add selected data into database.

R6 : Manager panel

Description :The manager can add volunteer ,main event and sub-event also .
Input :Main event, sub-event , volunteer.
Output : Add successfully in database .
Processing : The system will add selected data into database.
 Functional Requirements

R8 : Logout

Description : The system provides the facility to logout from the site
Input : Select logout option
Output : Logout from the system
Processing : User will logout
Use case
Sequence Diagram of admin
Sequence Diagram of admin
Sequence Diagram of Volunteer
Data flow diagram
Data flow diagram
ER diagram
Data base
 MODULES
1.Registration – Participants can register online for any event.

2. Event – Event manager can generate event by this module. They can edit, delete

the information of any generated event.

3. Certificate – eTL can generate certificated automatically and system can mail it to

particular participant.

4. Notification – Participants can get notification about event timing, place or any

updates.

5. User Module – User can register for event. Can easily check event details times and
6. Volunteer Module – Volunteer can view the details of his/her event

participants. Volunteer has to update the winner of his/her event in the system.

7. Admin Module – DBA has all the rights. He can add, edit, delete any

information in the system. He can add new event, event manager,