A PROJECT REPORT

ON

ONLINE EVENT
MANAGEMENT SYSTEM

A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF

REQUIRMENTS FOR THE AWARD OF THE DEGREE “BACHELOR
IN COMPUTER APPLICATION.”

SUBMITTED BY :- GUIDED BY:-

LEADER : BIBEKANANDA PATTNAIK &
SUBHASREE SATAPATHY AMBIKA PRASADINI PADHY

ROLL NO.- DI36219 (Senior Lecturer of Computer Application)

REGISTRATION NO.- 47262/2018

TEAM MEMBER:
BARSHA RANI PANDA

ROLL NO.- DI28619

REGISTRATION NO.-47186/2018

TANUJA NAYAK

ROLL NO.- DI36819

REGISTRATION NO.-47268/2018
B. SONALI NAYAK

ROLL NO.- DI28419

REGISTRATION NO.- 47184/2018

DISHA COLLEGE OF MANAGEMENT AND TECHNOLOGY

JAGANNATHPUR, NEAR SIDHA BHAIRAVI TEMPLE, GANJAM, ODISHA
1
 Disha College of Management & Technology
Near Sidha Bhairabi Temple, Jagannathpur

Certificate

Certified that this project report “Online Event Management System“ is the
bonafide work of “Subhasree Satapathy (DI36219), Barsha Rani Panda (DI28619),
Tanuja Nayak (DI36819), B.Sonali Nayak (DI28419)“ who carried out the project
work under my supervision.

Signature
Signature
Principal
Name Disha College of Mgmt. & Technology
Project Guide
Date:

Signature of External Signature of Internal

2
 Acknowledgment

I express my sincere thanks to Mr. Shaik llias, Director, Disha College of

Management & Technology, Berhampur.

I pay my deep sense of gratitude to Mr. Raj Ku. Baliyar Singh, HOD of BCA
Department, Disha College of Management & Technology, Berhampur to encourage
me to highest peak and to provide me the opportunity to prepare the project. I am
immensely obliged to my friends for their elevating inspiration, encouraging guidance
and kind supervision in the completion of my project.

I feel to acknowledge my indebtedness and deep sense of gratitude to my guide Mrs.

Ambika Prasadini Padhy and Mr. Vivekananda Pattnaik Sr. Lecturer of BCA
Department whose valuable guidance and kind supervision given to me throughout the
course which shaped the present work as its show.

3
 Declaration

I hereby declare that the project work entitled “ONLINE EVENT MANAGEMENT
SYSTEM” submitted to Berhampur University, is a record of an original work done
by me under the guidance of Mr. Vivekananda Pattnaik and Mrs. Ambika
Prasadini Padhy, Designation of Computer Science Dept, Disha College of
Management & Technology, and this project work is submitted in the partial
fulfillment of the requirements for the award of the degree of Bachelor of Computer
Application.

Full Signature

Subhasree Satapathy

Roll No.: DI36219

Barsha Rani Panda

Roll No.: DI28619

Tanuja Nayak

Roll No.: DI36819

Sonali Rani Nayak

Roll No.: DI28419

4
 ABSTRACT
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/she has all the contacts
details of these service providers so that he/she can contact them any time to plan an
event at given time. To manage all these activity we have developed this web
application. 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 system, lighting providers, canteen
services, stage construction and so on. The system allows only registered user to login
and new users are allowed to register on the application. It allows the user to select
from a list of event types. Once the user enters an event type, the system then allows
the user to select the date and time of event, place and the event equipment’s. All this
data is logged in the database and the user is given a receipt number for his booking.
This data is then sent to the administrator and they may interact with the client as per
his requirements.

The aim to automate its existing manual system by the help of computerized
equipment’s and full-fledged computer software, fulfilling their requirements, so that
their valuable data/information can be stored for a longer period with easy accessing
and manipulation of the same. Basically the project describes how to manage for good
performance and better services for the clients.

5
CONTENTS :-
1. Introduction about the project
2. Modules (Details about all modules used in Project)
3. Functional Requirements
4. Non –Functional Requirements
5. Introduction
6. Existing System
7. Drawbacks of Existing System
8. Proposed System
9. Expected Advantages of Proposed System
10. Feasibility Study
TECHNICAL Feasibility
ECONOMIC Feasibility
BEHAVIORAL Feasibility
11. Software and Hardware Specifications
Hardware Specification
Software Specification
12. Software Development Life Cycle (SDLC)
Systems analysis, requirements definition
Systems design
Development
Integration and testing
Acceptance, installation, deployment
13. Maintenance
14. Design

6
 Logical Design,
Physical Design,
Module Design
Input Design
Output Design
15. Data Flow Diagram
0- LEVEL DFD,
1- LEVEL DFD,
2- LEVEL DFD
E- R DIGRAM
16. DATABASE Design
Relational Database Management System (RDBMS)
RELATIONS, DOMAINS & ATTRIBUTES
17. Normalization
First NF
Second NF
Third NF
18. Table Structure
19. Software Environments
20. Testing
21. Screen Shots
22. Conclusion
23. Scope for Future Enhancement
24. Bibliography

7
1. INTRODUCTION ABOUT THE PROJECT:-
In the present era, scopes of information technology growing with a very fast, We do not see any are
untouched from this industry. The scope of information technology has become wider includes;
Business and industry.

Our project named “EVENT MANAGEMENT SYSTEM” is an application that store, organize and
maintained all events for customer satisfaction. It is the application of project management to the
creation and development of large scale events. Events create opportunities for people to connect
with an area, spend time together, celebrate and experience the diversity of culture and foster
creativity and innovation.

2. MODULES:-
1. ADMINISTRATOR MODULE:-

➢ LOGIN
➢ MANAGE EVENT
➢ MANAGE VENUE
➢ USER DETAILS
➢ BOOKING DETAILS
➢ CONTACT DETAILS
➢ MANAGE FOOD AND DRINKS
➢ PAYMENT DETAILS

2. USER MODULE:-

➢ REGISTER
➢ LOGIN
➢ BOOKING DETAILS
➢ PROFILE

8
3. FUNCTIONAL REQUIREMENTS:-
Requirement-3.1:-

ADMIN MODULE:-

Requirement-3.1.1

LOGIN :- This module shows the login page in which the admin can login in to the websiteby
entering their email and password.

Requirement-3.1.2

MANAGE EVENT : In this module the admin can add event, delete event and update event.

Requirement-3.1.3

MANAGE VENUE :- In this module the admin can add venue, delete venue and update
venue.

Requirement-3.1.4

USER DETAILS:- In this module the admin can view , update and delete user details in the
system.

Requirement-3.1.5

BOOKING DETAILS:- In this module the admin can view ,update and delete booking detailsin the
system.

Requirement-3.1.6

CONTACT DETAILS:- In this module the admin can view ,manage and reply the contactinformation
of the user.

Requirement-3.1.7

MANAGE FOOD AND DRINKS:- In this module the admin manage the catering system
according to the requirements of the user.

Requirement-3.1.8

PAYMENT DETAILS:- In this module the admin can manage the payment information and
receipt of the user.

9
Requirement-3.2:-

USER MODULE:-

Requirement3.2.1
REGISTER:- In this module the user can create their account by register in to the website ,
entering the information like: name , email , password , confirm password , phone number.

Requirement-3.2.2
LOGIN:- In this module the can login in to our website who have already their account by
entering their email and password.

Requirement-3.2.3
BOOKING DETAILS:- In this module the user can book an event by fill up the fields that are
provided and also choose their events , venues , date and time of events, food items, drinks
etc.

Requirement-3.2.4
PROFILE:- In this module the user can view their booking information , register information
and also update their profile.

4. NON-FUNCTIONAL REQUIREMENTS:

4.1 SAFETY REQUIREMENT:

• The details need to be maintained properly.

• Users must be authenticated.

• The database must be kept backed up.

4.2 SECURITY REQUIREMENT:

• After entering the password and user ID the user can access his profile.

• The details of user must be safe and secure.

• Sharing of details.

• It provides high level security for the database of user.

4.3 PERFORMANCE REQUIREMENT:

• The system needs to be reliable.

• If unable to process the request then appropriate error message.

10
• Web pages are loaded within few seconds.

• System shall interface with an oracle or Access database

• System shall run on Microsoft window as well as android.

• Easy tracking of records and updating can be done. There are two types of requirement.

1. Static requirements- These requirements do not impose any constraints on the execution
characteristics of the system. They are number of terminals and number of users.

2. Dynamic requirement- These specify constraints on the execution characteristics of thesystem.

They typically include response time and throughout of the system.

4.4 PORTABILITY REQUIREMENT:

• The code and supporting modules of the system will be well documented and easy to
understand.

• Online user documentation and help system requirements.

4.5 RELIABILITY REQUIREMENT:

• 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.

4.6 AVAILABILTY REQUIREMENT:

• 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 24*7 in a week.

11
5. INTRODUCTION:-
Event management is the process of designing and producing events. An occasion, a gathering of
people at a certain place at certain time for a specific reason. This is basically a web application
where various events are planned and executed. The event includes any concert, functions, occasion
etc. it is a process of organizing a professional and focused event, for a particular target
audience. The event management system also deals with account planning for the events for
maximum profit. This site can be used as a very powerful promotional tool to launch or market a
product or services. Event management involves small sub-modules which have one unique base
module and which is describes the all event details. These details are basically made for the
customers. The customer who wanted to planan event they refer the system.

5.1 OBJECTIVE OF THE PROJECT:-

➢ Our aim is to make a user friendly website that can let a user to plan decoration for anevent.

➢ User can select the event and according to the event user appropriate decoration canbe
made.

➢ Choice of decoration can be made from the list of panel.

➢ Client will also find out the cost for particular decoration and virtual representation ofthat
particular decoration.
➢ The project will help clients to decorate for an event and the cost required forparticular
decoration. No need to visit decorators

➢ Identifying and determining corresponding control measures.

5.2 PURPOSE: The purpose of this document to build an online system to manage events,
customers, bookings for easy event management system.

5.3 SCOPE: The scope of the online event management system is to ease to event management
and to create a easy to use application for users, trying to book events. The system effectively
manages all the data related to the various events that take place in an organization and also to
maintain a centralized database of all event related information.

➢ Any field can be added and deleted from the database.

➢ Storing large amount of data is easy.
➢ Reduce the time.
➢ Reducing manual efforts for maintaining the system.

➢ To allow the access of data and software to only the people who are authenticated.
➢ Greater accuracy and consistency.

➢ Reducing paper work.

➢ Reducing cost.

➢ Improved arrangement for event coordination.

12
 ➢ Generating bills are easy.
➢ Gives quick information about customers, staffs, vendors and materials.
➢ Maintain very large database.
➢ Reducing the lead time & serve customers to their satisfaction.

5.4 DEFINITION: The event management system is the application to the creation and
development of small and large events such as festivals, conferences, weddings, birthdays,
concerts etc.

5.5 SYSTEM OVERVIEW: In our system a user can visit our site and easily book events
by a secure register system. If the user already have an account then the user can directly login
otherwise the user have to register first and after that he/she can book the event. We also
provide a secure payment system for the customers.

6. EXISTING SYSTEM:-
In the present scenario, existing system has many drawbacks which make it inefficient to carry on
with it. The present working system of the referred company is manual. It is difficult to maintain all
details of events, customers and the event sometimes delays due to unmanaged planning. As far as
quality is concerned it is ok but not as good when handled using computerized system. This system is
not providing online help. This system doesn’t provide tracking of users activities and their progress.
This manual system gives us very less security for saving data and some data may be lost due to
mismanagement. This system is not providing event management through internet and also not
providing proper events information.

7. DRAWBACKS OF EXISTING SYSTEM:-

• At present the system which is not effective and efficient way.
• It does not has the security. Any user can access that system.
• The existing system is not friendly.
• The existing system is not providing secure registration and profile management of allthe
users properly.
• It requires on expend hand to work on.
• If anyone wants to work on, then it requires a special training for this.
• Unnecessary printing is too much costly.
• There is no any file management technique used so it lacks it deserve high speed dataaccess.

To avoid the drawbacks we follow:-

1. More man power.

2. Time consuming.
3. Needs manual calculation.
13
 4. Consumes large volume of paper work.
To avoid all the limitation and make the working more accurately the system needs tobe
computerized in a better way.

8. PROPOSED SYSTEM:-
The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The existing system has several
disadvantages and many more difficulties to work well. The proposed system tries to eliminate
or reduce these difficulties up to some extent. The proposed system will help the user to reduce
the workload and mental conflict. The proposed system is computerized and gas been developed
using advance language therefore it gives more facilities than present system. It provides quick
data. In this system user have to enter the data only once and then it get linked with all files. This
reduces the workload of user and it is also a time saving process. The information about any event
can be easily retrieved and updating the record at regular interval.

9. EXPECTED ADVANTAGES OF PROPOSED SYSTEM:-

The system is very simple in design and to implement. The system requires very low systemresources and
the system will work in almost all configurations.

It has got following features;

• Minimize manual data entry.

• Minimum time needed for the various processing.
• Greater efficiency.
• Better service.
• User friendliness and interactive.
• Minimum time required.

10. FEASIBILITY STUDY:-

A feasibility study is a high-level capsule version of the entire system analysis and design process.
Having identified and defined all the elements of the event, it is necessary to consider the feasibility
of the proposed event. Although this is identified here as following onfrom event concept design, in
reality, the factors below would be considered at the same timeas the event was being designed.

Broadly speaking there are such areas which impact upon event feasibility which are listedbelow:

• Operational factors impacting on feasibility: venue availability, skills required, resources,

licenses and permits etc.
• Financial factors impacting on feasibility: costs and predicted revenues, funding sources, etc.
The document provide the feasibility of the project that is being designed and lists various
areas that were considered very carefully during the feasibility study of this project such as
technical, economical and behavioral feasibilities.

14
10.1 TECHNICAL FEASIBILITY:-
This involves questions such as whether the technology needed for the system exists, how difficult it
will be to build, and whether the firm has enough experience using that technology. The assessment
is based on outline design of system requirements in terms of input process , output field ,programs
and procedures. This can be qualified in terms of volume of data ,trends , frequency of updating in
order to give an introduction to the technical system. The application is the fact that it has been
developed on windows 10 platform and high configuration of 8GB ram on i5 10th generation
processor.

10.2 ECONOMICAL FEASIBILITY:-

Establishing the cost-effectiveness of the proposed system i.e. if the benefits do not outweigh the
costs then it is not worth going ahead. In the fast paced world today there is a great need of online
social networking facilities. Thus the benefits of this project in the current scenario make it
economically feasible. The purpose of the economic feasibility assessment is to determine the
positive economic benefits to the organization that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This assessment typically involves a
cost/benefits analysis.

10.3 BEHAVIORAL FEASIBILITY:-

It is a human resist changes in the beginning. Therefore the employees need to be given training
when a system is being implemented for the organization. The proposed system is highly user
interactive so it is easy for end user to understand the system and use it.

11. SOFTWARE AND HARDWARE SPECIFICATION:-

11.1 HARDWARE SPECIFICATION:-

• Processor: Intel(R) core™ i5-10210U CPU @ 1.60GHz 2.11GHz
• RAM: 2GB or above
• Operating System: Windows 10

11.2 SOFTWARE SPECIFICATION:-

• Package: XAMPP
• Text Editor: Visual Studio Code
• Database: MY SQL
• Browser: Google chrome
• Frontend language: HTML, CSS, JS
• Backend language: PHP, MY SQL

15
12. SOFTWARE DEVELOPMENT LIFE-CYCLE (SDLC) MODEL:-
Software development life cycle(SDLC) is a process used by the software industry to design, develop
and test high quality softwares. The SDLC aims to produce a high quality software that meets or
exceeds customer expectations, reaches completion within times and cost estimates. SDLC is a
framework defining tasks performed at each step in the software development process.

WHAT IS SDLC ?

SDLC is a process followed for a software project, within a software organization. SDLC is the
series of activities performed while developing a software . The development must be effective,
result oriented, qualitative, on time and with low cost so that the customer will appreciate the
software. The development team must determine a suitable life cycle model for a particular plan
and then observe to it.

Without using on exact life cycle model, the development of a software product would not be in a
systematic and disciplined manner. When a team is developing a software product, there must be a
clear understanding among team representative about when and what to do. Otherwise , it would
point to chaos and project failure.

A software life cycle model describes entry and exit criteria for each phase. A phase can being only
if its stage-entry criteria have been fulfilled. So without a software life cycle model, the entry and
exit criteria for a stage cannot be recognized. Without software life cycle models, it becomes tough
for software project managers to monitor the progress of the project.

Here we use spiral model for our project “EVENT MANAGEMENT SYSTEM”.

16
Spiral model:

Here, the picture looking like a spiral that means the operations take place while developing any
product, they will be in the form of spiral.

“Spiral model is a model of the software development process in which the constituent activities,
typically requirements analysis, preliminary and detailed design, coding, integration and testing are
performed iteratively until the software is complete.”

The spiral model known as Meta model because it use one or more process model (Waterfall,
Prototype, Evolutionary). It is the combination of waterfall model and iterative model. In this model
each phase starts with a design goal and ends with a customer reviewing. The spiral model have
many cycle.

Software is developed in a series of incremental release. The spiral model divided into frame work
activities also called as task regions. It is beneficial for large, complex and expensive projects. It is
based on unique risk patterns of a given project. It is a risk-driven software development process
model.

1. Communication:- Here, the developer and customer communicate. The developers discuss
the project and what are the requirement they want.
2. Planning:- In this task region the developers have to plan how to fulfill the requirement or
specification of the customer. The developer estimate the project scheduling the project and
analyzing the risk. The developers analyzing the risk and make alternative solution of them.
The risk may be technical of management risk. They prepared specific prototype to particular
problem components.
3. Modeling:- The developers prepare the documentation in a diagrammatic form. Developer
give a pictorial design to the project.
4. Construction:- The developer have to write code for the project and after that have totest for
know to the product is success or not and also prepare a report on it.
5. Deployment:- After testing the developer deliver to project to the customer, and if there is
any support requirement then the developer have to provide that. And the developer also get
the feedback from the user about the project.

The spiral model is a realizing approach for development of large-scale system and software.
Because the software progresses in a process and the developer and customer buffer understanding
and react to risks at each level. The spiral model uses prototyping a risk reduction mechanism but
also enables the developer, to apply the prototyping approach at any stage in developing of the
product.

Why we use spiral model?

• Because the project is large. When releases are required to be frequent.

• When risk and cost evaluation to be important. When requirement are unclear and
complex. For medium to high risk project.

17
 • It gives us space to get feedback directly from the customer.
• When long term project is running and commitment is not feasible due to changesmade
in economic priorities.
• Main benefit of this spiral model is risk management, this risk analysis phase save usfrom
complications in the future.

Advantages:-

• Additional functionality or changes can be done at later stage.

• Cost estimation become easy.
• It is a cyclic model. It works in a spiral shape. Alike a waterfall model which is alinear
one.
• It is risk-driven model and they using prototyping. Large projects are getting handledin a
strategic way.

Disadvantages:-

• It is not good for smaller projects. It might be cost.

• Risk is not meeting the schedule or budget.
• It is a complicated approach especially for projects with a clear SRS.
• The risk analysis phase requires an expert authority to make the analysis.
• For effective delivery, spiral model protocol should be followed strictly.

12.1 System analysis:- System analysis means the act, process, or profession of studying an
activity typically by mathematical means in order to define its goals or purposes and to discover
operations and procedures for accomplishing them most efficiently. It is a processof collecting and
interpreting facts, identifying the problems, and decomposition of a system into its components.

12.2 Requirements Definition:- This paper proposed a kind of software requirements analysis
technology method based on event-driven. In structured analysis method, system relation diagram,
DFD fragments and 0-level figure are developed through the establishment of events table. Further
DFD diagrams decomposition is carried on to obtain the analytical model. We can divided the
subsystem through events and external entities interaction, data storage interaction and common
point analysis in processing requirements.

12.3 System Design:- System design is the phase that bridges the gap between problem domain
and the existing system in a manageable way. This phase focuses on the solution domain, i.e.
“How to implement?”. In this phase, the complex activity of system
development is divided into several smaller sub-activities, which coordinate with each otherto
achieve the main objective of system development.

18
12.4 Development:- After the successful completion of the requirement and design phase, the next
step is to implement the design into the development of a software system. In the entire SDLC, the
development phase is considered to be the largest one. In this phase, the actual project is developed
and built. This is the phase where we start building the software and start writing the code for the
project. The outcome from this phase is Source Code Document (SCD) and the developed product.
The development phase marks the end of the initial section of the process.

12.5 Integration and Testing:- Testing is the last phase of the software development life cycle
before the software is delivered to customers. During testing, experienced testers start to test the
system against the requirement. Integration testing is a software testing methodology used to test
individual software components or units of code to verify interaction between various software
components and detect interface defects. Components are tested as a single group or organized in an
iterative manner. After the integration testing has been performed on the components, they are
readily available for system testing. Integration testing primarily focuses on verifying data
communication among different modules of the software.

12.6 Acceptance:- This system testing is perform by the customer himself after the product
delivery to determine whether to accept the delivered product or reject it. Acceptance testing is a
process of testing the system or its authenticity. The acceptance testing is executed by the client to
check whether the system is able to fulfill the requirements or not.Though system testing has been
completed successfully, the acceptance test is demanded by the customer. Tests conducted here are
repetitive, as they would have been covered in system testing.

12.7 Installation :- Installation testing is performed to check if the software has been correctly
installed with all the inherent features and that the product is working as per expectations. Also
known as implementation testing. Moreover, with the assistance of installation testing the team of
testers are able to validate the quality as well as the correctness of the installation process and ensure
that the users receive optimum user experience.

12.8 Deployment:- This phase is initiated after the system has been tested and accepted by the
user. The system is installed to support the intended business functions. System performance is
compared to performance objectives established during the planning phase. Implementation includes
user notification, user training, installation of hardware, installation of software onto production
computers, and integration of the system into daily work processes.

19
13. MAINTENANCE:-
The maintenance stage is the final phase of the SDLC. After software passes the design stage and is
implemented, the maintenance phase of the software life cycle begins. It allows individuals to check
the performance of the software after it is launched to see if it is all working correctly.

This stage is very important as it:

• Ensures that the system remains running at peak performance levels.

• Solves any software bugs/problems that arise.
• Customize the software to users needs as user’s needs may change with time.
• Adds increased functionally to the system.
• What happens during the rest of the software’s life: changes, correction, additions, moves to a
different computing platform and more. This is often the longest of the stages.

14. DESIGN:-
Design is the first step into the development phase for any engineered product or system. Design is a
creative process. A good design is the key to effective system. The term “design” is defined as “the
process of applying various techniques and principles for the purpose of defining a process or a
system in sufficient detail to permit its physical realization”. It may be defined as a process of
applying various techniques and principles for the purpose of defining a device, a process or a system
in sufficient detail to permit its physical realization. Software design sits at the technical kernel of the
software engineering process and is applied regardless of the development paradigm that is used. The
system design develops the architectural detail required to build a system or product. As in the case
of any systematic approach, this software too has undergone the best possible design phase fine
tuning all efficiency, performance and accuracy levels. The design phase is a transition from a user
oriented document to a document to the programmers or database personnel.

14.1 Logical Design-

Logical design pertains to an abstract representation of the dataflow, inputs and outputs ofthe
system. It describes the inputs(sources), outputs(destinations), databases(data stores),
procedures(data flows) all in a format that meets the user requirements.

The logical flow of a system and define the boundaries of a system. It includes the followingsteps:

• Reviews the current physical system – its data flows, file content, volumes ,Frequencies
etc.
• Prepares output specifications – that is, determines the format, content and Frequencyof
reports.
• Prepares input specifications – format, content and most of the input functions.
• Prepares edit, security and control specifications.
• Specifies the implementation plan.
• Prepares a logical design walk through of the information flow, output, input, Controlsand
20
 implementation plan.
• Reviews benefits, costs, target dates and system constraints.
14.2 Physical Design-
Physical design relates to the actual input and output processes of the system. It focuses on how
data is entered into a system, verified, processed, and displayed as output. It produces the working
system by defining the design specification that specifies exactly what the candidate system does.
It is concerned with user interface design, process design, and data design. Physical system
produces the working systems by define the design specifications that tell the programmers exactly
what the candidate system must do.

It includes the following steps-

• Design the physical system.

• Design the database and specify backup procedures.
• Design physical information flow through the system and a physical design
• Plan system implementation. Prepare a conversion schedule and target date.
• Determine training procedures, courses and timetable. Specify input and output media.
• Devise a test and implementation plan and specify any new hardware/software.
14.4 Module Design-
Module design is an approach used to design various products or applications by breaking it down
into separate or independent parts. These individual parts can then be used for the samefunctionality
in different systems or products.

Some of the benefits of modular design- Easy to customize products. Faster to market, cost
efficiency, sustainability, allow incremental upgrades.

• ADMINISTRATOR MODULE- Admin can Login to the website, add& manage events
and venues manage user details, booking details, contact details, manage food and drinks &
payment details
• USER MODULE- User register to the website after registration he/she can login and book
the event and venues according to their choices. Users create their profiles and also view and
edit their booking details.

14.5 Input Design-

In an information system, input is the raw data that is processed to produce output. During the
input design, the developers must consider the input devices such as PC, MICR, OMR, etc. It should
serve specific purpose effectively such as storing, recording, and retrieving the information. The
main forms used here are:

Login Form- This form through which different users can enter into the system. Different levels of
validation at server and client side have been given.
21
Client Requirement Form- This form allows the remote clients to register in the system.

Booking Form- This form allows the clients to booking in the system.

14.6 Output Design-

Design outputs are the results of a design effort at each design phase and at the end of the total
design effort. Establish and maintain procedures for Design Output define and document design
output in terms that allow an adequate evaluation of conformanceto design input.

• Convey information about past activities, current status or projections of the Future.
• Signal important events, opportunities, problems, or warnings.
• Trigger an action.
• Confirm an action.
Outputs from computers are required primarily to communicate the results of processing to the users.
They are also used to provide a permanent copy of these results for later consultation. The output
types are: External output, Internal outputs, Operational outputs, Interactive outputs, Turnaround
outputs. The outputs may be defined in terms of type of output, content, format, location, frequency,
response, volume, sequence and action required.

CLASS DIAGRAM:-

22
USE-CASE DIAGRAM:-

23
 ACTIVITY DIAGRAM:-

SEQUENCE DIAGRAM:-

24
15. DATA FLOW DIAGRAM
A dataflow diagram shows the way information flows through a process or system. It includes data
inputs and outputs, data stores, and the various sub processes the data moves through. DFDs are built
using standardized symbols and notations to describe various entitiesand their relationships.

The Basic Notation used to create the DFD’s are as follows:

External entities- An external entity can be a person, organization, or system that is external to the
system; from entities, the information flows into the system(also known as a source) or the entities
receive data from the system(also known as a sink). Entities are represented usingrectangles.

ENTITY NAME

• Processes- A process is an activity or a function that is carried by the system. Processes

manipulate and transform the data; they receive some inputs and generate some outputs. A
process name in the DFD should start with a verb and end in a noun; it should have at least
one input dataflow and one output data flow. Each process in the DFD is numbered uniquely.
Processes are described as a segmented rectangle.

PROCESS NAME

• Data stores- Data stores are used to store the information by the process that can be later
retrieved by the same or another process. A data store name should be noun e.g ‘order’ and it
should be assigned a unique number. Data stores are represented as a rectangle that has two
parts; one for its number and another for its name.

• Data Flows- Data flows describe the flow of information between processes, entities and
data stores. Data flows are represented using arrows; the data name is written above the arrow
and the arrow shows the flow direction.

25
 There are 3 level of diagrams are- 0(context level diagram)

1-level diagram

2-level diagram

0(CONTEXT) LEVEL DATA FLOW DIAGRAM:

26
1- LEVEL DATA FLOW DIAGRAM-

2- LEVEL DATA FLOW DIAGRAM-

27
ER-Diagram-

28
16. DATABASE DESIGN-
A database is an organized mechanism that has the capability of storing information through which a
user can retrieve stored information in an effective and efficient manner. The data is the purpose of
any database and must be protected. The main objectives of database designing are to produce
logical and physical designs models of the proposed database systems. The logical model
concentrates on the data requirements and the data to be stored independent of physical
considerations. It does not concern itself with how the data will be stored or where it will be stored
physically. The physical data design model involves translating the logical design of the database
onto physical media using hardware resources and software systems such as database management
systems(DBMS).

Relational Database Management System (RDBMS)- RDBMS is a Database Management

System (DBMS) that is based on the relational model as introduced by E. F. Codd. A relational
database management system (RDBMS) is a collection of programs and capabilities that enable IT
teams and others to create, update, administer and otherwise interact with a relational database.
RDBMS store data in the form of tables, with most commercial relational database management
systems using Structured Query Language (SQL) to access the database. However, since SQL was
invented after the initial developmentof the relational model, it is not necessary for RDBMS use. The
RDBMS is the most popular database system among organizations across the world. It provides a
dependable method of storing and retrieving large amounts of data while offering a combination of
system performance and ease of implementation.

Relations, Domains & Attributes-

A relation, also known as a table or file, is a subset of the Cartesian product of a list of domains
characterized by a name. and within a table, each row represents a group of related data values. A
row, or record, is also known as a tuple. The columns in a table is a field and is also referred to as
an attribute. A domain is the original sets of atomic values used to model data. By atomic value, we
mean that each value in the domain is indivisible as far as the relational model is concerned. A
description property which is owned by each entity of an entity set. Attributes helps to describe an
entity. Qualitative data that have a quality characteristics or attributes that is described in terms of
measurements.

• The relationships are established using key. The two main keys of prime importance are
primary key & foreign key. Entity integrity and referential integrity relationships can be
established with these keys.
• Entity integrity and referential integrity enforces that no primary key can have null values.
• Relationships have been set between every table in the database. This ensures both referential
and Entity Relationship Integrity.

29
17. NORMALIZATION-
Normalization is a systematic approach of decomposing tables to eliminate data redundancy
(repetition) and undesirable characteristics like Insertion, Update and Deletion Anomalies. It is a
multi-step process that puts data into tabular form, removing duplicated data from the relation tables.

Normalization rules are divided into the following normal forms:

First Normal Form: - First normal form (1NF) is a property of a relation in a relational database. A
relation is in first normal form if and only if the domain of each attribute contains only atomic
(indivisible) values, and the value of each attribute contains only a single value from that domain.

Second Normal Form: - Second normal form (2NF) is a normal form used in database
normalization. A relation is in the second normal form if it fulfils the following two requirements: It
is in first normal form. It does not have any non-prime attribute that is functionally dependent on any
proper subset of any candidate key of the relation.

Third Normal Form:-Third normal form (3NF) is a database schema design approach for
relational databases which uses normalizing principles to reduce the duplication of data,avoid data
anomalies, ensure referential integrity, and simplify data management.

UNNORMALIZED BOOKING TABLE

bo Stre City State Pin Conta Em Eve Eve Eve Boo Foodit Drin Th them Advance_
oki et co ctNu ail ntty ntd ntti king em ks em e_pri catering_
ng de mber pe ate me date e ce price
iD

B Dha BB Odis 75 88956 Kris Birt 12/ 12p 5/11 Lunch Soft car 1200 5000
O1 rma SR ha 10 45784 hna hda 11/ m- /20 drin to 0
1 biha 30 12 y 20 3p ks on
r m

B C.V. Ben Karn 56 76890 Lali Con 22/ 7p 10/1 Dinne Juic Ju 1300 4000
O2 Ram galu atak 00 45631 t34 cert 11/ m- 1/20 r e ng 0
2 an ru a 93 20 11p le
naga m bo
r ok

B Moti Mu Mah 40 93452 Pun Mar 2/1 7am 20/1 Lunch Cof ma 2500 10000
O3 lal mba aras 01 78968 it14 riag 2/2 - 1/20 /break ee/j ril 0
3 naga i htra 04 e 0 4p fast uice e
r m

30
1nf PK FK

Booking Email (@gmail.com) Contact Street City State Pincode Booking

ID NO. info ID

BO11 Krishna12 8895645784 Dharma BBSR Odisha 751030 01

bihar

BO22 Lalit34 7689045631 C.V.Raman Bengaluru Karnataka 560093 02

nagar

BO33 Punit14 9345278968 Motilal Mumbai Maharashtra 400104 03

nagar

Booki Booki Eventt Eventd Eventti Booking Foodit Drinks The theme_p Advance_cate
ng ng id ype ate me date em me rice ring_
info
id
01 BO11 Birthda 12/11/2 12pm- 5/11/20 Lunch softdri carto 12000 5000
y 0 3pm nks on

O2 BO22 Concert 22/11/2 7pm- 10/11/20 Dinner Juice Jungl 13000 4000
0 11pm e
book
O3 BO33 Marriag 2/12/20 7am- 20/11/20 Lunch Coffee maril 25000 10000
e 4pm e

03 BO33 Marriag 2/12/20 7am- 20/11/20 breakfa juice maril 25000 10000
e 4pm st e

2nf

Booking Booking Details

ID info ID ID

BO11 B1 01

BO22 B2 02

BO33 B3 03

Deta Email (@gmail.com) Contact NO. Street City State Pincode

ils
ID

01 Krishna12 8895645784 Dharma bihar BBSR Odisha 751030

02 Lalit34 7689045631 C.V.Raman Bengaluru Karnataka 560093

nagar

03 Punit14 9345278968 Motilal nagar Mumbai Maharashtra 400104

31
18. TABLE STRUCTURE-
Registration table
Column Name Data type Width Allow Default Description
Null
Sln Int 11 Primary None Unique ID generated for every user
key [AUTO_INCREMENT]

Username Varchar 30 No None Name of the user

Password Varchar 255 No None Password for registration process
Email Varchar 50 Unique None Email id of the user
key
ContactNumber Bigint 10 No None Contact number of the user
Type Varchar 30 No None

Contact table
Column Data type Width Allow Default Description
Name Null
c_id Int 10 Primary key None Unique ID generated for every user
[AUTO_INCREMENT]

Name Varchar 30 No None Name of the user

Email Varchar 30 No None Email id of the user
Phone Bigint 10 No None Contact number of the user
Query Longtext No None Query of the user
Event table

Column Data type Width Allow Default Description

Name Null
Event id int 10 Primary key None Unique
ID[AUTO_INCREMEN
T]
Eventname Varchar 30 No None Name of the event
Description Varchar 500 No None Description about event
Picture Varchar 20 No None Picture of the event

Venue Table

Column Data type Width Allow Default Description

Name null
theme_id int 10 Primary key None
Name Varchar 20 No None
Picture Varchar 50 No None
Theme Varchar 50 No None
Price float No None

32
 Booking Table
Column Data Type Width Allow Null Default Description
Name

booking iD Int 10 Primary Key None Unique ID generated for every user
[AUTO_INCREMENT]

Street Varchar 30 NO None Street of the user

City Varchar 20 No None City of the user

State Varchar 10 NO None State of the user

Pincode Int 7 NO None Pincode of the users location

ContactNu Int 10 NO None Contact number of the user

mber

Email Varchar 30 Unique key None Email of the user

Eventtype Varchar 50 NO None User can select the eventtype

Noofguest Int 5 NO None Total no of guest on the event program

Eventdate Date NO None User can select the date of their event

Eventtime Time NO None User can select the time of their event

Bookingdat Timestamp NO Current_ti Users booking date

e mestamp()

Fooditem Varchar 50 NO None User can select the food item according to their
choice
Drinks Varchar 50 NO None User can select the drinks according to their choice

Theme Varchar NO None User can select the theme of the event

theme_pric Float No None Cost of the theme

e
Advance_c Float No None Advance payment by user
atering_pri
ce

33
19. SOFTWARE ENVIRONMENT:-
Visual Studio Code:-

Visual Studio Code is a freeware source-code editor made

by Microsoft for Windows, Linux and macOS. Features include support
for debugging, syntax highlighting, intelligent code completion, snippets, code
refactoring, and embedded Git. Users can change the theme, keyboard shortcuts,
preferences, and install extensions that add additional functionality.
Visual Studio Code includes basic support for most common programming
languages. This basic support includes syntax highlighting, bracket matching, code
folding, and configurable snippets. Visual Studio Code also ships with IntelliSense for
JavaScript, Typescript, JSON, CSS, and HTML, as well as debugging support for
Node.js. Support for additional languages can be provided by freely available
extensions on the VS Code Marketplace.

Stable release: 1.53.2 (11 February 2021)

Initial release: April 29, 2015;

Preview release: 1.53.0-insider

Size: Windows: 40.8–68.3 MB; Linux: 46.5–66.6 MB; macOS: 67.5 MB

Programming languages: JavaScript, HTML, Java, CSS, Typescript

Platforms: x86-32 (32 bit Intel x86), x86-64, AArch64

XAMPP:-

XAMPP is a free and open-source cross-platform web server solution

stack package developed by Apache Friends, consisting mainly of the Apache HTTP
Server, Maria DB database, and interpreters for scripts written in
the PHP and Perl programming languages. Since most actual web server deployments
use the same components as XAMPP, it makes transitioning from a local test server to
a live server possible.
XAMPP is regularly updated to the latest releases
of Apache, MariaDB, PHP and Perl. It also comes with a number of other modules
including OpenSSL, phpMyAdmin, MediaWiki, Joomla, WordPress and more. Self-

34
 contained, multiple instances of XAMPP can exist on a single computer, and any
given instance can be copied from one computer to another. XAMPP is offered in
both a full and a standard version (Smaller version).

Stable release: 8.0.2 / February 9, 2021;

Initial release: September 4, 2002;

License: GNU General Public License

Platform: IA-32 (Windows package only) and x64 (macOS and Linux packages only)

Size: Windows: 157 MB; Linux: 152 MB; macOS: 357 MB

Available in: 11 languages

HTML:-

-HTML elements are the building blocks of HTML pages. With HTML constructs, images and
other objects such as interactive forms may be embedded into the rendered page. HTML provides a
means to create structured documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using
angle brackets. Browsers do not display the HTML tags, but use them to interpret the content of the
page.

CSS:-

CSS is designed to enable the separation of presentation and content, including layout, colors
and fonts. This separation can improve content accessibility, provide more flexibility and control in
the specification of presentation characteristics, enable multiple web pages to share formatting by
specifying the relevant CSS in a separate .CSS file which reduces complexity and repetition
in the structural content as well as enabling the .CSS file tobe cached to improve the page load
speed between the pages that share the file and its formatting.

JavaScript:-

JavaScript is high-level, often just-in-time compiled, and multi-paradigm. It has curly- bracket
syntax, dynamic typing, prototype-based object-orientation, and first-class functions.

JavaScript engines were originally used only in web browsers. They are also embedded in a variety
of applications created with frameworks such as Electron and Cordova.

35
PHP:-

PHP is a general-purpose scripting language especially suited to web development. It was originally
created by Danish-Canadian programmer Rasmus Lerdorf in 1994. The PHP reference
implementation is now produced by the PHP Group. PHP originally stood for Personal Home
Page, but it now stands for the recursive initialism PHP: Hypertext Pre- processor.

20. TESTING-

Testing is the vital for the success of any software/application.no design is ever perfect. Testing is
carried out in two phases. First phase is during the software engineering that is during the module
creation. Second phase is after the completion of software. This is system testing which verifies that
the whole set of programs hanged together.

Testing is a set of activity that can be planned in advanced and conducted systematically. Testing
begins at the module level and work towards the integration of entire computers based system.
Nothing is complete without testing, as it vital success of the system testing objectives, there are
several rules that can serve as testing objectives. They are

• Testing is a process of executing a program with the intend of findingan error.

• A good test case is one that has high possibility of finding an undiscovered error.
• A successful test is one that uncovers an undiscovered error.
If a testing is conducted successfully according to the objectives as stated above, it would
uncovered errors in the software also testing demonstrate that the software function appear to be
working according to the specification, that performance requirement appear to have been met.

There are three ways to test program.

• For correctness
• For implementation efficiency
• For computational complexity

The levels of testing include:

❖ Unit testing
❖ Integration Testing
❖ Data validation Testing
❖ Output Testing

36
Unit Testing- Each module is considered independently. It focuses on each unit of software as
implemented in the source code. Unit testing was done in Sell-Soft System by treating each module
as separate entity and testing each one of them with a wide spectrum of test inputs. Some flaws in the
internal logic of the modules were found and were rectified.

White Box Testing- In this technique, the close examination of the logical parts through the
software are tested by cases that exercise species sets of conditions or loops. All logical parts of the
software checked once. Errors that can be corrected using this technique are typographical errors. It
test all the individual parts within a module a logical decision on their true and the false side are
exercised, all loops and bounds within their operational bounds were exercised and internal data
structure to ensure their validity were exercised once.

Black Box Testing- This method enables the software engineer to device sets of input techniques
that fully exercise all functional requirements for a program. Black box testing tests the output and
the external data. It checks whether the input data is correct and whether we are getting the desired
output.

Alpha Testing- Acceptance testing is also sometimes called alpha testing. Be spoke systems are
developed for a single customer. The alpha testing proceeds until the system developer and the
customer agree that the provided system is an implementation of the system requirements.

Beta Testing- On the other hand, when a system is to be marked as a software product, another
process called beta testing is often conducted. During beta testing a system is delivered among a
number of potential users who agree to use it. The customers then report problems to the developers.
This provide the product for real use and detects errors which may not have been anticipated by the
system developers.

Integration Testing- Integration testing aims at constructing the program structure while at the
same constructing tests to uncover errors associated with interfacing the modules. Modules are
integrated by using the top down approach. After unit testing in Sell-Soft System all the modules
were integrated to test for any inconsistencies in the interfaces. Moreover differences in program
structures were removed and a unique program structure was devolved.

Validation Testing- Validation testing was performed to ensure that all the functional and
performance requirements are met.At the culmination of integration testing, software is completely
assembled as a package; interfacing errors have been uncovered and corrected, and a final series of
software test-validation checks may begin. In the proposed system, if the clients click the submit

37
button after registering or booking, then the system will show the confirmation message for their
actions. This is how the data validations were made in the proposed system.

System Testing- it is executing to check logical changes made in it with intention of finding errors.
A system is tested for online response, volume of transaction, recovery from failure etc. System
testing is done to ensure that the system satisfies all the users requirements.

The steps in the software testing-

• Preparation of the test cases.

• Preparation of the possible test data with all the validation checks.
• Complete code review of the module.
• Actual testing done manually.
• Modifications done for the errors found during testing.
• Prepared the test result scripts.

The unit testing done included the testing of the following items-

1. Functional of the entire modules/forms.

2. Validation for user input.
3. Checking of the coding standards to be maintained during coding.
4. Testing the module with all the possible test data.
5. Testing of the functionality involving all type of calculation etc.
6. Commenting standard in the source files.

After completion of the unit testing of all the modules, the whole system is integrated with all it’s
dependencies in that module. While integration, we integrated the modules one by one and tested the
system at each step. This helped in reduction of errors at the time of system testing.

The steps involved during system testing are as follows-

• Integration of all the modules/forms in the system.

• Actual testing done manually.
• Recording of all the reproduced errors.
• Modifications done for the errors found during testing.
• Prepared the test result scripts after rectification of the error.

The unit testing done included the testing of the following items-

1. Functional of the entire systems as a whole.

2. User interface of the system.
3. Testing the dependent modules together with all the possible test data scripts.
4. Verification and validation testing.
5. Testing the reports with all its functionality.

38
After the completion of system testing, the next following phase was the acceptance testing. Clients
at their end did this and accepted the system with appreciation. Thus we reached the final phase of
the product delivery.

Test Cases 1-
Module Name Precondition Test Check Result Remark
Registration No field should be kept All field and some This field is required Result is correct.
blank. Correct values of the fields are kept displayed to depict
must be supplied. blank. empty fields.
Login No field should be kept All field and some This field is required Result is correct
blank. Correct values of the fields are kept displayed to depict
must be supplied. blank. empty fields.

Test Case2-

Module Name Precondition Test Check Result Remark

User No field should be kept All field and some This field is required Result is correct.
authorization blank. of the fields are kept displayed to depict
blank. empty fields.
Query No field should be kept All field and some This field is required Result is correct.
blank. of the fields are kept displayed to depict
blank. empty fields.

Test case3-
Module Precondition Test Check Result Remark
Name
Book Event Start date should be Start date is kept “End date should Result is correct.
less than end date. smaller than end date be greater than start
date” message is
displayed
Book Event No field should be All field and some of This field is Result is correct.
kept blank. the fields are kept required displayed
blank. to depict empty
fields.

39
 21. SCREENSHOTS-
Home-Page :-

Event-page:-

40
After clicking view more button:-

41
Gallery-page:-

Service-page:-

42
 About-page:-

Team-page:-

Contact-form:-

43
Search-page:-

Registration-page:-

44
 If you enter any wrong information:-

Login-form:-

If you give wrong username and password:-

45
After Registration or login home page is:-

For booking:-
FIRST STEP IS SELECT CITY:-

46
SECOND STEP IS SELECT CATEGORYY:-

THIRD STEP IS SELECT VENUE:-

47
FOURTH STEP IS FILL UP BOOKING FORM:-

FIFTH STEP IS FILL UP CATERING FORM:-

48
USER-DASHBOARD:-

49
Admin-dashboard:-
Manage Events -

Manage Menu items -

50
Manage Venues -

Manage Booking -

51
Manage Contact -

52
22. CONCLUSION:-
The project “Online Event Management System” is a web based application. This software provides
facility for registration, login, event booking, feedback, profile update and cancel event. It can search
according to user’s choice events and venues. Our project is only humble venture to satisfy the needs
to manage their project work. Several user friendly coding have also adopted. This package shall
prove to be a powerful package in satisfy all requirements of the user. The objective of software
planning is to provide a frame work that enable the manager to make reasonable estimate made
within a limited time frame at the beginning of the software project and should be update regularly as
the project regularly. The project is an attempt to provide a prototype for what an event management
system can be! Therefore more commercial aspects are needed to be validated for the system to be a
commercially viable one.

The system is very flexible and versatile. This application is a user-friendly screen that enables the
user to use without inconvenience. Validation checks included have greatly reduced errors.

At the end it is concluded that we have made effort on following points-

• A description of background and context of the project and its relation to work
already done in the area.
• Made statement of the aims and objectives of the project.
• The description of the purpose, scope and applicability.
• We define the project on which we are working in project.
• We describe the requirement specifications of the system and actions that can be doneon
these things.
• We designed user interface and security issue related to system.
• Finally the system is implemented and tested according to the test cases.

53
23. SCOPE FOR FUTURE ENHANCEMENT-
In a nutshell, it can be summarized that the future scope of the project circles around
maintaining information regarding:

• In future we can use photo reorganization instead of using heterogeneous database more over
High speed, accuracy and non-redundant data are the main advantages of the proposed
system
• We can give more advance software for Event Management System including more facilities.
• We will host the platform on online servers to make it accessible worldwide.
• Integrate multiple load balancers to distribute the loads of the system.
• Create the master and slave database structure to reduce the overload of the database queries.
• Implement the backup mechanism for taking backup of codebase and database on regular
basis on different servers.

The above mentioned points are the enhancements which can be done to increase the applicability
and usage of this project. Here we can maintain the records of Event and Activity. There is a scope
for introducing a method to maintain the Event Management System. Enhancement can be done to
maintain all the event, activity, organization, attendees,conductors.

24. BIBLOGRAPHY-
The content for this project report has been taken from the following sources:

• https://www.freeprojectz.com

• https://phpgurukul.com/event-management-system-using-php-and-mysql/

• https://www.studentprojectguide.com/project-report/database-design/event-
management-system-database-design/

54