Event Management System

Project Instructor
Miss Nazish Yousaf

Project developed by
Khajasta Iqbal
Qudsia Ejaz
Farah Sajjad
Sana Chaudhary
Ibrar Hussain
 Event Management System
Chapter 01. Introduction

1.1 Purpose of System

Event management system is used to manage all the activity related to event. 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 an event at given time. 
To manage all these activity we have developed this system. To get success in the event
management business, user should have strong network contacts of service provider. To make an
event, successful event, manager needs different service provider
like Sound systems services, Lighting providers, Canteen services, stage construction and so on.
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.
Keeping this entire problem in mind we have developed this system.
EMS is a complete management system that organizes different events according to
requirements of customers. It has different standards of menu, venue and decoration. In this
project we create a computer base management system. The system will be maintained and
managed by organizers.

Page 1 of 7
1.2 Designated Audience and Reading Suggestions

This infotainment is for Admin , Employee, Customer and all other stakeholders.

Introduction Admin ,Customer

Overall Description Admin,Customer,Employee
External Interface Requirements Admin,Customer,Employee
System Features Admin,Customer,Employee
Other non-functional Requirements Admin,Customer,Employee
Other Requirements Admin,Customer,Employee

1.3 Application Scope

Computerization means to change our manual system to computer based system. Keeping in
view the requirement and deficiencies of the existing system we proposed the computerized base
database system. A DATABASE is a collection of logically related data set or files. Each file
may contain different type of information and are used for specific purposes.

Chapter 02. Overall Explanation

2.1 Application View

In existing system records are maintained manually in file system which is time consuming and
have more drawbacks which are described below
 Security Problem of data manual Editing
 Manual Editing
 Cost Factor
 Lack of flexibility
 Time Factor
2.1.1 Security Problem of data manual Editing
In manual work data is stored in files, paper and register. In this method it is difficult to secure
and save the data completely. In many cases data may loss due to wastage of papers and others
many issues.

2.1.2 Manual Editing Page 2 of 7

Data is edit by manual way which consumes much time and human efforts which causes many
problems. Sometimes typewriting is also difficult task to manage.
2.1.3 Cost Factor
Every system was cane in to being for reducing cost and maximizing the benefits. In the
manually storage we need more space wastage of time, stationary and efforts.
2.1.4 Lack of Flexibility
The file processing system is not very flexible. It cannot easily generate the information that is
different from routine. It can take a lot of time to collect data from different files and write
programs to produce the desired information.

2.1.5 Time Factor

The time factor plays an important role in efficiency of any system which is manually operated
so its speed of processing is very slow and also a time consuming.

2.2 Application Functions Relationship

The basic requirements state that the users be will be able to securely register and manage their
profiles. They will also be able to navigate through available events (venue, menu, decoration)
by using a well defined navigation system. Finally, a payment mechanism will be built in to
allow the use of credit cards and checks to book an event.
The database will be maintained and managed by organizers/admin. They will have the authority
to approve and reject requests for events, their venue, menu, and decoration.

2.3 User Criteria and Characteristics

There are three main persons who play their role with our system; Customer,Admin,Employee. So each
of them has their own requirements.

Admin/Organizer: Admin have all the access. He can also hire employees and generate
bill.
Employee: Employees are hired by the organizers. They manage the whole event.
Customer: Customer has the ability to place an order. Customer can also pay for the
order.

2.4 Operating Environment

Our Event booking system will be available 24 hours a day.
2.5 Software Tools to be used
 Papyrus
 SQLite / database development

Page 3 of 7
Chapter 03. External Design Requirements

3.1 User Interfaces

One User Interface for user.

Admin/Organizer: Admin have all the access. He can also hire employees and generate bill.
Employee: Employees are hired by the organizers. They manage the whole event.
Customer: Customer has the ability to place an order. Customer can also pay for the order.

3.2 User Characteristics

Admin/Organizer: Admin have all the access. He can also hire employees and generate bill.
Employee: Employees are hired by the organizers. They manage the whole event.
Customer: Customer has the ability to place an order. Customer can also pay for the order.

Chapter 04. System Features

 The proposed system should be able to book different Events.
 To provide data storage in computerized form..
 The proposed system should be able to save time and efforts.
 To provide event booking our system minimized the cost.
 To provide the flexible system so changes can be easily accommodated..
 The system should be user-friendly and attractive.

4.1 Non Functional Requirements

Accuracy Requirements

Availability:

Our system must be available 24 hours a day.

Response time:

System should respond to the users within one minute.

Performance:

System should be able to withstand a large number of user requests for the desired service.

4.1.1 Refuge/Safety Requirements

Page 4 of
This system should have power backup records for server computing system. As7 the ambulances should
be available in 24 hours or a full day, there must be power backup for server which will gives the proper
information. Each and every day the data should be backup.
4.1.2 Security Requirements
Perceptive data is secure from unwanted access by user’s appropriate technology and execute strict user-
access process. Availability of unique user number and Password in such a way that unauthorized user or
illegal users cannot log in.

4.1.3 Software Quality Attributes

Maintainability:

System should deal with new technology or to fix defects.

Portability:

System or component should be easily transferred from one environment to another.

Accuracy:

System should provide the order total accurately.

Scalability:

System should manage a growing amount of work in a capable way or it should be able to accommodate
that growth of work.

Compatibility:

System should be compatible in every environment.

4.2 Other Requirements

Legal Requirements:

System must resolve all proprietary issues.

Page 5 of 7