A Project Report on

“Event Management System”

At

C. B. Patel Computer College &

J. N. M. Patel Science College,
Bharthana-Vesu, Surat
As A Partial Fulfilment for The Degree Of

Bachelor of Computer Application

2023-24
Guided By: Submitted By:
Asst.Prof. Mohamedsohel Shaikh Grishma J. Chanchad(2054)
Raj C. Vavliya(2397)
Harshkumar G. Sojitra(2346)

C. B. Patel College of Computer Application

Bharthana-Vesu, Surat
Affiliated With

Veer Narmad South Gujarat University, Surat, Gujarat, India

 Acknowledgement

The reason of completing the project work successfully is not just our efforts but
efforts of many people. The people, who trusted us, guided us and encouraged us
with every means. Guide is a person who provides you the direction towards
success, so I feel great pleasure to express our gratitude to our guides, our faculty
members as well as every person who helped us directly or indirectly with our
project.

We are also indebted to our Professor Asst. Prof. Mohamedsohel Shaikh who
provided constant encouragement, support & valuable guidance before and during
our project. It was her effort who led us to this place for project work. Her guidance
and suggestions were valuable.

We are also Thanks full to our all Faculties Members & specially Our Dean
Dr.Dhananjay Patel , to give us opportunity to make us project.

Thank you very much,

Grishma J. Chanchad
Raj C. Vavliya
Harshkumar G. Sojitra
 INDEX

Topic Page No.

01. Introduction

02. Project Profile

03. Objectives

04. Project Category

05. Environment Description

06. Analysis Report

6.1 Current System

6.2 Limitation of Current System

6.3 Requirement Specification

6.4 Proposed System

6.5 Advantages of Proposed System

6.6 Data Flow Diagram

6.7 Process Specification

6.8 Data Dictionary

6.9 Table Structure With Relationship

07. Design Report

7.1 Site Diagram / Program Flow Diagram

7.2 Algorithms / E-R Diagram

7.3 Security Issues

7.4 Input Screen Layout

 7.5 Output Reports

08. Testing Report

8.1 Test Case Design

8.2 Testing Issues

09. Limitation of The Proposed System

10. Future Enhancement

11. Justifications Of System as MIS & DSS

12. References
 CHAPTER: 1

INTRODUCTION

INTRODUCTION
  College Profile

C. B. Patel College of Computer Application, Surat a highly commendable private institute, occupies
a place amongst the technical institutes of the southern region of Gujarat. It is established in year
2001, financed and run by the Navnirman trust, Surat. It is affiliated to Veer narmad south gujarat
university.

The college is controlled by the executive board formed from the representatives of the Trust under
constitution & by laws of the college. The college campus is located at the open green field areas
with a beautiful location, situated at New city light Road, Bharthana – Vesu, Surat.

The College has excelled itself in many fields. It has occupied a prominent place in the education
sphere of South Gujarat. The building surrounded by green fields and contains spacious classrooms,
well documented library, a multipurpose hall, modern computer lab. It has at present around 850
students.

 Vision
In 21st century, IT technology has been growing in every area of business & society, while in
competitive environment it is our vision to make the students more efficient in the field of
Information Technology, which will help students to become more efficient skill oriented
professional and ready to grab opportunities in the said field.

 Mission
Our mission is to provide learning experience through renowned educational institution which shall
expose the students in the area of computer application in day to day life.

Imparting quality undergraduate education in the area of Computer Application through well
designed curriculum and train students to apply this education for lifelong high quality careers and
give them competitive benefit in the ever- changing and challenging global work environment of
21st century.

 Objectives
The College of Computer Application shares University’s overall mission of being a center of
academic excellence by providing qualitative education and integrating training. The progressive
and innovative faculty, through their teaching, scholarship and publication, leadership and service
are fully committed to the provision of an educational environment which prepares individuals to
become successful professionals.

The main objective of the Department is to help students meet their long-range needs as maturing
professionals as well as their immediate needs upon entering the profession.
 CHAPTER: 2

Project Profile
 Project Profile

Project Title Event Management System

Front-End

Back-End

Language

Platform

Operating System

Microsoft Windows 11

Internal Guide Asst. Prof. Mohamedsohel Shaikh

Team Member Grishma J. Chanchad

Raj C. Vavliya
Harshkumar G. Sojitra

Submitted To C. B. Patel Computer Collage

CHAPTER: 3

Objectives
 Objective
Event management has many objectives, including:

 Budgeting :-
An event manager's primary responsibility is to create and manage the event's budget.
This helps limit plans and stimulate creativity.

 Event marketing :-
Event marketing involves :
- Keeping in touch with participants and visitors
- Understanding their needs and motivations
- Developing products that meet those needs
- Building a communication program

 Event planning :-
Pre-event surveys can help organizers set goals and plan the event. These goals can
also help assess the event's success.

 Event proposal :-
An event proposal is a critical document for promoting an event planning business. It
gives potential clients a chance to review the event's plan.

 Evaluating the success of the event :-

Event managers are responsible for evaluating the success of an event. This can include
using examples from past experiences to explain how factors are considered.

 Marketing and promotion :-

Event marketing and promotion involves :
- Creating awareness
- Generating interest
- Attracting attendees
- Consistent messaging across promotional materials and channels
- Leveraging online marketing channels, such as social media and email
 CHAPTER: 4

Project Category

Project Category
Event management is a process of organizing a professional and focused event, for a particular
target audience. It involves visualizing concepts, planning, budgeting, organizing and executing
events such as wedding, musical concerts, corporate seminars, exhibitions, birthday celebrations,
theme parties, etc. Event Management is a multi - million dollar industry, growing rapidly, with
events hosted regularly. Surprisingly, there is no formalized research conducted to access the
growth of this industry. The industry includes fields such as the MICE (Meetings, Incentives and
Events), exhibitions, conferences and seminars as well as live music and sporting events. On the
profession side, event management is a glamorous and exciting profession that demands a lot of
hard work and dynamism. The logistics side of the industry is paid less than the sales/sponsorship
side, though some may say that these are two different industries.

Event management is the application of Project Management to the creation and development of
large - scale events. The process of planning and coordinating the event is usually referred to
as event planning and which can include budgeting, scheduling, site selection, acquiring necessary
permits, coordinating transportation and parking, arranging for speakers or entertainers, arranging
decor, event security, catering, coordinating with third party vendors, and emergency plans. The
events industry now includes events of all sizes from the Olympics down to business breakfast
meetings. Many industries, charitable organizations, and interest groups hold events in order to
market themselves, build business relationships, raise money, or celebrate achievement. An event
refers to a social gathering or activity, such as a festival, (for example a musical festival), a
ceremony (for example a marriage) and a party (for example a birthday party). There are mainly 3
types of event management:

 Corporate Event Management

 Product Launch Event Management
 Special event Management

The project category of an Event Management System falls under the broader umbrella of
"Information Technology" or "Software Development." Specifically, it can be classified within the
domain of "Enterprise Applications" or "Business Software." Here are some potential categories and
subcategories for an Event Management System project:

1. Software Development:
 Custom Software Development
 Web Application Development
 Database Design and Management

2. Enterprise Applications:

 Event Management System

 Business Process Automation
 Customer Relationship Management (CRM)

3. Business Software:

 Corporate Event Planning Software

 Meeting and Conference Management
 Event Registration and Ticketing

4. Information Technology:

 IT Solutions for Event Planning

 Technology-enabled Event Services
 Cloud-based Event Management

5. Project Management:

 Project Planning and Execution

 Agile Software Development
 Team Collaboration Tools

6. App Development:

 Front-end Development
 Back-end Development
 Full-Stack Development

7. Database Management:

 Database Design and Optimization

 Data Storage and Retrieval
 Database Integration

8. User Experience (UX) and User Interface (UI) Design:

 UI/UX Design for Event Management Systems

  User-Centered Design
 Interaction Design

Remember that these categories are not mutually exclusive, and the project could be classified
under multiple categories depending on its scope and functionalities. Additionally, the classification
might vary based on the context or the industry in which the Event Management System is being
implemented.
 CHAPTER: 5

Environment Description
 Hardware and Software Requirement

 Software Requirement

SOFTWARE REQUIREMENT

OPERATING SYSTEM WINDOWS 11

Front End Dart, Flutter

Back End Firebase

Other Tools Used Android Studio, Chrome.

 Hardware Requirement
 HARDWARE

Client-Side Environment

PROCESSOR INTEL CORE I5

RAM 8GB RAM

HARD DISK 256 GB

Server-Side Environment

SSD 256 SSD

RAM 8 GB

MICROPROCESSOR INTEL CORE I5

 Technology To Be Used:
 Programming Languages:- Dart , Flutter
 Data base Management:- Firebase Firestore
 Payment Getway :- Razorpay

 Server-Side and Client-side Tools

Client-Side Environment

PROCESSOR INTEL CORE I3

RAM 4GB RAM

HARD DISK 256 GB

Server-Side Environment

HDD 256 HDD

RAM 4GB

MICROPROCESSOR AMD RYZEN 5 3550H

 CHAPTER: 6

Analysis Report

6.1 Current System

There are several existing systems for event management, including popular platforms like
Eventbrite, Cvent, and Bizzabo. These platforms enable individuals to book and organizing events
directly with each other, without the need for intermediaries like cultivate relationship.

Some key features of existing Event management systems include:

1. User profiles: Event management platforms typically allow users to create profiles that
include information about themselves, such as their name, location, and booking event
history.

2. Listing and search functionality: Organiser can list events for booking on the platform, and
Users can search for and booked these events. Many platforms offer advanced search
functionality, such as filters for price, location, and event category.

3. Communication tools: Most Event management platforms provide communication tools

that enable organiser and users to communicate with each other, such as messaging
systems or chat functionality.

4. Payment processing: Many Event management platforms provide integrated payment

processing systems, which enable users to securely pay for events using credit cards or
other payment methods.

5. Reviews and ratings: Event management platforms often have a system for organiser and
users to leave reviews and ratings for each other, which can help build trust and credibility
in the marketplace.

6. Dispute resolution: Some Event management platforms offer dispute resolution services,
which can help resolve conflicts between users and organiser.

7. Mobile apps: Many Event management platforms offer mobile apps that allow users to buy
and sell products on the go, using their smartphones or tablets.

Overall, existing Event management systems provide a convenient way for individuals to book and
organizing events directly with each other. However, they also present several challenges, such as
trust and credibility issues, pricing pressures, and competition from other organiser.

6.2 Limitation of Current System

The limitations of event management systems could include the following aspects. Keep in mind
that the technology landscape is dynamic, and advancements may have been made since then.
Here are some potential limitations:

1. Integration Challenges: Some event management systems may face difficulties when
integrating with other software or systems that event organizers use, leading to data silos
and manual workarounds.

2. Scalability Issues: Certain systems might struggle to scale effectively, especially when
dealing with a sudden influx of users, large events, or a high volume of transactions.

3. User Interface Complexity: The user interface of certain event management systems
may be complex or not very user-friendly, requiring a learning curve for users to navigate
and utilize the platform effectively.

4. Limited Customization: While many event management systems offer customization

options, there could be limitations in tailoring the platform to specific event requirements,
potentially limiting its suitability for unique events.

5. Dependency on Internet Connectivity: Systems heavily reliant on internet

connectivity may face challenges in locations with poor or unreliable internet access,
impacting the ability to manage events smoothly.

6. Data Security Concerns: With sensitive attendee data and financial transactions
involved, security is crucial. Some systems may face scrutiny regarding data protection
measures, and any security vulnerabilities could pose risks.

7. Cost Constraints: The cost of implementing and maintaining certain event management
systems may be a limiting factor for smaller organizations or events with tight budgets.

8. Limited Support for Hybrid Events: As the trend towards hybrid events grows
(combining in-person and virtual components), some systems may not be equipped to
handle the unique challenges and requirements associated with hybrid event management.

9. Inadequate Mobile Functionality: Mobile access is crucial for event organizers on the
go. Systems with limited or inadequate mobile functionality may hinder the efficiency of
managing events, especially during on-site operations.

10.Insufficient Real-time Updates: In dynamic event environments, real-time data and

updates are vital. Systems that lack real-time analytics or quick synchronization features
may hinder decision-making during the course of an event.

11.Reliability and Downtime: Unforeseen technical issues or system downtime during

 critical periods, such as during registration or on the day of the event, can be a significant
limitation.

It's important to note that advancements and improvements are continually made in the field of
event management systems. Before choosing a system, it's recommended to assess the specific
needs of your event, read user reviews, and consider any updates or new features that have been
introduced by the system providers since my last knowledge update.

6.3 Requirements Specification

  Requirement Analysis :
An event would need to meet several requirements in booking to be successful. The app should
have a user registration system, allowing users to create an account and store their personal and
payment information securely. The search and filter system should allow users to easily find the
events they want, with the ability to filter by price, time, place, and type.

The app should provide detailed events information, including descriptions, images, prices, charts,
and users reviews. The main types of requirements analysis include: Business, Customer, Product,
Functional, Non-functional. Each type represents a stakeholder or stage of the project and
communicates the project needs.

Event analysis is used to identify the interactions and responses between customers and
enterprises. It can be used in conjunction with other analysis techniques to define the profile of a
company's value streams.

 Data Gathering:
Data gathering involves collecting information about the target audience, the industry, and the
competition. This information can be gathered through surveys, interviews, market research, and
data analysis. Some key pieces of data that should be gathered for an event management platform
include:

 User demographics: age, gender, location, interests, and purchasing habits

 Competitor analysis: analyzing the strengths and weaknesses of competitors in the market

 Market trends: identifying current and future trends in the event managements industry

 Payment and shipping preferences: understanding how users prefer to pay and receive
their events

 Product inventory: determining the types of events that will be offered

on the platform

Once the requirements have been analyzed and the data has been gathered, this information can
be used to design and develop an event managements platform that meets the needs of its users
while also being profitable and scalable.

 Time-Line Chart

Work Tasks Ja Fe March Apr

n b
 Week 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
1.Requironment Gathering & Analysis
1.1 Learn Flutter
1.2 Requirement Gathering
1.3 Requirement Analysis
Milestone: Requirements Gathered.
2.Modeling
2.1 Identifying proposed project profile.
2.2 Identifying Objectives.
2.3 Scope definition.
2.4 Review.
Milestone: Modelling Completed.
3.System Design
3.1 Design system flow.
3.2 Database Design.
3.3 Organiser Side Design.
3.4 Consumer Side Design
3.5 Review.
Milestone: System Design completed
4.Coding
4.1 Organiser Side Coding
4.2 Consumer Side Coding
Milestone: Coding completed
5.Testing
5.1 Unit Testing
5.2 Navigational Testing
5.3 Functional Testing
5.4 Environmental Testing
Milestone: Testing Complete
6. Documentation

6.4 Proposed System

 Scope:
Event management is the process of planning, organizing, and executing events. The scope of event
management includes:

1. Event types :-
Event management involves managing, creating, and developing events such as corporate
conferences, weddings, festivities, formal parties, exhibitions, trade shows, product launches,
sports events, cultural festivals, charity galas, and government summits.

2. Event scope :-
The scope of an event defines its boundaries and extent, such as its duration, location, theme,
audience, and resources.

3. Event deliverables :-
Deliverables are tangible and intangible products or services that you'll provide to your attendees,
sponsors, and other stakeholders.

4. Event planning :-
Event planning involves coordinating various aspects of an event from start to finish in a timely and
efficient manner.

5. Event research :-
Event management involves a lot of research about the brand, target audience, and the concept of
the event before planning the actual event.

6. Event skills :-
Event management skills include organizational skills, along with problem-solving skills and great
communication skills.

Event management graduates can pursue careers as event planners, marketing coordinators, public
relations specialists, and more in various industries such as corporate, hospitality, entertainment,
and sports.

 Feasibility Study :

A feasibility study is a high-level capsule version of the entire System analysis and Design Process.
The study begins by classifying the problem definition. Feasibility is to determine if it’s worth doing.
Once an acceptance problem definition has been generated, the analyst develops a logical model of
the system. A search for alternatives is analyzed carefully. There are 3 parts in feasibility study.

 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, processes, output,
fields, 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 XP platform and a high configuration of 1GB RAM on Intel
Pentium Dual core processor.

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

 Operational Feasibility :

Operational feasibility is the measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development. The
operational feasibility assessment focuses on the degree to which the proposed development
projects fits in with the existing business environment and objectives with regard to development
schedule, delivery date, corporate culture and existing business processes. To ensure success,
desired operational outcomes must be imparted during design and development. These include
such design-dependent parameters as reliability, maintainability, supportability, usability,
producibility, disposability, sustainability, affordability and others.

6.5 Advantages of Proposed System

Here are the benefits of event management:

1. Meticulous Planning: Event management ensures detailed planning, covering all aspects
of an event from conceptualization to execution, leading to a well-organized and
coordinated experience.

2. Seamless Execution: Event managers excel in executing plans with precision, ensuring
that all elements come together seamlessly on the day of the event, minimizing disruptions.

3. Time and Resource Optimization: Efficient event management optimizes time and
resources, allowing for the effective allocation of budget, personnel, and logistical support
to enhance overall productivity.

4. Enhanced Creativity: Event managers bring creative flair to the planning process,
introducing innovative ideas and themes that make events memorable and engaging for
attendees.

5. Client Satisfaction: Through clear communication and understanding of client

expectations, event management aims to achieve client satisfaction by delivering events
that align with the envisioned outcome.

6. Risk Mitigation: Event managers identify potential risks and develop contingency plans,
ensuring that any unforeseen challenges are addressed promptly, reducing the impact on
the success of the event.
6.6 Data Flow Diagram (DFD)
OR
Unified Modeling Language(UML) -> Activity, Usecase, Class,
Sequence Diagram

Introduction:
 Also known as DFD, Data Flow Diagram are used to graphically represent the flow of data in
a business information system. DFD describes the processes that are involved in a system to
transfer data from the input to the file storage and reports generation.

 Data flow diagrams can be divided into logical and physical. The logical data flow diagram
describes flow of data through a system to perform certain functionality of a business. The
physical data flow diagram describes the implementation of the logical data flow.

Symbols used in DFD’s:

 External Entity
 Process
 Data Store
 Dataflow

1. External Entity:
 An outside system that sends or receives data, communicating with the system being
diagrammed.
 They are the sources and destinations of information entering or leaving the system. They
might be an outside organization or person, a computer system or a business system.
 They are also known as terminators, sources and sinks or actors. They are typically drawn on
the edges of the diagram.

2. Process:
 Any process that changes the data, producing an output. It might perform computations, or
sort data based on logic. Or direct the data flow based on business rules. A short label is
used to describe the process, such as “Submit Payment.”
 3. Data Flow:
 Files or repositories that hold information for later use, such as a database table or a
membership form. Each data store receives a simple label, such as “Orders”.

4. Data Source:
 A data source is a repository of data. An open-ended rectangle or tow horizontal parallel
lines represent it.
 A DFD, which describes the system at a very general level, is called the context diagram.
 It contains a single process, but it plays a very important role in studying the system.
 The following pages displayed the context diagram and the DFD’s of the subsequent level of
the Job4U Management System.

DFD stands for Data Flow Diagram, which is a graphical representation of how data flows through a
system or organization. It is a modeling technique used in software engineering and systems
analysis to represent the flow of data and the processes that transform the data within a system.

DFDs are composed of a set of symbols, including circles, squares, and arrows, which represent the
different components of a system and the data flows between them. The circles represent data
sources or destinations, the squares represent processes or transformations that take place on the
data, and the arrows represent the flow of data between the different components.

DFDs can be used to model both the physical and logical aspects of a system, and are often used in
the early stages of system development to help identify the requirements for a system and to
communicate those requirements to stakeholders. They can also be used to identify areas of a
system that may need improvement, or to document the current state of a system for future
reference.

 0-Level Diagram (Context Diagram):

 1st Level User Diagram:
 1st Level Organiser Diagram:
 1st Level Admin Diagram:
 2nd Level Manage Users (Admin):
 2nd Level Manage Organiser (Admin):
 2nd Level Manage Events (Admin):
 2nd Level Manage Bookings (Organiser):
6.7 Process Specification

 Login (User, Organiser & Admin) Process:

 Ratings & Reviews (User) Process:

 Feedback (User, Organiser) Process:

 Queries (Users, Organiser) Process:
 Manage Payments (Organiser) Process:
6.8 Data Dictionary

 Admin:

Name Admin

Alias -

Source Admin

Destination Main admin

Manage Users, Organiser, Events, Bookings & Payments & having all the
Description
details.

 Booking:

Name Booking

Alias -

Source Users

Destination Booking Events

User’s Event booking details like Booked Event data, date and
Description
duration, amount paid, etc.
  Organiser:

Name Organiser

Alias -

Source Organiser, Admin

Destination Organisers
Event owners & having all the details of their Events and their
Description
personal information

 Rating & Reviews:

Name Rating & Reviews

Alias -

Source Users & Ogranisers

Destination Events

Description All the Ratings & Reviews of every Events provided by users

 Users:
Name Users

Alias -

Source User, Admin

Destination Users

Description User details, Books Event according to their requirements

 Events:

Name Events

Alias -

Source Organisers

Destination Users
Events data which is provided by Organisers in which the whole Event
Description
data and expected price also available.
6.9 Table Structures

 User Details

Field Name Type Constraint

Email String Unique, Required

Mobile Number Unique, Required

Name String Required

Usertype Array Required

 Event Details

Field Name Type Constraint

Email String Unique, Required

EventName String Required

ContactNo Number Required

EventImage Image Required

EventAbout String Required

EventDate Date Required

Location String Required

TicketPrice Number Required

 Feedback

Field Name Type Constraint

UserType Array Required

description String Required

feedbackStatus String Required

title String Required

 Reviews

Field Name Type Constraint

Bookingid ObjectId Unique, Required

description String Required

rating Number Required

 Support

Field Name Type Constraint

UserType String Required

category Array Required

description String Required

queryStatus String Required

solution String Required

userid ObjectId Required

 CHAPTER: 7

Design Report
7.1 Site Diagram / Program Flow Diagram
7.2 Algorithms / E-R Diagram

 Algorithms
 E-R Diagram
7.3 Security Issues

Event management systems, like any other software platform, can be susceptible to various
security issues. Here are some common security concerns associated with event management
systems:

1. Data Breaches: Event management systems often store sensitive information such as
attendee personal details, payment information, and event schedules. A breach in the
system could lead to unauthorized access to this data, resulting in identity theft, financial
loss, or other forms of fraud.

2. Weak Authentication and Authorization: Inadequate authentication mechanisms or lax

authorization policies can allow unauthorized users to gain access to the system or perform
actions beyond their privileges. This can lead to data manipulation, service disruption, or
unauthorized transactions.

3. Insecure Communication: Unencrypted communication channels between the client and

server, or between different components of the system, can expose data to interception
and tampering. This vulnerability can be exploited by attackers to eavesdrop on sensitive
information or launch man-in-the-middle attacks.

4. Injection Attacks: Event management systems that use dynamic content or user inputs
without proper validation are susceptible to injection attacks such as SQL injection or cross-
site scripting (XSS). These attacks can allow attackers to execute malicious code, manipulate
databases, or steal session cookies.

5. Denial of Service (DoS) Attacks: Event management systems may become targets for DoS
attacks, where attackers overwhelm the system with a large volume of requests, causing it
to become slow or unresponsive. This can disrupt event registration, ticket sales, or other
critical functionalities.

6. Insufficient Logging and Monitoring: Without comprehensive logging and monitoring

mechanisms in place, it can be challenging to detect and respond to security incidents
promptly. Attackers may exploit this lack of visibility to carry out stealthy attacks or cover
their tracks effectively.

7. Third-Party Integrations: Integrating with third-party services or APIs can introduce security
risks if those services have vulnerabilities or inadequate security measures. Attackers may
exploit weaknesses in these integrations to compromise the event management system
indirectly.
 8. Insider Threats: Malicious insiders with privileged access to the event management system
can abuse their permissions to steal data, disrupt operations, or sabotage the system.
Implementing proper access controls and monitoring user activities can help mitigate this
risk.

9. Software Vulnerabilities: Like any software, event management systems may contain
vulnerabilities such as buffer overflows, insecure deserialization, or outdated libraries.
Regular security assessments, code reviews, and patch management are essential to
address these issues promptly.

10. Social Engineering: Attackers may attempt to exploit human vulnerabilities through
techniques such as phishing or pretexting to gain unauthorized access to the event
management system. Educating users about security best practices and implementing multi-
factor authentication can help mitigate this risk.

To address these security concerns, event management system developers and administrators
should follow security best practices such as implementing strong encryption, conducting regular
security audits, keeping software up-to-date, and fostering a security-aware culture within the
organization. Additionally, engaging with cybersecurity professionals for risk assessments and
penetration testing can help identify and remediate potential vulnerabilities before they are
exploited by attackers.
7.4 Input Screen Layouts

 Splash Screen
 On-Boarding Screens
 Sign-In Screen
 Sign-Up Screen
 User Side

 Home Screen
 Favourite Screen
 Show Tickets Screen (Upcoming)
Show Tickets Screen (Past)
 Profile Screen
 Logout Screen
 Feedback screen
 Organiser Side

 Home Screen
 My Event Screen
 Search Screen
 Add Event Screen
 Drawer
7.5 Output Reports

 Admin Side

 Login Screen
 Dashboard (Admin)
 All Event Show Screen
 Guest List Screen
 Event Organiser List Screen
 Supports Screen
 CHAPTER: 8

Testing Report
8.1 Test Case Design

Introduction
Software Testing is a method to check whether the actual software product matches expected
requirements and to ensure that software product is defect free. It involves execution of
software/system components using manual or automated tools to evaluate one or more properties
of interest. The purpose of software testing is to identify errors, gaps or missing requirements in
contrast to actual requirements.

Some prefer saying Software testing as a White Box and Black Box Testing. In simple terms,
Software Testing means the Verification of Application Under Test (AUT). This tutorial introduces
testing software to the audience and justifies its importance.

Objectives
There is strong evidence that effective requirement management leads to overall project cost
savings. The three primary reasons for this are:

 Requirement errors typically cost well over 10 times more to repair than other errors.
 Requirement errors typically comprise over 40% of all errors in a software project.
 Small reduction in the number of requirement errors pays big dividends in avoided rework
costs and schedule delays.

Levels of Testing
There are mainly four levels of testing in software testing:

1. Unit Testing: checks if software components are fulfilling functionalities or not

2. Integration Testing: checks the data flow from one module to other modules
3. System Testing: evaluates both functional and non-functional needs for the testing.

Each of these testing levels has a specific purpose. These testing level provide value to the software
development lifecycle.

Unit Testing
A Unit is a smallest testable portion of system or application which can be compiled, liked, loaded,
and executed. This kind of testing helps to test each module separately.
The aim is to test each part of the software by separating it. It checks that component are fulfilling
functionalities or not. This kind of testing is performed by developers.

Integration Testing
Integration means combining. For Example, In this testing phase, different software modules are
combined and tested as a group to make sure that integrated system is ready for system testing.

Integrating testing checks the data flow from one module to other modules. This kind of testing is
performed by testers.

System Testing
System testing is performed on a complete, integrated system. It allows checking system's
compliance as per the requirements. It tests the overall interaction of components. It involves load,
performance, reliability and security testing.

System testing most often the final test to verify that the system meets the specification. It
evaluates both functional and non-functional need for the testing.

Other Types of Testing:

 Regression Testing
 Buddy Testing
 Alpha Testing
 Beta Testing
8.2 Testing Issues

Testing an event management system application involves identifying and addressing various issues
to ensure the software's reliability, functionality, and user satisfaction. Here are common testing
issues and considerations specific to an event management system application:

User Interface (UI) Issues:

 Ensure that the UI is intuitive and user-friendly.
 Verify proper display and alignment of elements on different devices and screen sizes.
 Check for consistency in design and branding across all pages.

Registration and Login:

 Test the registration process for ease of use and accuracy.
 Verify secure password storage and authentication during the login process.
 Check for password recovery functionality.

Event Creation and Management:

 Verify that users can create and manage events without encountering errors.
 Test different event configurations (e.g., single-day, multi-day, recurring).
 Ensure accurate handling of date and time formats.

Ticketing and Registration:

 Test the ticket creation and registration process.
 Verify that tickets are issued correctly and that registrants receive confirmation.
 Check for the handling of sold-out events and waitlists.

Payment Processing:
 Test the payment gateway integration for different payment methods.
 Verify accurate calculation of fees, taxes, and discounts.
 Check for secure handling of sensitive payment information.

Communication and Notifications:

 Verify that users receive timely and accurate notifications (e.g., event updates, registration
confirmations).
 Test email delivery and content for correctness.

Accessibility:
 Ensure the application is accessible to users with disabilities.
  Test with screen readers and keyboard navigation.

Performance and Scalability:

 Conduct load testing to assess how the system handles a large number of simultaneous
users.
 Check response times for critical actions and pages.
 Verify that the application scales well as the user base grows.

Integration Testing:
 Test third-party integrations (e.g., payment gateways, social media sharing).
 Verify data consistency between the event management system and external platforms.

Security Testing:
 Conduct security testing to identify vulnerabilities.
 Test for secure data transmission and storage.
 Verify proper access controls and user permissions.

Cross-Browser Compatibility:
 Test the application on different web browsers to ensure consistent functionality.
 Check compatibility with various browser versions.

Mobile Responsiveness:
 Verify that the application is responsive and functions well on mobile devices.
 Test different screen sizes and orientations.

User Feedback and Surveys:

 Test feedback forms and surveys for accuracy and completeness.
 Verify that user comments and suggestions are recorded and accessible to administrators.

Localization and Internationalization:

 Test the application with different language settings.
 Verify that date and time formats, as well as currency symbols, are displayed correctly.

Data Backup and Recovery:

 Test data backup and recovery procedures.
 Verify that critical data is not lost during system failures.

Regular and systematic testing, including both automated and manual testing, is essential to
identify and address these issues throughout the development lifecycle of the event management
system application.
 CHAPTER: 9

Limitations of the Proposed

System
  Limitations of the Proposed System

There are also some limitations of the system:

 Net connection and other web related software are requiring to run thissystem.
 This limitation can be minimised by validating data using client side.
 Net connection and other web related software are requiring to run thissystem.
 The system does not have an online payment option on the online room reservation menu.
 The system is not designed to run off-line.

Identifying the limitations of a proposed event management system is crucial for understanding
potential challenges and ensuring stakeholders have realistic expectations. Here are some common
limitations that may be associated with an event management application:

1. Scalability:
 Limitation: Difficulty in scaling the system to accommodate a rapidly growing
number of events and users.
 Implication: As the user base and event load increase, system performance may
degrade.

2. Customization Constraints:
 Limitation: Limited flexibility for event organizers to customize the system according
to their specific needs.
 Implication: Users may find it challenging to tailor the application to unique event
requirements.

3. Integration Challenges:
 Limitation: Difficulty in integrating with external systems and services.
 Implication: Limited interoperability may hinder seamless data exchange with other
tools or platforms.

4. Learning Curve:
 Limitation: Complexity in the user interface and functionality leading to a steep
learning curve for event organizers and attendees.
 Implication: Users may require additional time and resources to become proficient in
using the application.

5. Dependency on Internet Connectivity:

 Limitation: Reliance on a stable internet connection for both organizers and
attendees.
  Implication: Unstable or no internet connectivity may hinder access to critical
features.

6. Data Security Concerns:

 Limitation: Potential security vulnerabilities in data storage, transmission, or
processing.
 Implication: Confidential event information and attendee data may be at risk of
unauthorized access.

7. Cost of Ownership:
 Limitation: High initial implementation and ongoing maintenance costs.
 Implication: Small or budget-constrained organizations may find it challenging to
adopt or sustain the system.

8. Limited Support for Offline Functionality:

 Limitation: Inability to access and use the application offline.
 Implication: Users may face difficulties in areas with poor or no internet connectivity.

9. Device Compatibility:
 Limitation: Limited compatibility with certain devices or operating systems.
 Implication: Some users may be excluded if the application does not support their
preferred devices.

10. Lack of Advanced Analytics:

 Limitation: Limited analytical capabilities for tracking and analyzing event
performance.
 Implication: Organizers may miss valuable insights for improving future events.

11. Regulatory Compliance:

 Limitation: Challenges in complying with data protection regulations or industry
standards.
 Implication: Legal and regulatory issues may arise, affecting the use and adoption of
the application.

12. Inadequate Support for Diverse Event Types:

 Limitation: Difficulty in handling a wide range of event types and formats.
 Implication: The application may not cater to the specific needs of certain event
organizers or industries.

13. Limited Mobile App Features:

 Limitation: Reduced functionality or usability in the mobile application compared to
the web version.
 Implication: Users relying on mobile devices may experience limitations in accessing
certain features.
 14. Reliability and Downtime:
 Limitation: Occasional system downtime or disruptions.
 Implication: Users may experience inconvenience and potential loss of data during
system unavailability.

15. Vendor Dependency:

 Limitation: Dependency on a single vendor for updates, support, and maintenance.
 Implication: Users may face challenges if the vendor experiences financial issues or
discontinues support.

It's essential to address these limitations through ongoing development, user feedback, and system
enhancements. Regular updates and improvements can help mitigate potential challenges and
enhance the overall effectiveness of the event management system.
  Types of Event Management Models

There are various event management models that organizations can adopt based on their specific
needs and the nature of the events they are organizing. Here are several types of event
management models:

1. In-House Event Management:

 Description: Organizations handle all aspects of event planning and execution
internally.
 Advantages: Complete control over the entire process, direct communication within
the organization.
 Considerations: Requires a dedicated team and resources.

2. Outsourced Event Management:

 Description: Organizations hire external event management agencies to plan and
execute events.
 Advantages: Access to professional expertise, reduced workload for the
organization.
 Considerations: Cost implications, potential loss of direct control.

3. Hybrid Event Management:

 Description: Combining in-house and outsourced elements for event planning and
execution.
 Advantages: Flexibility, leveraging internal strengths while benefiting from external
expertise.
 Considerations: Coordination challenges, need for effective communication.

4. Freemium Event Management:

 Description: Using a free or basic version of an event management platform with the
option to upgrade for additional features.
 Advantages: Cost-effective entry, flexibility to upgrade based on specific needs.
 Considerations: Limited features in the free version, potential costs associated with
upgrades.

5. Enterprise Event Management:

 Description: Deploying comprehensive event management solutions designed for
large organizations with diverse needs.
 Advantages: Scalability, centralized management of multiple events.
 Considerations: High initial setup costs, potential complexity.

6. Community-Driven Event Management:

 Description: Involving the community or target audience in aspects of event
planning and execution.
 Advantages: Enhanced engagement, community ownership.
  Considerations: Requires effective communication channels and community
involvement.

7. Agile Event Management:

 Description: Applying agile project management principles to event planning for
flexibility and responsiveness to changes.
 Advantages: Adaptability, rapid response to evolving requirements.
 Considerations: Requires a dynamic and collaborative team.

8. Project-Based Event Management:

 Description: Structuring event management as a project with defined phases and
milestones.
 Advantages: Clear project management structure, well-defined timelines.
 Considerations: Rigidity in adapting to unforeseen changes.

9. Destination Event Management:

 Description: Focused on organizing events in specific destinations or locations.
 Advantages: Expertise in local logistics and resources, unique experiences for
attendees.
 Considerations: May involve additional coordination challenges.

10. Sustainable Event Management:

 Description: Integrating sustainability practices into event planning and execution.
 Advantages: Environmental and social responsibility, positive brand image.
 Considerations: Requires conscious effort in sourcing and logistics.

Organizations may choose a model or combination of models based on factors such as the scale of
events, budget constraints, internal capabilities, and the desired level of control.
 CHAPTER: 10

Future Enhancement
  Future Enhancement

The future enhancements of an event management application can be driven by technological

advancements, industry trends, and the evolving needs of event organizers and attendees. Here are
some potential areas for improvement and future enhancements for an event management
application:

1. Artificial Intelligence (AI) Integration:

 Implement AI for personalized event recommendations based on attendee
preferences.
 Use AI-powered chatbots for real-time assistance during events.
 Analyze data to provide insights for optimizing future events.

2. Virtual and Hybrid Event Capabilities:

 Enhance virtual event features for a seamless online experience.
 Develop advanced tools for virtual networking and collaboration.
 Integrate augmented reality (AR) or virtual reality (VR) elements for immersive
hybrid events.

3. Blockchain for Security and Transparency:

 Explore blockchain technology for secure ticketing and payment transactions.
 Ensure transparent tracking of event-related transactions and data.
 Enhance security measures for attendee data protection.

4. Enhanced Mobile Experience:

 Develop a feature-rich mobile application for event management.
 Introduce mobile check-in and badge generation for on-site events.
 Utilize mobile push notifications for real-time updates during events.
5. Predictive Analytics for Event Planning:
 Use predictive analytics to forecast attendance and resource requirements.
 Analyze historical data to optimize event scheduling and venue selection.
 Implement predictive models for budgeting and resource allocation.

6. Integration with Emerging Technologies:

 Explore integration with Internet of Things (IoT) devices for smart event
management.
 Implement beacon technology for location-based services and navigation.
 Integrate with wearables for personalized attendee experiences.

7. Enhanced Networking Features:

 Develop advanced matchmaking algorithms for improved attendee networking.
 Introduce in-app messaging and collaboration tools for event participants.
 Implement features to facilitate post-event connections and networking.
 8. Green and Sustainable Event Features:
 Integrate sustainability metrics and tools for planning eco-friendly events.
 Provide options for carbon footprint tracking and offsetting.
 Encourage and reward sustainable practices among event organizers.

9. Augmented Reality (AR) for On-Site Experiences:

 Implement AR features for interactive on-site experiences.
 Offer AR-guided tours of event venues and exhibits.
 Enhance event signage and wayfinding through AR.

10. Enhanced Security Measures:

 Implement advanced cybersecurity measures to protect attendee data.
 Utilize biometric authentication for secure access control.
 Provide end-to-end encryption for sensitive communication.

11. Improved Accessibility Features:

 Enhance accessibility features for attendees with disabilities.
 Implement real-time translation services for multilingual events.
 Ensure compliance with accessibility standards.

12. Advanced Reporting and Analytics:

 Provide more in-depth analytics and reporting features for event performance.
 Integrate AI-driven insights for actionable recommendations.
 Customize reporting dashboards based on user roles and preferences.

13. Collaboration with Emerging Platforms:

 Explore partnerships and integrations with emerging social media or communication
platforms.
 Integrate with new technologies that become popular among event organizers and
attendees.

These future enhancements aim to keep the event management application at the forefront of
technological innovation and industry trends, providing a more seamless, engaging, and efficient
experience for both organizers and participants.
 CHAPTER: 11

Justifications of System as MIS

& DSS
  Justifications of System as MIS & DSS

In the context of an Event Management System (EMS), the justifications for considering the system
as both a Management Information System (MIS) and a Decision Support System (DSS) are based
on the diverse needs of event organizers and the multifaceted nature of event planning and
management:

Management Information System (MIS) Justifications:

1. Data Aggregation and Reporting:

 Justification: The MIS aspect of the event management application collects and
aggregates data from various sources, providing comprehensive reports on
attendance, revenue, and other key metrics. These reports aid in assessing the
overall performance of past events.

2. Registration and Attendee Management:

 Justification: MIS functionalities handle the registration process, maintain attendee
databases, and track participation. This ensures accurate and up-to-date information
for organizers and helps in understanding attendee demographics.

3. Logistics and Resource Management:

 Justification: MIS components manage logistical details such as venue availability,
equipment requirements, and resource allocation. This helps organizers optimize
event planning based on historical data and resource utilization.

4. Financial Tracking:
 Justification: MIS features track financial transactions, ticket sales, and budgeting
information. This allows event organizers to maintain financial transparency, analyze
revenue streams, and make informed decisions for future financial planning.

5. Operational Efficiency:
 Justification: MIS contributes to operational efficiency by streamlining routine tasks,
automating processes, and providing real-time insights into the status of ongoing
activities. This enhances overall organizational productivity.

Decision Support System (DSS) Justifications:

1. Predictive Analytics for Attendance Forecasting:

 Justification: DSS capabilities within the application can utilize predictive analytics to
forecast attendance for upcoming events. This helps organizers make informed
decisions regarding venue size, resource allocation, and marketing strategies.

2. Scenario Analysis for Resource Planning:

 Justification: DSS supports scenario analysis for resource planning, allowing
organizers to simulate different scenarios and assess the impact on costs, logistics,
 and attendee experience. This aids in contingency planning and risk mitigation.

3. Customized Marketing Strategies:

 Justification: DSS functionalities enable personalized and data-driven marketing
strategies. By analyzing attendee data and preferences, the application can
recommend targeted promotional activities, increasing the likelihood of attracting
the desired audience.

4. Real-time Decision Support During Events:

 Justification: DSS components provide real-time decision support during events,
helping organizers adapt to unexpected situations or changes in attendance. This
agility is crucial for ensuring a smooth event experience.

5. Feedback Analysis for Continuous Improvement:

 Justification: DSS tools analyze post-event feedback and surveys, providing insights
into areas of improvement. This supports continuous enhancement of future events
by addressing attendee concerns and preferences.

6. Strategic Planning for Future Events:

 Justification: DSS contributes to strategic planning by providing in-depth insights into
trends, market dynamics, and competitive landscape. This information assists
organizers in making strategic decisions for the long-term success of the event
management initiative.

By combining MIS and DSS functionalities, an Event Management Application can offer a holistic
solution that not only efficiently manages day-to-day operations but also empowers organizers with
strategic insights for future planning and decision-making.
CHAPTER: 12

References
  References

https://console.firebase.google.com/u/0/project/shoesapp-e36b6/overview
https://pub.dev/
https://firebase.flutter.dev/docs/overview/
https://stackoverflow.com/
https://app.diagrams.net/
https://medium.com/flutter

 Bibliography

 Flutter in Action by Eric Windmill.

 Beginning Flutter by Marco L. Napoli.
 Flutter for Beginners: An introductory guide to building cross-platform mobile applications
with Flutter and Dart 2 by Alessandro Biessek.
 Flutter Cookbook: Over 100 hands-on recipes to efficiently develop and manage mobile
applications with Flutter and Dart 2.0 by Fu Cheng.
 Learning Flutter: A Hands-On Guide to Building Native iOS and Android Apps Using Dart by
Paul Trebilcox-Ruiz.