“Event Management System”

 An Event is characterized by several elements coordinated together for a

period of time.
o Objective of the event

o Target audience who will visit the event.

o Period of the event.

o Manner of inviting the audience (Exclusive invitation, public advert

etc.)
o Type of Event

o Date(s) of the event

o Venue(s) of the event. (May even be in multiple cities/towns).

o Hospitality

o Performances

 Another important entity in the Events business is Sponsors. Sponsors are

either companies or specific departments within companies who have specific
event budgets, which may be solicited for to host certain kinds of events. For
example, as part of a Rock Festival event, 3 to 4 sponsors may be involved to
cover specific areas of expenditure. A particular readymade Jeans brand
company may sponsor ticket printing and sales, another company may
sponsor lighting and so on.

Category – RDBMS

This project can be purely considered for the RDBMS category. Why? Well there
are many reasons in support.
 This deals in keeping record of all the events organized.
 It deals with maintenance of the rights for each level of hierarchy of the
users in the company.
 Keeps track of all the sponsors and service providers.
Software Engineering Paradigm of Event management system
Spiral Model
This model has many cycles. The radial dimension represents the
cumulative cost incurred in accomplishing the steps done so far, and angular
dimension represents the progress made in completing each cycle of the spiral.

A spiral model is divided into a number of framework activities, also called task
regions. Typically, there are between three and six task regions.

 Customer communication – Tasks required to establish effective

communication between developer and customer.

 Planning – Tasks required to define resources, timelines and other

project related information.

 Risk analysis Of event management system – Tasks required to

assess both technical and management risks.

 Engineering – Tasks required to build one more representations of the

application.

 Construction and release – Tasks required to construct. Test, install and

provide user support (e.g. documentation and training).

 Customer evaluation – Tasks required to obtain customer feedback

based on evaluation of software representations created during the
engineering stage and implemented during the installation stage.

The spiral model is a realistic approach to the development of large-scale systems and
software. Because software evolves as process progresses, the developer and customer
better understand and react to risks at each evolutionary level. The spiral model uses
prototyping as a risk reduction mechanism but more important enables the developer, to
apply the prototyping approach at any stage in the evolution of the product. It maintains the
systematic stepwise approach suggested by the classic lifecycle but incorporates it into an
 iterative framework that more realistically reflects the real world. The spiral model demands
a direct consideration of technical risks at all stages of the project and, if properly applied,
should reduce risks before they become problematic.

DFD (Data flow diagram) of event management systme

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 as
information flow modeling.
A level “O” DFD, also called a fundamental system model or a context
model , represents the entire software element as single bubble with input and
output data indicated by incoming and outgoing arrows respectively.
A level “1” DFD contain five or six bubbles with interconnecting arrows.
Each of the processes represented at level 1 is a sub function of the overall
system.
Similarly DFD level 1 can be refined into next level 2 .The information flow
continuity has been maintained between each levels.

DFD ‘0’Level

Client
Event
Organization Event

Staff

‘1’ Level
Client
Event
Entry Event

Organize
event

Staff
DFD

‘2’ level

Register Client
Client
Not
Valid
Delivery
Check
Challan
Login
Valid

Enter Service
Event Estimate Delivery
Purchase
Event_Desc Order
Generate
Generate
Estimate
PO
Contact
Check
Possible
Contact Provider
Possible Valid

Enter
Sponsor Provider
Check
Not
Login
Valid
Enter Register
Sponsor

Staff Staff
Entity Relationship Diagram

Client Views

Submit
s

Checked Event Request

by

Staff

Contacts

Service
Sponsors
Providers

Generat Declare
e Sponsorshi
Estimate p Amount
Charges

Expenses Revenues

Estimates
Expenditure
Expenses
Class Diagram

Event
EventName
Description
ClientName Client
Date ClientName
Venue ClientDetails

AddEvent() Registration()
GetEvent() Login()
Proposal()

Staff
Staffname
Password ServiceProvider
ProviderId
Login() Type
Product
Units

AddProvider()
Sponsors AssignEvent()
SponsorId
SponsorName
Amount

AddSponsor()
AssoignEvent()
8. A Complete Database and tables detail with Primary and Foreign
Keys, and proper Constraints in fields..
Database Design and RDBMS

The general theme behind database design is to handle information as

on integrated whole. There is none of the artificiality that is normally
embedded in separate files or applications. A database is a collection
of interrelated data stored with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make
information access easy, quick, inexpensive and flexible for the user.
In database design of this project several objectives were considered.

1. Controlled redundancy: Redundant data occupies space and

therefore is wasteful. If versions of the same data are in
different phase of updating, the system gives conflict
information. A unique aspect of database design is strong a data
only once, which control redundancy and improves system
performance.

2. Ease of learning and use: A major feature of user-friendly

database package is how easy it to learn and use. Related to this
point is that a database can be modified without interfering with
established way of using data.

3. Data independence: An important database objective is

changing hardware and store procedures or adding new data
without having to rewrite application programs.

4. Performance: This objective emphasizes response time to

inquiries suitable to use of the data. How satisfactory the
response time is depends on the nature of the user database
dialogue.
9. Structure of Event management system

* Modular Structure
 Customer Module – It is customer who has to take initiative for inputting the
values for any event.

 Event management – The events needs to be entered for the company to

organize.

 Sponsors management – Some events cannot do without sponsors so their

arrangement and management has to be done.

 Service Providers management – These are care taker of the event so work has to
be allotted.

Process Logic of Module

Customer Module

Customer

Visits
Website

Creates
Login
Account

Does Event
Entry Check
Proposal
Event Module

Staff

Visits
Website

Login

Views
Event Entry

Prepares
Proposal
Checks
Gets Service
Sponsors Providers
Arranged
Sponsors Module

Staff

Visits
Website

Login

Adds
Sponsors

Sponsorship
Amount

Sponsorship
Get Method
Complete
Details
Service Module

Staff

Visits
Website

Login

Adds
Service
Providers
Rate per
Unit

No. of units
Get provided
Complete
Details