EVENT MANAGEMENT SYSTEM

AIM:
To create a system to perform the Event Management system.

(I) PROBLEM STATEMENT:

In any event many service providers work simultaneously and it is very hard to manage these providers.
It is also important for event organizer that he has all the contact details of these service providers so
that he can contact them any time to plan a event at given time. In present system Event Company has
to do all management work manually.

They keep all payment information on papers. There is no system to check the past expenses on
any event. To do this , they have to check payment register and this task is very time consuming and
tiresome.

(II) SOFTWARE REQUIREMENTS SPECIFICATION:

1.0 INTRODUCTION

Event Management System is the interface between Customers and Event Managers. This system helps
the event management company to manage their paper work online and they can also receive report of
last event they have completed.

This system helps to manage historical data in database.

1.1 PURPOSE

Event management system is used to manage all the activities related to an event. In the manual
system event organizer has to keep all the details of these service providers so that he can contact them
any time to plan an event at given time. To manage all these activities, an Automated System is most
essential to meet this demand. This system helps the event company to manage their paper work
online. This system has been verified and validated successfully.

1.2 SCOPE

The System provides an online interface to customers where participants can register for any happening
event from anywhere. Event manager can keep records of participants. The data is organized in a central
way which is organized in a central way which is available to all the event managers. The authority
concerned with the management of event processes the application in a fast manner and makes the
event successful.
1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

 Event Organizer/Manager – Refers to the super user who are responsible for planning events
and ensure they run smoothly.
 Customer/User – one who wishes the event to be happened.
 J2EE – Java 2 Enterprise Edition is a programming platform and it is a part of the java platform
for developing and running distributed java applications.
 HTTP – Hyper Text Transfer Protocol.
 TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol used to
connect hosts on the internet.
 Service providers – Refers to the people who provides service such as catering etc.

1.4 REFERENCES

IEEE Software Requirement Specification format

1.5 TECHNOLOGIES TO BE USED

 HTML,CSS,JAVASCRIPT

 Oracle 11g

 Visual Studio

 Java

1.6 TOOLS TO BE USED

 Visual Studio Tools

 Rational Rose tool (for developing UML Patterns)

1.7 OVERVIEW

Event management is the application of project management to the creation and development of
large scale events such as festivals etc. To get success in event management, event organizer should
have strong network contacts of service provider. To make an event successful event manager
needs different service provider.
2.0 OVERALL DESCRIPTION:

It will describe major role of the system components and inter-connections.

2.1 PRODUCT PERSPECTIVE

The SRS acts as an interface between the 'Users’ and ‘Event Organizers’. The system always tries to
make the interface as simple as possible and at the same time not risking the security of data stored
in the system. This minimizes the time duration in which the user can book different types of events.

2.2 SOFTWARE INTERFACE

 Front End Client - The interface is built using Visual Studio with HTML,CSS, JAVASCRIPT and
JQUERY.

 Back End - Oracle 11 g database

2.3 HARDWARE INTERFACE

 The interface should be of atleast 512 MB RAM, Windows 7 or 8.

 The server is directly connected to the client systems. The client systems have access to the
database in the server.

2.4 SYSTEM FUNCTIONS

 Secure Registration of information by the Users.

 Event management system generates reports from the past events.

 Event manager is the only authorized person to add the application information into the database.

2.5 USER CHARACTERISTICS

 User – These are the people who desire to plan for an event and submit the application
information to the database.

 Event Organizer/Manager – He has the privileges to plan for an event and ensuring that the event
runs successfully.

 Event Administrator – He is the person who is responsible for processing conference and events
bookings, liasing with other departments about customer requirements.

 Volunteers – These are the people who carry out their duties listed in volunteer description.

2.6 CONSTRAINTS

 Only registered users will be able to book online event venues.

 To get important notification through E-mail, user must have to provide an valid email address.

 Online meetings with event organizer/manager are not available.

 Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constant monitoring.
  User have to specify event information with most care.

2.7 ASSUMPTIONS AND DEPENDENCIES

 The client will be able to see available time slots for an event online.

 Users should have basic knowledge of computer and English.

 User may be facilitating for online payment.

 People should have proper internet connection to visit the website.

(III) USE-CASE DIAGRAM:

The event management use cases are:

1. Registration

2. Login

3. Event selection

4. Manager profile

5. Add volunteer

6. Payment

7. Add winner

8. Logout

ACTORS INVOLVED:

1. User

2. Admin

3. Manager

4. Volunteer
(IV) ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
can be used to describe the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control. An activity is shown as an rounded
box containing the name of the operation. This activity diagram describes the behavior of the
system.

(V) CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static analysis diagram. The main
task of object modeling is to graphically show what each object will do in the problem domain. The
problem domain describes the structure and the relationships among objects.
(VI) SEQUENCE DIAGRAM:
A sequence diagram represents the sequence and interactions of a given USE-CASE or scenario.
Sequence diagrams can capture most of the information about the system. Most object to object
interactions and operations are considered events and events include signals, inputs, decisions,
interrupts, transitions and actions to or from users or external devices. An event also is considered
to be any action by an object that sends information. The event line represents a message sent from
one object to another, in which the “form” object is requesting an operation be performed by the
“to” object. The “to” object performs the operation using a method that the class contains. It is also
represented by the order in which things occur and how the objects in the system send message to
one another.

(VII) COLLABORATION DIAGRAMS:

The diagram shows that the user is logged in and creates Account and subscribes for News letters.
Then, he will post different types of queries.
(VIII) DEPLOYMENT DIAGRAM:
Deployment diagrams are used to visualize the topology of the physical components of a system
where the software components are deployed.
(IX) COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships.
(X) STATE CHART DIAGRAM:
It consists of state, events and activities. State diagrams are a familiar technique to describe the
behavior of a system. They describe all of the possible states that a particular object can get into and
how the object's state changes as a result of events that reach the object.