GHANA COMMUNICATION TECHNOLOGY UNIVERSITY

FACULTY OF COMPUTING AND INFORMATION SYSTEMS

DEPARTMENT OF INFORMATION TECHNOLOGY

LEVEL 400 / BSC. INFORMATION TECHNOLOGY

PROJECT TITLE: DESIGN AND IMPLEMENTATION OF A STADIUM

MANAGEMENT SYSTEM

By

REYNOLDS AYISAH ANSAH 040919656

ASINOR SAMUEL OPPONG 040919568

KWATCHEY KELVIN KORATENG 040919616

SUPERVISOR:

DR. ELI FIANU

THIS PROJECT IS SUBMITTED TO THE SCHOOL OF COMPUTING AND

INFORMATION SYSTEMS, GHANA COMMUNICATION TECHNOLOGY
UNIVERSITY IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE
AWARD OF A BSC. IN INFORMATION TECHNOLOGY.

NOVEMBER 2023
 DECLARATION

This project is presented as part of the requirements for a BSc in Information Technology
awarded by Ghana Technology University College. I hereby declare that this project is entirely
the result of hard work, research, and inquires. I am confident that this project work is not
copied from any other person. All sources of information have however been acknowledged
with due respect.

AUTHOR: Asinor Samuel Oppong SIGNATURE: …………………….

STUDENT ID: 0 4 0 9 1 9 5 6 8 DATE: …………………………….

SUPERVISOR: Dr Eli Fianu SIGNATURE: ...................................

HOD: Dr William - Acquaye DATE: …………………………….

i
 ABSTRACT

This project focuses on the design and implementation of a web-based stadium

management system. The system automates various tasks involved in running a sports stadium,
including ticket sales, event scheduling, security management, and facility maintenance. The
primary aim is to enhance the overall efficiency of stadium management. This platform
provides more control over the ticketing process, ensuring better ticket availability, pricing,
and security. It also offers a user-friendly interface for purchasing tickets online, scanning them
at the venue, and a virtual assistant which is designed to interact with customers and provide
helpful information based on their queries. Additionally, the system incorporates a maintenance
tracking feature to help stadium authorities keep track of maintenance needs and schedule
repairs more efficiently. The system is developed using Django which is an open-source web
framework and MySQL database. CSS and Java Script are some other technologies used to
implement this system. A prototype model was employed to build the system, allowing for
iterative improvements and feedback gathering.

ii
 TABLE OF CONTENTS

Title Page
Declaration .................................................................................................................................. i
Abstract ...................................................................................................................................... ii
Table of contents ....................................................................................................................... iii
List of tables .............................................................................................................................. vi
List of figures ........................................................................................................................... vii
Acknowledgement ..................................................................................................................... ix
Chapter One: Introduction...................................................................................................... 1
1.1 Background to Study......................................................................................................... 1
1.2 Statement of the Problem .................................................................................................. 5
1.3 Aim & Objectives.............................................................................................................. 6
1.4 Significance of the Study .................................................................................................. 6
1.5 Organization of the Study ................................................................................................. 7

Chapter Two: Literature Review............................................................................................ 8

2.1 Introduction of Stadium management system ................................................................... 8
2.2 Ways in which technology can improve Stadium Management Systems ........................ 8
2.2.1 Technologies used in stadium management system................................................... 9
2.2.1.1 Database management system........................................................................ 10
2.2.1.1 Cloud Computing ........................................................................................... 10
2.3 Features of stadium management system ......................................................................... 12
2.3.1 Essential features..................................................................................................... 12
2.3.2 Advanced features ................................................................................................... 13
2.4 Critical component of stadium management system......................................................... 13
2.4.1 Online ticketing system .......................................................................................... 14
2.4.1.1 Review of Online ticketing system .......................................................... 16
2.5 Success factors for stadium management system.............................................................. 19
2.5.1 User friendly interface............................................................................................ 19
2.5.2 Customer service .................................................................................................... 19
2.5.3 Security and privacy… ........................................................................................... 19
2.6 Summary of literature review............................................................................................ 20
2.7 Proposed system ................................................................................................................ 20
iii
Chapter Three: Methodology, System Specification and Design....................................... 23
3.1 Overview ............................................................................................................................ 23
3.1.1 Methodology ............................................................................................................... 23
3.1.1.1 Justification for chosen methodology ............................................................... 24
3.2 System Requirement Specification..................................................................................... 26
3.2.1 Functional Requirements............................................................................................. 27
3.2.1.1 Admin ................................................................................................................. 27
3.2.1.2 User .................................................................................................................... 27
3.2.2 Non-Functional Requirements .................................................................................... 28
3.3 System Specification .......................................................................................................... 29
3.3.1 Hardware Requirements .............................................................................................. 29
3.3.2 Software Requirements ............................................................................................... 29
3.4 System Design.................................................................................................................... 29
3.4.1 Use case diagram.......................................................................................................... 29
3.4.2 Entity relationship diagram ......................................................................................... 31
3.4.3 Data flow diagram ....................................................................................................... 33
3.4.4 Sequence diagram ........................................................................................................ 33
3.4 System Architecture ........................................................................................................... 35

Chapter Four: System Implementation................................................................................ 36

4.1 Introduction ........................................................................................................................ 36
4.2 Implementation challenges ................................................................................................. 36
4.3 Technologies used .............................................................................................................. 37
4.3.1 Python .......................................................................................................................... 37
4.3.2 JavaScript .................................................................................................................... 37
4.3.3 MySQL ........................................................................................................................ 37
4.3.4 Django ......................................................................................................................... 38
4.4 Interface design ............................................................................................................. 38
4.4.1 Login pages ............................................................................................................ 39
4.4.2 Customer view ........................................................................................................ 40
4.4.3 Super Admin Panel ................................................................................................. 46
4.4.4 Staff Panel .............................................................................................................. 47
4.5 Testing ........................................................................................................................... 53

iv
 4.5.1 Testing stages ......................................................................................................... 53
4.5.2 Testing plan ............................................................................................................ 54
4.5.3 Testing cases ......................................................................................................... 55

Chapter Five: Conclusion and Recommendation ................................................................ 56

5.1 Objectives and Achievements ........................................................................................... 56
5.2 Problems Encountered....................................................................................................... 56
5.3 Lessons Learnt................................................................................................................... 57
5.2 Future Development .......................................................................................................... 57

REFERENCES ....................................................................................................................... 58
Appendix A: Installation guide and System Requirements...................................................... 62
Appendix B: Test Cases ........................................................................................................... 69
Appendix C: Sample Codes ..................................................................................................... 77
Appendix D: User Evaluation .................................................................................................. 86

v
 LIST OF TABLES

Table 4.1: Testing plan ............................................................................................................. 54

Table B.1: Test case – CreateAccount01 ................................................................................. 68
Table B.2: Test case – Login01................................................................................................ 69
Table B.3: Test case – Login02................................................................................................ 70
Table B.4: Test case – Permission01........................................................................................ 71
Table B.5: Test case – User01.................................................................................................. 72
Table B.6: Test case – Edit01................................................................................................... 72
Table B.7: Test case – Event01 ................................................................................................ 73
Table B.8: Test case – Refund01 ............................................................................................. 74
Table B.9: Test case – Parkinglot01......................................................................................... 75
Table B.10: Test case – Asset01 .............................................................................................. 75
Table B.11: Test case – Maintenance01 ................................................................................... 76

vi
 LIST OF FIGURES

Figure 2.1: Ticketmaster.com website ..................................................................................... 16

Figure 2.2: egoTickets.com website........................................................................................ 17
Figure 2.3: Studhub.com website ............................................................................................. 18
Figure 3.1: Prototype model..................................................................................................... 24
Figure 3.2: Use case diagram for the user ................................................................................ 30
Figure 3.3: Use case diagram for the admin and staff .............................................................. 31
Figure 3.4: ERD diagram ......................................................................................................... 32
Figure 3.5: Data flow diagram ................................................................................................. 33
Figure 3.6: Sequence diagram .................................................................................................. 34
Figure 3.7: System architecture diagram.................................................................................. 35
Figure 4.1: MVC diagram ........................................................................................................ 38
Figure 4.2: Login page for users .............................................................................................. 39
Figure 4.3: Login page for super admin ................................................................................... 39
Figure 4.4: Signup page for user .............................................................................................. 40
Figure 4.5: Available events in concert category ..................................................................... 40
Figure 4.6: Available events in sports category ....................................................................... 41
Figure 4.7: Event and booking details...................................................................................... 41
Figure 4.8: Payment page ......................................................................................................... 42
Figure 4.9: Confirmation page of ticket .................................................................................. 42
Figure 4.10: Customer personal information ........................................................................... 43
Figure 4.11: Transaction history for customer ......................................................................... 43
Figure 4.12: Customer dashboard ............................................................................................ 44
Figure 4.13: Customer reserve parking space .......................................................................... 44
Figure 4.14: Event search......................................................................................................... 45
Figure 4.15: Chatbot................................................................................................................. 45
Figure 4.16: Groups and available permission ......................................................................... 46
Figure 4.17: Total number of customers .................................................................................. 46
Figure 4.18: Total number of staff members............................................................................ 47
Figure 4.19: Record of events and actions within the system .................................................. 47
Figure 4.20: Staff dashboard .................................................................................................... 48
Figure 4.21: Adding events ...................................................................................................... 48

vii
Figure 4.22: List of events ....................................................................................................... 49
Figure 4.23: Ticket sales .......................................................................................................... 49
Figure 4.24: Parking space ....................................................................................................... 50
Figure 4.25: Add parking lot .................................................................................................... 50
Figure 4.26: Stadium assets...................................................................................................... 51
Figure 4.27: Add asset .............................................................................................................. 51
Figure 4.28: Schedule maintenance dashboard ........................................................................ 52
Figure 4.29: Add maintenance ................................................................................................. 52
Figure 4.30: Tickets refund ...................................................................................................... 53
Figure A.1: Python interpreter download interface .................................................................. 62
Figure A.2: Node.js download interface .................................................................................. 62
Figure A.3: Stadium management system folder ..................................................................... 64
Figure A.4: Backend and frontend folders ............................................................................... 65
Figure A.5: Backend files......................................................................................................... 65
Figure A.6: Starting Django server .......................................................................................... 66
Figure A.7: Starting backend server using command prompt .................................................. 66
Figure A:8: Starting frontend server using command prompt ................................................. 67
Figure B.1: Account created successfully ................................................................................ 69
Figure B.2: Invalid login attempt occurred .............................................................................. 70
Figure B.3: Admin edit user information ................................................................................. 73

viii
 ACKNOWLEDGMENT

First and foremost, I want to express my heartfelt gratitude to my supervisor, Dr. Eli
Fianu, for his constant support throughout this project. His comments, encouragement,
patience, enthusiasm, extensive knowledge, and guidance have been invaluable to me. I am
truly grateful for his mentorship.
We would also like to extend my thanks to all my lecturers at Ghana Communication
Technology University. Their dedication and expertise have greatly contributed to my
knowledge and professional growth during my time at the university.
Furthermore, we would like to express our deepest gratitude to God for His blessings,
guidance, and unwavering presence throughout this project. His divine support has been a
source of strength and inspiration for me.
In addition, we would like to extend my sincere appreciation to our esteemed colleague
for their unwavering support during the implementation stage of this project.
Finally, we must express my very profound gratitude to my mother and my relations for
providing me with unfailing support and continuous encouragement throughout my years of
study and through the implementation of the project and writing this thesis. This
accomplishment would not have been possible without them.

ix
 CHAPTER ONE

INTRODUCTION

1.1 Background to Study

A stadium is a structure that surrounds a central field or stage in which a spectator event
takes place. It includes seating for viewers to stand or sit, as well as other amenities to enhance
the spectator experience (Cambridge Dictionary, 2023).
A stadium is a specially constructed facility that can accommodate large numbers of
people during organized sporting events, as defined by FIFA. The design of a stadium takes
into account numerous factors that enhance the audience's enjoyment of the sporting event.
Shin and Lyu's (2019) research paper suggest that the physical environment of sports facilities
plays a vital role in stimulating sports fans' attendance intentions and encouraging repeat visits,
particularly in developed nations.
A stadium management system is a software application that automates tasks related to
running a sports stadium, such as managing ticket sales, scheduling events, ensuring security,
and maintaining the stadium's facilities. The system streamlines operational activities to
improve the stadium's management efficiency. Sports teams or venue operators can implement
stadium management systems to streamline stadium or arena management. The software can
improve efficiency, reduce costs, and enhance the fan experience by providing real-time
information on event schedules, seating availability, and other relevant details.
According to Xu's (2017) research paper, China has constructed over 80 stadiums in
Africa with a total capacity of nearly 3 million spectators. The largest stadium in Africa, Soccer
City, is located in Johannesburg, South Africa, and can hold up to 94,000 people. During the
opening ceremony of the 2010 FIFA World Cup, over 90,000 people were in attendance at this
stadium. These stadiums in Africa are versatile and host sporting events such as football, as
well as non-sporting events like musical concerts and other entertainment events.
Governments and sports departments worldwide have constructed stadiums to help
organize sporting events, enabling people to buy tickets and attend games to cheer on their
favorite teams across various sports. According to Dominik and Payam's (2022) research paper,
stadium attendance demand is critical for business leaders in the professional sports sector.
Barcelona Football Club’s stadium is the largest in Europe, with a capacity of 99,500
spectators. The stadium's official annual report indicates that it accounts for 19% of all club
revenues, amounting to €194 million by the end of the 2018-2019 season. The club's official.

1
report also reveals that the average attendance during the 2021-2022 season was 55,026, with
the highest average attendance being 86,422.
In the past, stadium managers relied on outdated technology to manage stadium
operations, such as manual ticket recording and data storage. However, with the evolution of
technology, most stadium managers in Europe are now adopting new technologies to meet the
changing needs of their fans. Application programming interfaces (APIs) enable developers to
create systems that utilize stadium information, such as schedules for sporting events or
concerts, seating charts, and mobile ticketing systems.
Stadiums have seen significant changes in their management systems since the 1990s.
Early systems relied on proprietary hardware and software for ticket sales and access control.
However, modern stadium management systems have become more centralized and integrated
with the advent of computer technology, allowing spectators to connect with stadium
administrators through the Internet using their devices. These systems connect people, goods,
and services and provide content and services that spectators can enjoy at the stadium. Modern
systems can handle everything from ticket sales to concession management and provide fans
with real-time information, such as seat location and wait times. Today's systems incorporate
real-time analytics, predictive maintenance, and mobile ticketing.
According to Kenneth and Jane (2016), enterprise-wide information systems have
enabled managers to make accurate and timely decisions by accessing important information
online almost instantly. These systems are relied on by over 21 million managers and 154
million workers in the information and knowledge sectors of the United States to conduct their
business. There are various types of stadium management systems currently in use. The most
common include ticketing systems, security systems, crowd control systems, facility
maintenance systems, and event management systems.
Ticketing systems are essential for managing ticket sales and distribution and can enhance
the experience for both fans and event organizers. By integrating with other stadium
management systems, ticketing systems can provide a more seamless experience for fans.
Several European stadiums have developed custom ticketing systems that cater to their specific
needs, such as Old Trafford in Manchester, Johan Cruyff Arena in Amsterdam, Camp Nou in
Barcelona, and Signal Iduna Park in Dortmund. In Africa, some stadiums have their own
ticketing systems, while others may use commercial ticketing systems. The Ghana Football
Association (2022) announced that an e-ticketing system will be used for the purchase of
advance tickets for the MTN FA Cup final match at the Accra Sports Stadium.

2
 Stadiums in Europe prioritize the safety and security of attendees by implementing a
range of security features such as CCTV monitoring, access control systems, and emergency
response systems. Due to concerns over terrorism and security threats, many stadiums have
increased their security measures in recent years. FIFA has mandated that all stadiums need to
have a fully integrated safety and security strategy that covers the entire structure and its
surroundings. Security measures in African stadiums are dependent on the stadium, with some
having more advanced security features like CCTV monitoring and access control systems.
Unique security challenges, such as political instability, can also impact the level of security
required in some African stadiums.
Facility maintenance involves the processes and activities that enable organizations to
derive maximum utility from their commercial buildings, encompassing the assets and
equipment within and around the structure (Jonathan, 2021). It is a crucial component of
stadium management systems, ensuring that stadiums are safe, comfortable, and functional for
their intended purposes. Most sports stadiums worldwide employ facility maintenance to keep
their facilities in good working condition. However, in Ghana, public infrastructure such as
stadiums, offices, and the national theater is in poor condition, posing safety hazards to the
public (Chen et al, 2018). These issues are attributed to the over-centralization of maintenance
decisions.
Event scheduling is a crucial element in stadium management systems. It enables
stadium managers to plan and organize events, allocate resources, and coordinate with event
organizers. There are various event management systems used worldwide, including
Eventbrite, Cvent, RegOnline, and Bizzabo. These platforms provide features such as
registration, marketing, and analytics to help event organizers manage their events, such as
games, concerts, and other performances. Ticketpro and Webtickets are popular in South Africa
and other parts of the world.
Stadium management systems provide several benefits to stadium operators. They offer
features such as online ticketing, mobile apps, and in-seat ordering that can enhance the fan
experience. They provide tools for marketing, ticketing, and concessions management that can
help increase revenue. They offer access control and emergency response features that can
enhance security. They facilitate better management of data related to ticket sales, attendance,
and other metrics. They provide tools for scheduling and maintenance that can streamline
operations.
Most of the football clubs in Europe offers stadium tours that allow visitors to book ticket
online and explore the stadium, learn about its history and architecture, and visit the stadium’s

3
museum. These tours are often led by knowledgeable guides who provide information about
the stadium’s design, construction, and use.
In Africa, some of the football clubs, including Kazier Chiefs, Orlando Pirates, and Al
Ahly offer online stadium tours and ticket book options. This can increase revenue through
booking fees to cover the cost of running the tour, such as staffing and maintenance expenses.
According to a video on CitiTube (2019), the Egyptian club Al Ahly gave a tour of their
facilities to Ghanaian sports journalist Fentuo Tahiru.
The largest multi-purpose stadium in Ghana is the Baba Yara Sports Stadium, which can
seat up to 40,528 people. It was built in 1957 by the United African Company and is primarily
used for football matches, but it also hosts athletics, concerts, politics, and cultural events.
Other stadiums in Ghana include Accra Sports Stadium, Tamale Sports Stadium, Sekondi
Sports Stadium, and Ho Sports Stadium. These stadia have different seating capacities and are
also used for non-sports events such as cultural and comedy events. Most of the stadia in Ghana
are publicly funded by the municipal and local governments.
To improve fan attendance in the 2016/2017 football season, the Ghana Football
Association (G.F.A) organized a seminar for club administrators on strategies to attract fans to
Stadia. According to pioneering research undertaken by the African Sports Center in 2019,
there was a higher attraction to stadium attendance (58%).
The computerized ticketing system at Ghana's stadiums has been inefficient since the
first stadium was built. The National Sports Authority (NSA) is responsible for funding and
maintaining these stadia. During events, security personnel only allow people with tickets to
enter the stadium area. To make tickets more accessible, event organizers sell them at outlets
near the stadium on the day of the event.
In Ghana, event organizers and promotional teams advertise upcoming events like
football games on radio and TV stations. Tickets are usually printed and distributed to various
outlets such as shopping malls, restaurants, and filling stations. Additionally, people can
purchase tickets on online ticketing platforms such as eGotickets.
Fake ticketing is a significant issue in Ghana, particularly in the entertainment industry
and sports industry. However, there have been reports of counterfeit tickets being sold, as two
individuals believed to be Nigerians were arrested on March 24th, 2022 for allegedly selling
fake tickets to the match between the Blackstars and the Super Eagles at the Baba Yara
Stadium, according to a video on KofiTv (2022). This fraudulent activity not only hurts the
revenue of event organizers but can also endanger the safety of attendees. Implementing an

4
automated ticketing system with proper security measures can help prevent fake ticketing and
ensure a safe and enjoyable experience for all attendees.
This project will involve the design and Implementation of a Computerized Stadium
Management System which will be able to generate and deliver electronic tickets, store, locate
or retrieve information, when necessary, schedule events, and other operational activities.

1.2 Statement of problem

Ticketing is a crucial aspect of stadium management, as it is typically the primary source
of revenue for venues. As a result, many stadium management systems prioritize ticketing
functionality, such as online ticket sales, seat selection, and ticket scanning. In Ghana, fans can
purchase tickets for stadium events through ticketing platforms like eGotickets or USSD.
However, the lack of a custom-built ticketing platform specifically designed for stadium events
in Ghana is a significant issue. Reliance on other platforms to sell tickets can result in a lack of
control over the ticketing process, leading to problems with ticket availability, pricing, and
security. Fans who purchase tickets via USSD face several disadvantages, including a time-
consuming process, limited availability on mobile devices, and the potential for fraud or other
illegal activities. These issues can hurt the ticketing process for stadium events in Ghana.
The problem with managing facility maintenance in the stadium management system is
that it can be challenging to keep track of maintenance needs across different parts of the
stadium. According to reports filed by Ghana Soccer Net (2023), the Aliu Mahama Sports
Stadium is in poor condition due to a lack of maintenance, despite requiring major renovation
every ten years. The VVIP section's roof, toilet facilities, and popular stands need repair.
Stadium management systems, such as Ticketmaster, eGotickets, Paciolan, and
Ticketek, offer valuable services to improve stadium operations, including ticketing,
marketing, customer relationship management, and venue management. However, there is still
a gap to be addressed. For example, eGotickets, used in Ghana, require customers to contact
customer service or wait for bank processing for refunds, which is inconvenient. Additionally,
systems like Paciolan, eGotickets, and Ticketek lack a user dashboard to display monthly and
weekly spending, making it difficult for users to monitor their expenses.
A proposed system could address these gaps by providing a user-friendly platform that
allows customers to easily request refunds, track their spending, and receive a refund through
their ticketing account. The system could also offer a dashboard that displays monthly and
weekly spending, making it easier for users to monitor their expenses. Additionally, the system
could offer a chatbot or AI assistant that can assist customers with their inquiries and provide

5
customer support, reducing the need for customers to contact customer service. Overall, the
proposed system could offer a more efficient and convenient experience for customers,
improving stadium operations and customer satisfaction.

1.3 Aims and Objectives

This project aims to design and implement a computerized stadium management system.
It will be able to achieve the following objectives.
● To design a system that manages customer information and details of the previous
transaction.
● To design an online system for ticket sales and payment.
● To implement a prototype of a design system.
● To ensure the system is user-friendly.
● To test the developed system to ensure all proposed functions were met.
● To provide a Chatbot or AI assistant to assist customers with their inquiries and
provide support.
● To test the module to ensure that it accurately displays customer refunds and updates
in real-time.
● To develop a database that stores maintenance records and track progress over time
● To develop a database that can be used to manage employee records and track
employee performance.

1.4 Significance of study

The implementation of a new stadium management system that addresses the gaps in
existing systems, such as the lack of a user dashboard and inconvenient refund processes,
would significantly improve the overall customer experience. By providing users with a
dashboard to display their monthly and weekly spending, the new system would enable
customers to monitor their expenses and make informed decisions about their purchases.
Additionally, by streamlining the refund process and providing customers with a more
convenient way to request refunds, the new system would increase customer satisfaction and
loyalty.
This system helps provide an accurate data storage and retrieval system for easy
manipulation of information about employees, such as their job titles, roles, and contact
information. This helps keep track of employee attendance and monitor their punctuality. This

6
system also maximizes efficiency and throughput with virtually no need for human
intervention.
With this system, users can fill out and purchase their tickets in a faster and more
convenient way than by queuing for hours to purchase tickets. It also helps to eradicate
overcrowding issues at the stadium.

1.5 Organization of the Study

This study is organized into five chapters. Chapter one consists of the general
introduction which includes; the background of the study, a statement of the problem, aims and
objectives, the significance of the study, and the organization of the study. Chapter two is the
literature review which demonstrates knowledge and understanding of the academic literature
on a specific topic placed in context. Chapter three is the system specification which includes
the system requirements, system architecture, user interface design, and use cases. Chapter four
is the system implementation defines how the information system should be built and also
ensures that the system is operational and meets the quality standard. Chapter five will contain
a summary of findings, a discussion of findings based on the themes from the conclusions,
recommendations, and suggestions for further research.

7
 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction of Stadium Management System

Stadiums have been around since ancient Greece and Rome, where they were utilized
for athletic competitions and other public events. As time has progressed, stadiums have
become more sophisticated, incorporating advanced technologies and design elements to create
a better fan experience and promote sustainability (Ekaterina and Michel, 2020).
Technology has played an increasingly important role in transforming stadium
management in recent years. By leveraging technological advancements, stadium managers
have been able to improve the overall experience for attendees, optimize operational processes,
and enhance security measures (Global Sports Innovation Center, 2019). This literature review
examines the current state of stadium management systems, focusing on the latest technological
advancements, best practices, and challenges facing stadium managers. By analyzing existing
literature, this review aims to provide insights into the key factors that contribute to the success
of stadium management systems.
The review will explore the role of technology in stadium management systems, the
features that are essential to a successful system, and the critical components of a stadium
management system. Additionally, the review will propose a new system and analyze the
success factors that are critical to the development and implementation of a stadium
management system. By analyzing the current state of stadium management systems, this
review aims to provide a comprehensive understanding of the role of technology in stadium
management and identify areas for future research.

2.2 Ways in which technology can improve Stadium Management Systems

Stadium management systems have become increasingly complex in recent years, as
stadiums have evolved from simple venues for sporting events to full-fledged entertainment
complexes. Stadiums are no longer just sporting venues but multi-purpose venues (Chub and
Kreizer, 2020). The efficient management of these systems is critical to the success of the
stadium, as it can have a direct impact on the fan experience, stadium operations, and revenue
generation.
Mobile applications are among the most popular technologies used to enhance the fan
experience in stadiums (Glebova and Michel, 2020). These apps provide real-time information
on parking, seating, concessions, and other amenities, making it easier for fans to navigate the

8
stadium. They also collect data on fan behavior and preferences, which can help stadium
managers improve their services and offerings. According to Yilmaz et al (2022), SeatGeek is
a mobile application that enables fans in the United States to purchase tickets and discover
seating options for events at stadiums and arenas. In addition, VenueNext is an app that
provides real-time information on parking and seating for the stadium.
Mobile apps are gaining popularity in the sports industry as they offer a convenient
way for fans to access information and services related to the stadium and events. One of the
key benefits of mobile apps and web applications is the consolidation of all services and data
in a single platform, which helps stadium managers provide a seamless experience for fans
and improve their overall experience (Schut and Glebova, 2022).
Analytics software optimizes stadium operations by analyzing data from various
sources, such as customer feedback and ticket sales, to reveal insights into customer behavior,
preferences, and trends. Stadium staff can use analytics software to visualize trends and make
data-driven decisions for long-term planning (Intel, 2016). Smart stadiums require a mix of
hardware, software, and wireless connectivity to establish communication links between
stadium operators and fans and to collect and analyze data using cloud infrastructure (Intel,
2016). IBM Sports Insight, SAS Sports Analytics, and Tableau are cited by Roy (2017) as
examples of analytics software used in stadium management systems.
Digital signage is a technology that enhances the fan experience and generates revenue
for the stadium. According to Lee et al. (2019), stadium signage has become standard
advertising in the sports industry, benefiting both the sports organization and the sponsor. The
introduction of digital signage has evolved stadium advertising. Recent stadiums use digital
boards to display the signage of a single sponsor as close to the viewer's field of view as
possible, creating a bigger impact on the audience (Lee et al, 2022). Digital signage provides
real-time information on parking, seating, and amenities to help fans navigate the stadium more
easily. It also displays advertisements and promotions, generating revenue for the stadium.

2.2.1 Technologies used in stadium management system

Database management systems and cloud computing are critical technologies utilized
in stadium management. These technologies enable stadium managers to enhance the fan
experience and streamline operational processes. This analysis seeks to explore the influence
of database management systems and cloud computing on stadium management systems.

9
2.2.1.1 Database management system
Database technology has significantly influenced the widespread use of computers.
Databases play a crucial role in storing and managing vast amounts of data, which is vital for
numerous computer applications (Elmasri and Navathe, 2010). According to Satinda and
Aditya (2017), a database is a collection of interrelated data that is stored together with
controlled redundancy to serve one or more applications in the best possible way.
A database management system (DBMS) is a software tool designed to help maintain
and utilize large collections of data, and its significance is increasing rapidly as organizations
increasingly rely on data to make informed decisions (Raghu and Johnnes, 2019).
The first general-purpose database management system (DBMS) was developed in the
early 1960s by Charles Bachman at General Electric. This system was called the Integrated
Data Store and formed the basis for the network data model. IBM developed the Information
Management System (IMS) DBMS in the late 1960s, which is still used today in many major
installations (Raghu and Johnnes, 2019). DBMSs have entered the Internet Age, and using a
DBMS to store data that is accessed through a web browser is becoming widespread. Queries
are generated through web-accessible forms and answers are formatted using a markup
language such as HTML. Database vendors are adding features to their DBMS aimed at making
it more suitable for deployment over the Internet (Raghu and Johnnes, 2019).
Elmasri and Navathe (2010) state that traditional database applications refer to those
where the majority of the information is stored and accessed in either textual or numeric format.
Stadium management systems typically use traditional databases to store and manage
structured data such as customer information, ticket sales, and stadium maintenance records.
According to Ghosal et al (2015), when a user books a ticket, the SQLite database stores the
geographic locations of the source and destination, ticket type, and booking date. This data can
be accessed and manipulated by authorized personnel to help manage the stadium and improve
the fan experience.
Stadium management systems store unstructured data in addition to structured data.
Unstructured data examples include photos, videos, and social media posts related to the
stadium or its events. Alternative data storage methods like NoSQL databases are used to
manage unstructured data (Dipanjan, 2016).

2.2.1.2 Cloud Computing

Cloud computing is a powerful technology that allows users to access computing
resources quickly and easily, regardless of their location or time zone. With cloud computing,

10
users don't need to worry about setting up infrastructure, purchasing new equipment, or
investing in licensed software. Instead, they can access any amount of computing resources,
large or small, for a nominal fee (Sandeep, 2017). According to Rashid and Chartuverdi (2019),
cloud computing refers to the practice of storing and accessing data and programs over the
Internet, rather than on a computer's hard drive.
Stadium management systems are now cloud-based and hosted on remote servers, which
makes them more flexible, scalable, and cost-effective than traditional on-premise systems.
Users can access the system via a web browser or mobile app, and all data is stored on the
remote servers. In a stadium management system, the three layers of cloud computing would
be Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service
(SaaS).
According to Mahdi et al. (2021), Infrastructure as a Service (IaaS) involves the
distribution of servers as a service, including storage, network, and operating systems. In this
model, the cloud provider is responsible for providing an imaginary computer that already has
the operating system installed and configured. At the Infrastructure as a Service (IaaS) layer,
the cloud provider would provide fundamental computing resources, such as virtual machines
and storage, to the stadium management system. This would enable the stadium to store and
analyze vast amounts of data related to ticket sales, concessions, and other aspects of stadium
operations.
In computing, platform as a service (PaaS) is the underlying system over which
applications run. The platform consists of the physical computing device (hardware) loaded
with layer(s) of software where the program or application can run. (Sandeep, 2017). At the
PaaS layer, the cloud provider would offer a platform for developing and deploying
applications specific to the stadium management system. This could include tools for managing
ticket sales and other aspects of stadium operations.
The Software as a Service (SaaS) layer provides fully functional software applications that
can be accessed over the Internet. These applications are hosted on the cloud provider's servers
and can be accessed by users through a web browser or mobile app. Cloud computing can help
stadiums operate more effectively by providing access to advanced technologies like data
analytics, artificial intelligence, and machine learning, which can help stadiums optimize
operations and improve the fan experience (Mahdi et al, 2021).

11
2.3 Features of stadium management system
Stadium management systems consist of two categories of features: essential and
advanced. Essential features include ticketing, access control, and facility maintenance, while
advanced features include real-time reporting and analytics, security management, and parking
management. The main goal of these features is to streamline processes, increase efficiency,
and enhance the overall fan experience (Christopher, 2018).

2.3.1 Essential features

Ticketing is a critical feature of stadium management systems as it allows administrators
to manage ticket sales for events, including setting prices, creating seating arrangements, and
tracking sales. This feature ensures that fans can purchase tickets easily and efficiently, which
is essential for the success of any event. According to Cakmak and Ciftci (2019), in Turkey,
spectators who want to attend football matches in stadiums are required to purchase tickets
electronically and link them to their Passolig card. This process is mandatory for all attendees
and helps to streamline the entry process, ensuring that the match starts on time.
The Access control system is also an essential feature of a stadium management
system. This feature enables administrators to manage the flow of people in and out of the
stadium, ensuring safety and security. The system can provide real-time data on the number
of people in the stadium, which can help administrators make informed decisions and
improve the overall fan experience.
Cakmak and Cifti (2019) state that there was an increase in incidents in the tribunes in
Turkey from the 2000s, and existing laws were not sufficient to prevent them. Law No. 6222
on Prevention of Violence and Disorder in Sports was published on April 14, 2011, and
introduced severe penalties for those involved in violent acts. The law also required
individuals who want to watch football matches in the tribune to have an electronic card.
Access control measures can help to prevent individuals who may be involved in violent acts
from entering the stadium by ensuring that only individuals with valid electronic cards are
allowed to enter.
A facility maintenance system is another essential feature of a stadium management
system. The system should be able to track and manage maintenance tasks, equipment, and
inventory. It should also be able to schedule and track preventive maintenance activities, such
as inspections and repairs, to ensure that facilities are in good condition and ready for events.
According to Kameli et al. (2019), effective facility maintenance requires managing a large
amount of information and data, including equipment, maintenance schedules, and work

12
orders. A comprehensive facility maintenance system can help streamline the process of data
management and ensure that the right information is available to the right people at the right
time.
Stadium management systems use analytics to track various aspects of events, including
ticket sales, attendance, and revenue. By analyzing this data, administrators can gain insights
into the success of events and make informed decisions about pricing, marketing, and event
planning.

2.3.2 Advanced features

Stadium management systems have an advanced feature called security management
which ensures the safety and security of the stadium, staff, and fans. This feature includes
surveillance cameras and security personnel. CAF (2019) highlights the critical role of ensuring
the safety and security of everyone involved in a stadium for the success of the sport, including
players, officials, fans, and other stakeholders.
Stadium management systems have advanced analytics features that include real-time
data analysis, predictive analytics, and machine learning algorithms for crowd management
and security. Caulfield et al (2022) state that some stadiums have implemented customer-facing
technology, while others have focused on the backend by using analytics to cut costs and
streamline operations. Croke Park in Dublin, Ireland, is an example of the latter approach,
where machine learning algorithms were used to predict when to light the pitch with heat lamps
for optimal growth, resulting in reduced costs for the stadium owners and an improved fan
experience (Smart Dublin, 2016).
Another advanced feature of stadium management systems is parking management,
which ensures a smooth and efficient parking experience for fans by using digital parking
passes and real-time parking availability updates. Advanced parking management features can
create a more seamless and enjoyable fan experience, ultimately leading to greater success for
the venue and the organization.

2.4 Critical component of stadium management system

The online ticketing system is a critical component of the stadium management system.
The stadium management system is a complex system that requires several components to
ensure its smooth operation. The online ticketing system is one of these critical components.
This system enables fans to purchase tickets online, making the ticketing process more efficient
and convenient. By implementing the online ticketing system, stadium managers can better

13
manage ticket inventory, reduce the risk of a black market, and provide a more secure way for
fans to purchase tickets.

2.4.1 Online ticketing system

Digital ticketing is when people buy, store, and show tickets for events using digital
technology. Instead of getting a paper ticket, customers can get an electronic ticket that they
can save on their phone or computer.
Kim et al (2022) found that both internal and external stimuli can positively predict the
intention to continue using digital tickets. However, the study also revealed that only internal
motivation has a positive effect on the intention to continue through service satisfaction.
E-ticket selling is the most appropriate way to overcome problems, satisfy the spectators,
and earn money. Jubair et al. (2019) noted that purchasing tickets at ticket counters in the
stadium can be time-consuming. However, with advancements in technology, it is now possible
to purchase tickets online, which can save time and make the process more convenient.
Narimani et al. (2017) found that the sale of e-tickets through websites has significantly
increased over the years. In 1999, e-ticket selling was only worth three hundred million dollars,
but by 2004, it had risen to 3.9 million dollars. Jupiter also reported that e-ticket sales via the
Internet increased from 45 million dollars in 2002 to half a million dollars in 2007.
According to Narimani et al. (2017), e-ticket selling is the most appropriate way to
overcome problems, satisfy spectators, and earn money. E-tickets provide a more convenient
and efficient way for people to purchase tickets, which can increase ticket sales and reduce
the likelihood of counterfeit tickets. Additionally, e-tickets can provide valuable data to
organizers, which can help them better understand their audience and improve their
marketing strategies.
Nazarian (2023) research revealed that the conventional method of purchasing tickets in
Iran is through the box office, which can be a time-consuming process and lead to a black
market where tickets are sold at inflated prices due to high demand. Although the box office
system is still valuable for generating revenue for venues, new technologies such as online
ticketing can make the process more efficient and reduce the risk of a black market. Ali et al.
(2023) also support this idea, emphasizing that online ticketing systems can offer a more
convenient and secure way for fans to purchase tickets, while also enabling venues to manage
their ticket inventory and pricing more effectively.
The e-ticket selling of Football League matches is a significant indicator for the Asian
Football Confederation, and it has the potential to significantly enhance the fan experience. In

14
Iran, online sales are the exclusive method of purchasing tickets for all league matches at Azadi
Stadium (Narimani et al, 2017). Narimani et al. (2017) also explain that for Premier League
clubs in Iran to be responsible for selling tickets for their teams, they must have their
stadiums. Unfortunately, most clubs in Iran do not have this essential feature.
Passolig is a smart card system introduced in 2014 to enhance security and prevent
violence at football matches in Turkey. Fans must purchase a Passolig card and register their
personal information to buy tickets. Spectators who want to watch football matches in stadiums
are required to purchase tickets electronically through this system and link the tickets to the
Passolig card (Eturan-Ogut, 2020; Gohkan and Sevda, 2021). The system aims to prevent the
unauthorized sale of tickets and monitor fan behavior to improve safety and security (Gohkan
and Sevda, 2021). According to Eturan-Ogut (2019), the Passolig card was introduced to enable
online ticket purchasing and stadium entrance systems through the designated bank, Aktif
Bank. Furthermore, the card also allows the government to have surveillance and control over
stadiums.
Ghana's National Sports Authority partnered with a private ticket vendor and Ghana.gov
to launch e-ticketing for sports events, according to a Ghana Web report. Fans could easily
purchase game tickets using mobile money via the shortcode (*711#) and obtain a unique code,
which they presented on game day to gain stadium admission (GhanaWeb, 2022). In Ghana,
Ego Tickets, an e-ticketing platform, provides an easy and convenient way for fans to purchase
tickets for sporting events, concerts, and other events
Jubair et al (2019) propose an Automated Stadium Attendance Management system that
includes a barcode to check the validity of tickets. Tickets are scanned by mobile phones, and
the system updates the database with ticket information such as seat number, block number,
match date, and attendance time. It calculates the amount of audience entry into the stadium
and displays their seats. If the ticket is not valid, the scanner application warns the gate guard.
Users can also update the attendance data of the system from their smartphones.
According to Li (2023), RFID technology and barcodes are frequently used in intelligent
ticketing systems to enhance data security and identify electronic ticketing information. The
ticket inspection service of these systems can utilize RFID card readers and barcode scanners
to simplify the ticket inspection process and bolster stadium security. Nughara et al. (2021)
conducted a study to enhance the design of a multi-sport event ticket accounting information
system by incorporating RFID and blockchain technologies to enforce COVID-19 health
protocols. The study revealed that the effectiveness of tickets for spectators was hindered by
budget and environmental issues.

15
2.4.1.1 Review of existing ticketing system

• Ticket-Master
Ticketmaster Entertainment, Inc. is an American-based company that distributes and
sells tickets. In 2010, it merged with Live Nation to form Live Nation Entertainment (Jeremy
and Yinka, 2015). Ticketmaster offers ticketing services for concerts, sports events, theater
performances, and other events. It operates in numerous countries worldwide, making it one of
the largest ticketing platforms globally.
TicketMaster is a widely used ticketing platform for stadiums, arenas, and other venues
across the United States. Some of the most famous venues that use TicketMaster include
Madison Square Garden, Staples Center, and the O2 Arena, but many other venues also use
TicketMaster for ticketing services.
Ticketmaster has various features and capabilities that are similar to those found in
stadium management systems. These functionalities are designed to help venues manage ticket
sales, event scheduling, and other aspects of event planning and management. The homepage
of Ticketmaster is shown in Figure 2.1.

Figure 2.1: ticketmaster homepage

One key strength of Ticketmaster is its user-friendly platform. The Ticketmaster website
and mobile app are easy to navigate, allowing consumers to efficiently purchase tickets for
events. Steve (2023) reports that Ticketmaster has implemented several features, like seat maps
and alerts, to enhance the ease of purchasing tickets.

16
 Another strength of Ticketmaster is its customer service. Ticketmaster has a dedicated
customer service team that is available to assist customers with any issues or questions they
may have.
Ticketmaster's refund procedure for canceled events may be a weakness as it may
consume a considerable amount of time and be frustrating for customers. Customers may have
to navigate Ticketmaster's website or contact customer support to request a refund, which can
contribute to the inconvenience of the canceled event.

• EgoTickets
eGotickets is an online ticketing platform that enables customers to purchase tickets for
events and experiences. It provides a convenient way for customers to buy tickets from their
homes, while also assisting event organizers in managing ticket sales and attendance. Although
primarily used in African countries, such as Ghana, Nigeria, South Africa, and Kenya,
eGotickets is available for use in other regions too. The platform is widely used for ticketing
events at various venues in Ghana, including the Accra International Conference Centre, the
National Theatre, Fantasy Dome, and various stadiums (egoTickets, n.d). The homepage of
eGoTickets is displayed in Figure 2.2.

Figure 2.2: egotickets ticketing platform homepage

eGotickets is a user-friendly platform that simplifies event creation and management for
organizers, and ticket purchasing for customers. Along with the platform, eGotickets developed
Checkpoint, a mobile app that scans and validates tickets using Android or iOS devices, and

17
provides real-time attendance metrics. Additionally, eGotickets provides event organizers
access to event analytics and customer data that can be used to evaluate the success of an event
and make informed decisions for future events.
eGotickets is primarily used in African countries, which could limit its appeal to
customers and event organizers in other regions. This could be particularly problematic for
events that have an international audience or for event organizers who want to reach a wider
audience beyond their local area.

• Studhub
StubHub is a ticketing platform that provides ticket purchasing and resale services for
sports organisations. Sports fans can use StubHub to buy tickets for sports events, as well as
to sell tickets they no longer need. StubHub offers a wide range of tickets for sports events,
including football, basketball, baseball, and hockey games. Figure 2.3 displays the homepage
of StubHub.

Figure 2.3 studhub ticketing platform homepage

The center is a multi-purpose sports and entertainment facility in Carson, California,

and it hosts a variety of events throughout the year, including soccer matches, concerts, and
other live events. As part of the naming rights agreement, StubHub became the official
ticketing partner of the Los Angeles Galaxy, and the company's branding was prominently
featured throughout the center.
One of the strengths of StubHub is its wide selection of tickets for sports events,
concerts, and other live events. The platform offers a marketplace where fans can buy and
sell tickets, which means that there is always a variety of tickets available for different events.

18
Another strength of StubHub is its user-friendly interface and mobile app, which make it easy
for fans to search for and purchase tickets on the go.
One of the weaknesses of StubHub is that the platform does not offer refunds for tickets
that are purchased but not used. This means that if a buyer is unable to attend an event, they
will not be able to get a refund for their ticket.

2.5 Success factors of stadium management system

2.5.1 User friendly interface

A user-friendly interface is a critical success factor for stadium management systems.
It ensures that administrators can easily manage events and that fans can purchase tickets and
access information quickly and efficiently. A well-designed interface will enhance the user
experience and make it easier for fans and administrators to navigate the system. A user-
friendly interface can include features such as clear and concise labeling, intuitive navigation,
and responsive design.
Universal design is a design process that aims to create products that can be used by
as many people as possible, regardless of their age, ability, or other characteristics (Alan et
al, 2004). The goal of universal design is to create products (stadium management systems)
and environments that are accessible and usable by everyone.

2.5.2 Customer service

Good customer service is a critical success factor for stadium management systems.
By providing excellent customer service, stadium management systems can help to ensure
that fans have a positive experience and are more likely to return for future events. This can
involve clear and timely communication, prompt addressing of customer concerns and
complaints, and assisting with ticketing and other issues.

2.5.3 Security and privacy

Security and privacy are crucial success factors for stadium management systems.
Stadiums are often crowded places with a high risk of security incidents, so it is vital to
ensure that the system is secure and can protect against threats such as cyberattacks, theft,
and violence. During a 2018/2019 NPFL Playoff match between Kano Pillars and Rangers
FC, a violent incident occurred when charging fans attacked the Referee due to the gates
leading to the field being left open (Yusuf et al, n.d.).

19
 Many important soccer leagues are using various applications to provide security in
stadiums. For example, soccer stadiums in England use closed-circuit television applications
for crowd management. At Leeds United stadium, police officers are stationed in a
windowless room with a series of video-monitors in front of them, controlling any part of the
stands with zoomable cameras. These measures have proven to be effective in ensuring the
safety of fans and preventing violent incidents (Eraslan et al, 2023).
Additionally, privacy is becoming increasingly important, and customers want to know
that their personal information is being protected. According to Eturan-Ogut (2020), fans in
Turkey were worried that the government could use the detailed personal information they
provided to the bank through the introduction of passolig (electronic ticketing system) to
blacklist them. To address this issue, governments and companies must be transparent about
how personal information is collected, used, and protected.

2.6 Summary of literature review

The literature review highlights the importance of stadium management systems and
how technology can improve them. The introduction of stadium management systems has made
it easier to manage various aspects of stadium operations. The use of technologies such as
database management systems and cloud computing can enhance the capabilities of these
systems.
The review also discusses the essential and advanced features of stadium management
systems, including online ticketing systems. The proposed system must have a user-friendly
interface, excellent customer service, and robust security and privacy measures. Overall, the
literature review emphasizes the need for effective stadium management systems to ensure a
positive experience for customers and efficient operations for stadium management.
The literature review will impact the design of the proposed stadium management system
by providing valuable insights into the essential and advanced features that should be
incorporated into the system. This means that the review will guide the design of the system to
ensure that it is effective, efficient, and customer-focused.

2.7 Proposed system

While there is a current stadium management system in place, we believe that our
proposed system offers many benefits over the current system. Our system will use modern
technologies and best practices in stadium management to provide a more efficient, secure,
and customer-friendly experience. The proposed system will include a comprehensive

20
ticketing system, a customer relationship management system, a staff management system, a
facility maintenance system, a parking management system, and an analytics system. By
implementing this system, we aim to improve security, reduce wait times, enhance customer
experiences, and increase revenue for the stadium. We believe that our system will be a
significant improvement over the current system and will provide a better overall experience
for customers, staff, and management.
The ticketing system streamlines the process and enhances the customer experience.
Customers can purchase tickets online through a comprehensive ticketing system. They can
choose seats and access their tickets via a web application, without needing physical tickets.
The system ensures that only valid tickets are used for stadium access by validating them using
barcode scanning or other technologies. It provides customer support for ticketing issues,
including technical support and assistance with refunds and exchanges.
A CRM system can enhance customer engagement, loyalty, and satisfaction in stadium
management. The proposed system can maintain customer data, including contact information,
purchase history, and preferences, in a centralized database. It can also track customer
interactions and feedback to provide insights into customer behavior and preferences.
Our proposed system includes a facility maintenance application designed to help
facility managers and maintenance teams manage the maintenance of the stadium's buildings,
equipment, and assets. The system provides a centralised location to manage work orders,
schedule preventative maintenance, manage inventory, and generate reports. The system
tracks the maintenance history of assets, schedules routine maintenance, and generates
reports on asset performance.
The parking management feature includes a system for managing parking spaces and
permits. Only ticket holders can request a parking space. The system can prompt users to enter
their ticket ID before they can request a parking space. The system can then verify the ticket
ID and only allow access to the parking request feature if the ticket is valid. This can help
ensure that only fans who have purchased tickets can request parking spaces, which can help
prevent unauthorized parking and improve overall parking management.
Our proposed stadium management system will include an analytics system that
generates insights and predictions to help us make informed decisions about optimizing
stadium operations. The system will use data from various sources, such as ticket sales data, to
train machine learning algorithms and statistical models.
The proposed stadium management system includes a sign-up module that allows new
users to register for an account and a sign-in module that ensures only authorised users can

21
 access the system. The homepage provides an overview of available events and allows users
to purchase tickets. Users can print tickets as PDFs, which is useful for generating hard copies
of tickets or distributing them to fans who prefer a physical copy. Additionally, the user
dashboard displays information such as the daily amount of money spent on tickets, which
helps users keep track of their spending and make informed decisions about future purchases.
Our stadium management system has a refund module that enables customers to get a
refund if an event is canceled. This feature ensures that customers do not incur financial losses
in case of event cancellation. By offering this service, we can foster trust and loyalty with our
customers, which can lead to increased revenue and repeat business.
Our proposed stadium management system categorises tickets based on the type of
event, such as sporting events, concerts, and comedy shows. This categorisation allows fans
to quickly and easily find tickets for the type of event they are interested in attending. By
providing clear and specific categories, we can improve the overall user experience and
increase ticket sales.
Our proposed stadium management system offers a search bar feature that enables users
to buy tickets. Users can enter specific keywords related to the event they want to attend, such
as the performer's name, team, or venue. This feature provides a quick and efficient way for
users to find and purchase tickets for their desired event.
Users of the system can edit their profile information within the system, which allows
them to update their personal information and preferences as needed. This feature ensures that
users can keep their profiles up-to-date and accurate, which can help to improve the overall
user experience.
The admin has control over user registration and authentication, event creation and
management, ticket sales, and customer support and assistance. Additionally, the admin can
assign roles to other users of the system, such as facility managers, cashiers, and other staff
members, to ensure that each user has the appropriate level of access and responsibility.

22
 CHAPTER THREE

METHODOLOGY, SYSTEM SPECIFICATION AND DESIGN

3.1 Overview
This chapter provides an overview of the process involved in designing the stadium
management system. The development of this system requires a systematic approach to ensure
that it meets the needs of its users and stakeholders. The chapter describes in detail the
procedures taken to design and develop the system, including the requirements-gathering
process, system analysis, and design. It also highlights the functional and non-functional
requirements of the system, covering both user and system requirements.
The primary objective of our project is to build a stadium management system that
enables stadium managers to manage stadium operations, including ticket sales, event
scheduling, and asset maintenance, efficiently and effectively. The system will provide users
with a user-friendly interface that is easy to navigate, while also ensuring that data is secure
and accessible only to authorized personnel. To achieve our project goal, we adopted an
iterative model. This model includes stages such as requirements gathering, system design,
implementation, testing, and maintenance. By the end of this chapter, readers will have a
comprehensive understanding of the design process for the stadium management system and
the key considerations that were taken into account.

3.1.1 Methodology
According to Ian (2016), there is no universal process model that is right for all kinds of
software development. The right process depends on a variety of factors, including customer
and regulatory requirements, the environment where the software will be used, and the type of
software being developed. There are various software process models, such as the Waterfall
model, the Agile model, and the Spiral model, each with its advantages and disadvantages.
The selection of the process model should be based on the project's specific needs and
requirements.
The Waterfall model is a linear, sequential approach that suits projects with well-defined
requirements. Agile is iterative and best for projects with changing requirements. Spiral is risk-
driven and ideal for large and complex projects. Software development is not a one-time event,
and the process model should be adjusted as the project progresses. The process model should
be reviewed and revised regularly to ensure that it is still meeting the project's needs and

23
requirements. The Iterative model is a cyclical approach that involves breaking the software
development process into smaller, more manageable pieces.

3.1.1.1 Justification for chosen methodology

The prototyping model is an iterative development methodology that allows for
continuous improvement and customer feedback. This model is ideal for building the stadium
management system because it enables us to reduce the risks associated with the final product
and provides a clear understanding of the system requirements.
Developing a working model that can be tested and refined based on customer feedback
is one of the main advantages of the prototyping model. This iterative process enables us to
identify and address issues early on in the development process, reducing the risks associated
with the final product.
Another advantage of the prototyping model is that it provides a clear understanding of
the system requirements. By developing a working prototype of the system, we can better
understand the requirements of the stakeholders and ensure that the final product meets their
needs. The prototyping model also enables early detection of errors and issues. By testing the
prototype early on in the development process, we can identify and address errors and issues
before they become more costly to fix. Figure 3.1 displays the prototyping model

Figure 3.1 prototyping model diagram

The phases of the prototype methodology include:

• Requirements gathering: For a stadium management system, requirements gathering in
the prototyping model would involve gathering information from stakeholders such as
stadium owners, event organizers, and fans. This may involve conducting interviews,

24
 surveys, or focus groups to determine what features and functionality the system should
have, such as ticketing, facility management, and parking.
• Quick design: Quick design in the prototyping model requires creating a preliminary
system design based on the requirements collected during the requirements-gathering
phase. For a stadium management system, this would entail creating a preliminary system
design based on the requirements gathered from stakeholders. This process may involve
creating sketches or wireframes of the user interface and determining the data needed to
support the system.
• Building a prototype – This involves creating a functional version of the system based on
the requirements gathered during the requirements gathering phase and the quick design
phase. For a stadium management system, building a prototype would involve creating a
functional version of the system based on the wireframes and data requirements and
functionality such as ticketing, facility maintenance, parking, and other features. The
prototype would be tested to ensure that it meets the needs of stakeholders and can be
refined and improved as necessary. Once the prototype is finalized, it can be used as the
basis for building the final version of the system.
• Testing – Testing a prototype in the prototyping model involves evaluating the functional
version of the system created during the prototype phase to ensure that it meets the needs
of stakeholders. For a stadium management system, testing the prototype would involve
evaluating the features and functionality of the system, such as ticketing, facility
maintenance, parking, and other aspects, to ensure that they meet the needs of stakeholders.
• Refining - To refine the system, improvements are made based on feedback received
during the testing phase. For a stadium management system, this would involve refining
features and functionality, such as ticketing, facility maintenance, and parking, to meet
stakeholder needs. The prototype is improved as necessary based on feedback received
during testing. Once finalized, it is used as the basis for building the final version of the
system.
• Maintenance – In the case of a stadium management system, maintenance would involve
correcting any errors that were not discovered earlier, such as issues with ticketing or
facility management. It would also involve improving the implementation of system units,
such as making it easier for fans to purchase tickets or for event organizers to manage
parking. Additionally, maintenance would involve enhancing the system's services as new
requirements are discovered, such as adding new features to the system based on feedback

25
 from stakeholders. This would ensure that the system continues to meet the needs of its
users and remains functional and reliable over time.

3.2 System Requirement Specification

The system requirements specification is a document that outlines the functional and
non-functional requirements of a software system. It is used to communicate the needs of
stakeholders, including end-users, developers, and testers, and to ensure that the system is
designed, developed, and tested according to those needs.
To derive the requirements for this project, a systematic approach followed to derive the
requirements for this project includes:
• Feasibility study - A significant amount of time was dedicated to conducting a detailed
feasibility study. This study focused on assessing the practicality of developing the desired
stadium management system in terms of implementation, cost constraints, and meeting the
deadline. The goal was to determine if the software product could be successfully
materialized. The output of this study is a feasibility study report that includes thorough
analysis, comments, and recommendations on whether or not the project should proceed.
• Requirement gathering - A comprehensive approach was used to gather insights and
prioritize system requirements. Surveys, interviews with past attendees, and observations
of stadium operations were conducted. The collected data was carefully analyzed to
determine key requirements and prioritize them. Based on the requirements gathered, it
appears that most of the respondents in the survey believe that an online ticketing system
is a crucial component of the stadium management system. This feedback can be used to
prioritize the development of this feature and ensure that it is user-friendly and accessible
for all fans. Other features such as facility management and parking can also be developed
based on the feedback gathered from stakeholders.
• Categorization - After gathering the information, the next step was to analyze it and
identify common themes and requirements. This involved organizing and categorizing the
requirements into functional and non-functional aspects.
• Documentation - Throughout the process, I documented the requirements in the system
requirements specification document, ensuring clear and concise communication of the
derived requirements to all stakeholders. This document serves as a reference point for the
design, development, and testing phases of the software system.

26
3.2.1 Functional Requirements
Functional requirements refer to the specific features and capabilities that the system
must have to perform its intended functions. These requirements describe what the system
should be able to do in order to support the stadium's operations and provide a positive
experience for fans and customers. The functional requirements for a stadium management
system include:

3.2.1.1 Admin
• User management: The admin should be able to create, modify, and delete user accounts.
• Event management: The admin should be able to create, modify, and delete events.
• Ticket management: The admin should be able to manage ticket inventory, set prices, and
track sales.
• Seating management: The admin should be able to manage seat availability.
• Parking management: The admin should be able to manage parking availability and
generate parking maps.
• Facility management: The admin should be able to manage physical assets and
infrastructure of the stadium, such as maintenance.
• Employment management: The admin should be able to manage employee data and track
employee attendance.
• Permission: The admin should be able to assign roles to other users on the system and also
ensure that every user has the appropriate level of access and permissions.

3.2.1.2 User
• User account creation: Users should be able to create an account on the system, providing
their name, email address, and other relevant information.
• Event browsing: Users should be able to browse upcoming events and view information
about each event, including date, time, location, and ticket prices.
• Ticket purchasing: Users should be able to purchase tickets for events, selecting the
number of tickets they want and the seating location (if applicable)
• Payment processing: Users should be able to pay for their tickets using a secure payment
system that accepts multiple forms of payment.
• Ticket delivery: Users should be able to receive their tickets via email or other digital
delivery method.

27
• Seat selection: If applicable, users should be able to select their seats from a seating chart
or similar interface.
• Parking reservation: Users should be able to reserve parking for events, selecting the
location and number of parking spots they need.
• Account management: Users should be able to view and modify their account information,
including their name, email address, and password. The Users should be able to view their
total amount of money spent on tickets and total amount of refunded tickets on the
dashboard.
• Support: Users should be able to contact customer support for help with any issues or
questions they have about the system or their tickets.
• Transaction History - The users should be able to view their entire ticket purchasing
history, including any booked parking spaces.

3.2.2 Non-Functional Requirements

Non-functional requirements refer to the system's characteristics and constraints that
are not directly related to its functionality but still play a crucial role in determining its
overall success. The Non-functional requirements for a stadium management system
include:
• Security: The system must have role-based access control to ensure that only authorized
personnel can access sensitive data or perform certain actions within the system.
• Performance: The system must be able to include response time, throughput, and resource
utilization. These requirements ensure that the system can handle the expected load and
provide a satisfactory user experience.
• Reliability: The system should be always accessible and can recover from unexpected
errors or failures. The system must be available 95% of the time and must be able to recover
from any failure within a short period.
• Usability: The system should be designed with the end-users in mind, and should be
accessible to people with varying levels of technical expertise. Additionally, the system
should provide clear and concise instructions, feedback, and error messages to help users
navigate the system.

3.3 System Specification

System specification refers to a detailed description of the hardware, software, and other
components that make up a system. It outlines the requirements for the system, including its

28
features, capabilities, and performance characteristics. System specification is an important
part of the system development process, as it ensures that all stakeholders have a clear
understanding of what the system is supposed to do and how it is supposed to do it.

3.3.1 Hardware Requirements

• Computer system.
• Processor: 1 gigahertz (GHz) or faster with two or more cores on a compatible 64-bit
processor system on a chip.
• Memory: 4 gigabytes (GB) or greater.
• Storage: 10 GB or greater available disk space.

3.3.2 Software Requirements

• Operating System: Windows 10 and higher.
• Programming Languages: Javascript, Phyton.
• Application Program: MySQL Workbench, XAMPP.
• Text Editor: Visual Studio, Notepad++, Sublime etc.
• Web Browser: Microsoft Internet Explorer, Google Chrome.

3.4 System Design

The stadium management system requires careful planning and design to ensure that it
is efficient, effective, and user-friendly. In this system design, we will be exploring the different
components of the stadium management system, including the use case diagram, entity
relationship diagram, sequence diagram, and data flow diagram. Each of these components will
help us understand how the system works, how data flows through the system, and how
different components interact with each other to perform various tasks.

3.4.1 Use case diagram

The use case diagram identifies the different actors and their roles in the system. It shows
the different ways that users interact with the system and the different tasks that they can
perform. The use case diagram helps to visualize the system's functionality from a user's
perspective and provides a high-level overview of the system's behavior. It can be used to
identify and define the system's requirements, understand the system's scope, and communicate
with stakeholders. The use case diagram for the user is typically shown in Figure 3.2, while the
use case diagram for the admin is usually shown in Figure 3.3.

29
Figure 3.2: Use case diagram for the user

30
 Figure 3.3: Use case diagram for the admin and staff

3.4.1 Entity relationship diagram

An ERD is a visual representation that displays how information is created,
stored, and utilized in a business system (Dennis et al, 2012). By reviewing an ERD, an
analyst can identify the specific pieces of information in the system and understand how
they are structured. The ERD diagram for the system is typically shown in Figure 3.4.

31
Figure 3.4: Entity relationship diagram

32
3.4.2 Data flow diagram
A data-flow diagram is a way of representing a flow of data through a process or a system
(usually an information system). The DFD also provides information about the outputs and
inputs of each entity and the process itself. The data flow diagram for the system is typically
shown in Figure 3.1

Figure 3.5: Data flow diagram

3.4.1 Sequence diagram

Sequence diagrams illustrate the interactions that occur between actors and the
system, as well as interactions between various components of the system (Ian, 2016).
Figure 3.1 shows the sequence diagram of the system.

33
Figure 3.6: Sequence diagram

34
3.5 System Architecture
Software architecture is a set of principles that define the way software is designed and
developed. Architecture defines the structure of the software system and how it is organized.
It also describes the relationships between components, levels of abstraction, and other aspects
of the software system. The system architecture for the system is typically shown in Figure 3.7
In a stadium management system, the web server acts as the initial point of contact for
customer, admin, and staff requests. These requests are then redirected to the appropriate
modules within the application server. The application server hosts modules such as ticketing,
parking, facility, event, and employee, each handling specific functionalities and business
logic.

Figure 3.7: System architecture diagram

35
 CHAPTER FOUR

SYSTEM IMPLEMENTATION

4.1 Introduction
This chapter delves into the implementation phase of the Stadium Management System.
Implementation involves transforming the detailed design outlined in the previous chapter into
a functional program, along with its supporting activities. The primary objective is to create a
working program that meets the project's requirements. Developers encounter various
challenges during implementation, including integration, scalability, security, performance
optimization, user interface development, error handling, and efficient data management.
Successful execution relies on collaboration, coordination, and thorough testing. Once
implemented and tested, the system can be deployed to effectively manage stadium operations.

4.2 Implementation Challenges

• Integration: Integrating software with external entities, such as libraries, databases, and
other programs, can be a challenge during implementation. This process involves
connecting system components, bringing together different subsystems, and linking
databases and file-based systems to ensure smooth operation and achieve consistent results.
• Error handling: Error handling can be a challenging aspect of implementing a system. It
involves anticipating and managing errors or exceptions that may occur during system
operation. Effective error handling includes identifying potential errors, implementing
error detection mechanisms, and providing informative error messages to users. In a
stadium management system, error handling could involve handling situations such as
ticket scanning errors, and payment transaction errors.
• User interface: User interface development can present several challenges during
implementation. These challenges include ensuring a responsive and visually appealing
design across different devices and screen sizes, creating an intuitive and user-friendly
interface, handling complex user interactions and workflows, and maintaining consistency
throughout the system.
• Data management: One of the challenges we encountered when implementing a stadium
management system is ensuring scalability to accommodate increasing data volumes and
user traffic. As the system grows, it needs to handle larger amounts of data and support a
higher number of concurrent users without experiencing performance issues.

36
4.3 Technology used
The technology used in building the stadium management system includes Python,
Django, MySql, and JavaScript. These technologies work together seamlessly to provide
efficient management of various aspects.

4.3.1 Python
Python is chosen as the high-level programming language for building the stadium
management system due to its versatility and extensive library support. Python's simplicity and
readability make it easier to develop and maintain the system's codebase. Additionally, its wide
adoption in the tech industry ensures a large community of developers who can contribute to
the system's development and provide support. Python's compatibility with other technologies
allows for seamless integration with different components of the stadium management system,
making it a reliable and efficient choice for building such a complex system.

4.3.2 JavaScript
JavaScript is a programming language that is primarily used for adding interactivity and
dynamic features to web applications. In the context of the stadium management system,
JavaScript plays a crucial role in enabling the creation of dynamic and interactive user
interfaces. It allows for real-time updates, form validation, and handling user events, enhancing
the overall user experience. JavaScript's versatility and compatibility with different web
browsers make it an essential component for building modern and engaging web applications,
including the stadium management system.

4.3.3 MySQL
MySQL, on the other hand, is a relational database management system (RDBMS) that
is commonly used with web applications. It provides a structured way to store and retrieve data,
using tables with rows and columns. MySQL is known for its reliability, scalability, and
performance, making it a popular choice for many web applications, including the stadium
management system.
In the context of the stadium management system, MySQL would be used as the backend
database to store information about stadiums, events, ticket sales, and other relevant data. It
would handle tasks such as creating tables, inserting, updating, and retrieving data, and
optimizing queries for efficient data retrieval.

37
4.3.4 Django
Django is a widely used Python web framework that follows the model-view-controller
(MVC) architectural pattern. MVC is a design pattern that separates an application into three
interconnected components: the model, the view, and the controller.
In the context of the stadium management system, Django's MVC structure allows for
efficient handling of user authentication, database management, and HTTP requests. It
simplifies development by providing pre-built components and promoting code reusability.
With Django, developers can create secure and efficient web applications, making it an ideal
choice for building the stadium management system. Figure 4.1 displays the diagram of MVC.

Figure 4.1: Model View Controller Diagram

• The model represents the data and the business logic of the application. It handles data
storage, retrieval, and manipulation.
• The view is responsible for presenting the data to the user and receiving user input. It
provides the user interface and interacts with the model to display and update data.
• The controller acts as an intermediary between the model and the view. It processes user
input, updates the model, and communicates with the view to reflect changes in the user
interface.

4.4 Interface Design

Interface design refers to the process of creating the visual and interactive elements of a
software application or website that users interact with. It focuses on designing an interface
that is user-friendly, visually appealing, and enhances the overall user experience.

38
4.4.1 Login pages
In Figure 4.2, the login page of the system is displayed. The login page is the initial entry
point for users to access the system. It typically includes input fields for users to enter their
credentials, such as a username and password. The login page ensures that only authorized
users can access the system, providing a layer of security. It also includes options for password
recovery and account creation for new users. The login page for the super admin is displayed
in Figure 4.3. The signup page of the system is displayed in Figure 4.4

Figure 4.2: Login Page for the users

Figure 4.3 Login page for super admin

39
 Figure 4.4 Signup page for user

4.4.2 Customer View

The customer view in a stadium management system refers to the interface design that
allows customers to interact with the system. It typically includes features such as:
• Ticket purchasing - The customer can browse events, select events, check event details,
and proceed to check out. Figure 4.5 shows the available events in the concerts category,
figure 4.6 events in the sports category, Figure 4.7 shows the event details and booking,
Figure 4.8 shows the payment page, Figure 4.9 shows the confirmation page of the ticket
purchase.

Figure 4.5: Available events in concert category

40
Figure 4.6: Available events in sports category

Figure 4.7: Event details and booking

41
 Figure 4.8: Payment page

Figure 4.9: Confirmation page of the ticket

• Account management - This includes tasks such as creating an account, updating personal
information, changing passwords, and managing preferences. Account management
ensures that users can easily access and modify their account details as needed. Figure 4.10
shows the interface where users can access and manage their personal information.

42
 Figure 4.10: Customer access personal information

• Transaction history – In Figure 4.11, the transaction history feature allows customers
to view the details of their ticket purchases. It shows a record of their past transactions,
including date, time, action, and status. This helps customers keep track of their
ticketing activities and provides a convenient way to review their purchase history.

Figure 4.11: Transaction history for customer

43
• Dashboard - In Figure 4.12, the customer dashboard displays the total number of
tickets purchased as well as the total number of ticket refunds.

Figure 4.12: Dashboard for customer

• Parking space - In Figure 4.13, the interface allows customers who have purchased a
ticket to select their desired parking space. To reserve a parking space, customers need
to enter their ticket ID. This feature ensures that only valid ticket holders can reserve a
parking spot, providing a secure and convenient parking experience.

Figure 4.13: Customer reserve for parking space

44
• Event search - Event search is a feature that allows customers to find specific events
based on their preferences. Figure 4.14 showcases the event search feature designed
specifically for customers. It provides an intuitive interface to easily search for events.

Figure 4.14: Event search at customer side

• Customer Support - Customer support with a chatbot is a fantastic way to provide

assistance and address customer queries. In Figure 4.15, the chatbot allows customers
to choose a subject related to parking, ticket, or refund.

Figure 4.15: Chatbot

45
4.4.2 Super Admin Panel
The super admin in the stadium management system is like the top-level administrator.
They have access to all the features in the system, and they have even more features than the
regular admin. Some of these extra features can only be accessed by the super admin. Some of
the features accessible only to the super admin include:
• Authentication and Authorization - Authentication verifies the identity of a user, while
authorization controls their access to features and tasks. One way to achieve this is by
creating groups and assigning permissions to them. In Figure 4.16, you can see the interface
that displays the groups created by the super-admin, the available permissions, and the
chosen permissions for each group. This allows different groups to have access to specific
features and perform tasks within the system.
• Users - The super admin can view the total number of users on the system, which includes
both customers and staff. Figure 4.17 displays the total number of customers, while Figure
4.18 displays the total number of staff members. These figures help the super admin track
the user base and system growth.

Figure 4.16: Groups and available permission

Figure 4.16: Total number of customers

46
 Figure 4.18: Total number of staff numbers
• Audit log - The audit log is a record of events and actions within a system. In Figure
4.19, it shows the recent actions that occurred within the system. The audit log captures
important information about user activity and system events.

Figure 4.19: record of events and action within a system

4.4.2 Staff Panel

The staff members in the stadium management system, who are like top-level managers,
have access to a variety of important features and can handle crucial tasks. Some of the features
accessible to the staff include:

47
• Dashboard - The admin interface dashboard shows the total number of users, total
ticket sales, and new sales. Figure 4.20 displays this dashboard.

Figure 4.20: Staff Dashboard

• Event management - The staff can add events to the system. Figure 4.21 displays the
interface they use to add events, while Figure 4.22 shows the list of events that have
been added by the staff. It's a handy way for the staff to manage and keep track of all
the events

Figure 4.21: Adding events

48
 Figure 4.22 List of events

• Ticket management - The staff members can handle various tasks related to ticket
management, including ticket sales, ticket inventory management, and even ticket
refunds. The interface displayed in Figure 4.23 provides a clear overview of ticket sales
and allows staff to easily track customer purchases.

Figure 4.23: Ticket sales

• Parking management - The staff members can oversee and manage parking
operations, including assigning parking spaces, and tracking availability. Figure 4.24
displays events in the stadium management system with the parking spaces created.

49
 This feature allows the staff to efficiently manage parking operations by assigning
designated parking spaces for attendees. Figure 4.25 displays the interface for adding a
parking lot.

Figure 4.24: Parking space

Figure 4.25: Add Parking lot

• Assets - The staff can add assets for the stadium. Check out Figure 4.26 to see the
interface that shows these stadium assets. Figure 4.27 displays the interface where the
staff adds assets to the stadium.

50
 Figure 2.26: Stadium assets

Figure 2.27: Add asset

• Maintenance - The staff can schedule maintenance for the added asset. Figure 2.28
displays the interface of the scheduled maintenance of the asset with a dashboard of
completed tasks, works in progress, and pending tasks. Figure 4.29 displays the
interface where the staff schedules maintenance of the assets

51
 Figure 2.28: Schedule maintenance dashboard

Figure 2.29: Add maintenance

• Refund - The staff can process refunds for customers who have purchased tickets.
Figure 2.30 shows the interface for processing ticket refunds by the admin, and it also
displays the total amount of money refunded for the tickets.

52
 Figure 2.30: Tickets refund

4.5 Testing
Testing plays a crucial role in ensuring that a program functions as intended and helps
identify any defects before it is deployed for actual use (Ian, 2016). The two main goals of
testing are to confirm that a program performs its intended functionality and to uncover any
defects or issues before it is implemented.

4.5.1 Testing stages

The testing stage refers to a phase in the software development process where the
program or system is evaluated to ensure that it functions correctly and meets the specified
requirements. In the stadium management system, various testing stages are utilized to ensure
its effectiveness and reliability. These stages may include:
• Unit testing - Unit testing is an important part of software development where
individual components, such as the event module in a stadium management system, are
tested in isolation. It helps ensure that each component functions correctly before they
are integrated into the larger system. For instance, in the event module, we would test
the functionality of creating, updating, and deleting events separately to identify and
fix any issues or bugs.
• Integration testing - Integration testing is an important part of software development.
It involves testing the interaction between different modules, such as the event module
and the refund module in a stadium management system. By simulating scenarios and

53
 verifying the communication and functionality between these modules, integration
testing ensures that they work together seamlessly, providing a smooth and reliable
experience for event management and refund processing.
• System testing – System testing is the process of evaluating the entire system as a
whole to ensure that it meets the specified requirements and functions correctly. For
example, in a stadium management system, system testing checks if tickets are issued
and validated correctly, events are scheduled and managed properly, refund requests
are processed accurately, and maintenance tasks are executed effectively. By doing
system testing, we ensure that all the modules work together smoothly, meeting the
requirements and providing a reliable stadium management system.

4.5.2 Testing plan

The testing plan is a crucial document that outlines the strategies, objectives, and scope
of the testing process for a system or software. The testing plan for this system is presented in
Table 4.1
Test Area Test Cases Status
1. Create Account CreateAccount01 True

2. Login Login01 True

Login02 True

3. Assign Permission to staff Permission01 True

4. Add / Remove User User01 True

5. Edit user account Edit01 True

6. Add Event Event01 True

7. Delete event DeleteEvent01 True

8. Process refund Refund01 True

9. Create / edit / delete parking Parkinglot01 True

lot

54
 10. Add / edit / delete asset Asset01 True

11. Add / edit / delete Maintenance01 True

maintenance schedule
Figure 4.1: Testing plan
4.5.2.1 Test Cases
(See Appendix B)

55
 CHAPTER FIVE

CONCLUSION AND RECOMMENDATIONS

5.1 Objectives and Achievements

The project successfully achieved its objectives by implementing a comprehensive
stadium management system. It effectively managed customer information and transaction
details through a database. The system also provided a seamless online ticket sales and payment
system, enhancing convenience for customers. User-friendly interfaces were designed,
ensuring easy navigation for both customers and staff. Online support was implemented to
provide prompt customer support. The system accurately displayed customer refunds and
updates in real-time, improving transparency. Maintenance records were stored in a database,
enabling effective planning and scheduling.
The user activity feature in the system can be used for employee performance evaluation.
By tracking the login and logout times, the system can provide insights into employee
attendance, punctuality, and work hours.

5.2 Problems Encountered

Developing a stadium management system indeed presents a unique set of challenges.
Throughout the project, we encountered various obstacles that required careful consideration
and innovative problem-solving. Some of the problems we faced included:
• Limited time to learn new technologies - During the project, we encountered significant
challenges that forced us to learn new technologies. We had to understand unfamiliar
programming languages and frameworks crucial for the stadium management system. This
time constraint had a notable impact, increasing the pressure on our team to effectively
learn and apply these technologies. However, we tackled this challenge by utilizing online
resources for assistance and collaborating with colleagues to seek help when needed.
Through our collective efforts, we successfully overcame this challenge and achieved our
goals.
• Effective communication – The inability to communicate face to face due to school
schedules negatively impacted the project's decision-making and problem-solving. Face-
to-face communication allows for real-time discussions and quick decision-making.
Without it, decision-making can be delayed, leading to project bottlenecks and slower
progress. This problem was tackled by leveraging online collaboration tools.

56
• Lack of domain expertise - One of the problems encountered during the development of
the stadium management system was a lack of domain expertise in the ticketing systems,
event management, facility management, and other related aspects. To tackle this
challenge, we conducted interviews, observations, and surveys to gather requirements from
both stadium attendees and individuals with expertise in the specific domain. This allowed
us to gain a comprehensive understanding of the unique requirements and complexities
involved in managing a stadium.

5.3 Lessons Learnt

During this project, we had the opportunity to learn and develop our skills in various
aspects. Firstly, we gained hands-on experience in managing a project from its inception to
its successful completion. We learned how to effectively plan, allocate resources, and meet
project deadlines.
Additionally, We also got to explore the field of user interface design. By doing
research and trying different approaches, we improved our skills in creating attractive and
user-friendly interfaces.

5.4 Future Development

Based on the outcomes and challenges faced during the stadium management system
project, some recommendations for future projects include:
• Enhance security measures: Integrate advanced security features such as access
control systems, facial recognition technology, and biometric authentication to ensure
the safety and security of both staff and attendees. These measures can help prevent
unauthorized access and enhance overall security protocols.
• Voice search: Implementing voice search in the system allows users to perform tasks
faster by using their voice. This feature enables users to search for tickets or perform
other related tasks by simply speaking their commands or queries instead of typing
them. Voice search utilizes speech recognition technology to convert spoken words into
text and then processes the text to perform the requested task. It provides a convenient
and hands-free way for users to interact with the system, saving time and effort.

57
 REFERENCES

1. Alan, D., Janet, F., & Russel, B. (2004) Human Computer Interaction. 3rd edn. Edinburg,
Pearson
2. Caulfield, J., & Jha, A. K. (2022). Stadiums and Digitalization: An Exploratory Study of
Digitalization in Sports Stadiums. Journal of Decision Systems, 31(S1), 331–340.
https://doi.org/10.1080/12460125.2022.2073629
3. Çakmak, G., & Çiftçi, S. (2021). Football Fans’ Views on the Passolig E-Ticket System
and the Decrease in Stadium Attendance: The Case of the Turkish Football Super League.
Physical Culture and Sport, Studies and Research, 92(1), 9–18.
https://doi.org/10.2478/pcssr-2021-0021
4. CAF, (2019) Safety and Security Regulations. Available at:
https://images.cafonline.com/image/upload/caf-prd/gqu2gsesganyqrgco3b0.pdf
5. CitiTube (2019) gives journalists tour of their club and facilities. July. Available at:
https://youtu.be/DH8ru5vccdc (Accessed: 10 May 2023)
6. Chub, A. N., & Kreizer, I. I. (2020). Principles of reconstruction of multifunctional
stadiums on the example of the Kiev stadium of CSC Armed Forces of Ukraine. IOP
Conference Series: Materials Science and Engineering, 907(1).
https://doi.org/10.1088/1757-899X/907/1/012066
7. Chen, Y., Sylvester, A. P. F., Bonsu, M. O.-A., & Minkah, A. Y. (2018). Practice of
Maintenance Management of Infrastructures on Sports Stadia in Ghana. Journal of Public
Administration and Governance, 8(4), 250. https://doi.org/10.5296/jpag.v8i4.14064
8. Dipanjan, S. (2017) Text Analytics with Phython.1st edn. Bangalore, Karnataka

9. egoTickets (n.d.) [Screenshot of egoTickets homepage]. Available at:

https://egotickets.com/ (Accessed 25 June 2023)
10. Eraslan, A., Üniversitesi, G., & Fakültesi, S. B. (2023). Futbol stadyumlarında alınan
güvenlik önlemlerine ilişkin seyirci algıları. Journal of ROL Sports Sciences Cilt, 1, 2023.
https://doi.org/10.5281/zenodo.7739750
11. Erturan-Ogut, E. E. (2020). Neoliberalizing football and fandom: the authoritarian e-
ticketing system in Turkish stadiums. International Journal of Sport Policy and Politics,
12(1), 91–110. https://doi.org/10.1080/19406940.2019.1638814
12. GhanaWeb (2022) E-ticketing for sports: How making ticketing easy for Ghana vs.
Nigeria game enhanced fans participation. Available at:
https://mobile.ghanaweb.com/GhanaHomePage/NewsArchive/E-ticketing-for-sports-

58
 How-making-ticketing-easy-for-Ghana-vs-Nigeria-game-enhanced-fans-participation-
1529231 (Accessed: 8 July 2023)
13. Ghosal, S., Chaturvedi, S., Taywade, A., & Jaisankar, N. (2015). Android Application for
Ticket Booking and Ticket Checking in Suburban Railways. Indian Journal of Science
and Technology, 8(S2), 171. https://doi.org/10.17485/ijst/2015/v8is2/60291
14. Glebova, E., & Desbordes, M. (2020). Technology Enhanced Sports Spectators Customer
Experiences: Measuring and Identifying Impact of Mobile Applications on Sports
Spectators Customer Experiences. Athens Journal Of Sports, 7(2), 115–140.
https://doi.org/10.30958/ajspo.7-2-3
15. Global Sports Innovation Center (2019) Digital Transformation of Sports Entities by 2025.
Available at: https://sport-gsic.com/wp-content/uploads/2019/07/GSIC-Report-Digital-
Transformation-of-Sports-Entitites-by-2025-VL.pdf (Accessed: 7 July 2023)
16. Ian. S. (2016) Software Engineering. 10th edn. Edinburgh Gate:Pearson Educational
Limited
17. Intel (2016) ‘Smart Stadiums Take the lead in Profitability, Fan Experience and Security.
Available at: https://cdrdv2-public.intel.com/612622/iot-smart-stadiums-brief.pdf
18. Jin, S and Lyu, S. O. (2019) Using a discrete choice experiment to estimate spectators’
willingness to pay for professional baseball park sportscape,
Sport Management Review Journal, 22(4) ,502-5112. doi:
http://10.1016/j.smr.2018.06.009

19. Kameli, M., Javad, M, S., & Mujtaba, H. (2019). An Application Framework for
BIM/RFID-Based Maintenance Management System Development: Case Study of a
Stadium Building. Canadian Journal of Civil Engineering. doi: 10.1139/cjce-2019-0107
20. KofiTv (2022) Two Nigerians Arrested Over Fake Ticket at Baba Yara Sports Stadium.
March. Available at: https://youtu.be/EXTYwJ6XJKo (Accessed: 5 May 2023)
21. Laudon, C. K. and Laudon, J. P. (2016) Management in Information System, Edinburgh.
14th edn. Edinburgh: Pearson.
22. Lee, M., Potter, R. F., & Pedersen, P. M. (2019). The effects of emotions on cognitive
effort while processing mediated stadium-embedded advertising: A dynamic motivational
systems approach. European Sport Management Quarterly, 19(5), 605–624.
https://doi.org/10.1080/16184742.2018.1562483
23. Lee, M., Tuchman, D., & Arner, E. (2022). Single vs. Multiple Signage: Applying
Limited Capacity Message Processing to Fan 2019;s Recognition and Recall of In-

59
 stadium Advertising. International Journal of Human Movement Science, 16(1), 19–28.
https://doi.org/10.23949/ijhms.2022.04.16.1.2
24. Li, S. (2023). Development of Intelligent Sports Stadium System Based on Internet of
Things Technology. In Proceedings of the 2022 2nd International Conference on
Computer Technology and Media Convergence Design (CTMCD 2022) (pp. 570–576).
Atlantis Press International BV. https://doi.org/10.2991/978-94-6463-046-6_67
25. Mahdi, M. J., Aljuboori, A. F., & Hussein Ali, M. (2021). Smart Stadium using Cloud
Computing and Internet of Things (IoT): Existing and New Models. International Journal
of Computer Applications Technology and Research, 10(05), 111–118.
https://doi.org/10.7753/ijcatr1005.1002
26. Narkotu, T.P. (2020) Ghana Premier League Report. Accra. Available at:
https://ascafro.com/wp-content/uploads/2021/03/2020-ASC-Ghana-Premier-League-
Report1.pdf
27. Narimani, A., Moosavi, R, T. & Keshavarv, L. (2017). Ranking the spectators
difficulties in purchasing electronic tickets of football premier league matches at Azadi
Stadium, Iran, 4(1), pp.9-15. Available at:
https://dergipark.org.tr/en/pub/sbsebd/issue/31663/347137>

28. Nugraha, A., Daniel, D. R., & Utama, A. A. G. S. (2021). Improving multi-sport event
ticketing accounting information system design through implementing RFID and
blockchain technologies within COVID-19 health protocols. Heliyon, 7(10).
https://doi.org/10.1016/j.heliyon.2021.e08167
29. Rashid, A., & Chaturvedi, A. (2019). Cloud Computing Characteristics and Services A
Brief Review. International Journal of Computer Sciences and Engineering, 7(2), 421–
426. https://doi.org/10.26438/ijcse/v7i2.421426
30. Sandeep, B. (2017) Cloud Computing. Delhi, Cambridge
31. Satinder, B. G. and Aditya, M. (2017) Introduction to Database Management System. 2nd
edn. Delhi, Laxmi

32. Schreyer, D. and Ansari, P. (2022) ‘Stadium Attendance Demand Research: A Scoping
Review’, Journal of Sports Economics, 23(6), pp. 749–788. Available at:
https://doi.org/10.1177/15270025211000404.
33. Schut, P. O., & Glebova, E. (2022). Sports Spectating in Connected Stadiums: Mobile
Application Roland Garros 2018. Frontiers in Sports and Active Living, 4.
https://doi.org/10.3389/fspor.2022.802852

60
34. SmartDublin. (2016). Croke park stadium. Available at https://smartdublin.ie/croke-
park-smart-stadium/

35. Sports Tech Innovation in the Start-up Nation Technology Trends in the Sports Market
Mapping Israel’s Sports Tech Start-ups. (2017).
36. Studhub (n.d.) [Screenshot of Studbub homepage]. Available at:
https://www.stubhub.com/?from=1688969910689&to=253402300800000&lat=NS42MD
Q%3D&lon=LTAuMTg3 (Accessed 25 June 2023 )
37. TicketMaster (n.d.) [Screenshot of Ticketmaster homepage]. Available at:
https://www.ticketmaster.com (Accessed 25 June 2023 )
38. Xu, C., Yan, L. and Zhang, J. (2022) ‘Research on a Complete Set of Sports Stadium
Projects Assisted by China and Africa’, OALib, 09(07), pp. 1–13. Available at:
https://doi.org/10.4236/oalib.1109053.
39. Yilmaz, O., Easley, R. F., & Ferguson, M. (2022). The Future of Sports Ticketing:
Technologies, Data, and New Strategies. SSRN Electronic Journal.
https://doi.org/10.2139/ssrn.4260366
40. Yusuf, A. O., Akinwusi, A. T., & Morakinyo, E. O. (n.d.). European Journal of Physical
Education and Sport Science, Examining the level Stadium Security and Safety During
Nigeria Professional Football League, https://doi.org/10.5281/zenodo.3627967

61
Appendix A: Installation guide and System Requirements
The guide includes the necessary hardware and software requirements to run the system
accurately. It also provides a step-by-step walkthrough on how to install the necessary software
to run the system properly. The following steps outline the installation process:

Step 1: Install Python 3.10 or 3.11 interpreter and runtime

To install Python 3.10 or 3.11, you can visit the official website or Microsoft Store.
Alternatively, you can open your command prompt and type "python", which will redirect you
to the Microsoft Store to download it. In Figure A.1, you can see the Microsoft Store displaying
the Python interpreter download interface.

Figure A.1: Python interpreter download interface

Step 2: Download and Install Node.js

Node.js is a runtime environment that allows you to run JavaScript code outside of a web
browser. You can download Node.js from the official website (https://nodejs.org/en/download)
Node.js is compatible with macOS, Windows, and Linux operating systems. In Figure A.2, you
can see the download interface of Node.js

Figure A.2: Node.js download interface

62
Step 3: Open the command line interface and start the backend server
The backend server is a part of a software application that handles the processing and
storage of data. It typically runs on a remote server and communicates with the frontend of the
application, which is what users interact with. To start the backend server, open the command
line interface and run the following command.

a. Moving up a directory - Navigate to the parent directory by using the command "cd .."
This will move you up one level in the directory structure.
b. Navigate to a folder - To navigate to a specific folder using the "cd" command, you need
to type "cd" followed by the path of the folder.
c. System directory change: After you navigate to the specific folder, you can use the "cd"
command followed by the path to change the directory where the stadium management
system files are stored. For example, if you want to navigate to the stadium management
system folder shown in Figure A.3, you can use the command "cd stadium_ms-main".
d. Navigate to the backend folder - The next step is to change the directory to the "backend"
folder using the command "cd backend". In the interface shown in Figure A.4, there are
two folders: "backend" and "frontend". To access the "backend" folder, simply type "cd
backend".
e. Activate virtual environment - To activate the virtual environment, you can open the
command prompt and type "venv\Scripts\activate.bat". In Figure A.5, the "venv" folder
contains all the essential files and dependencies needed to create an isolated environment.
f. Changing directory to api folder – To change the directory to the "api" folder, simply
type "cd api" in the command prompt. Figure A.5 displays the api folder situated in the
backend directory.
g. Installing dependencies- To install the necessary dependencies, just run the command "pip
install -r requirements.txt".
h. Starting Django server - To start the Django development server, simply run the
command "python manage.py runserver". This will launch the server and make your
application accessible at a local address. In Figure A.6, the interface shows that the Django
server has started with the URL http://127.0.0.1:8000, which can be accessed locally in a
web browser. In Figure A.7, the command prompt is shown with the commands entered to
start the backend server.

63
Step 4: Open the command line interface and start the frontend server
The frontend server is part of a software application that is responsible for showing users
the application interface and handling their interactions. It works hand in hand with the backend
server, which takes care of data processing and storage.
To start the frontend server, simply follow the commands listed in step 3 (a to c) for the
backend server. Once you have completed those steps, you can move on to the following
commands to start the frontend server.

a. Navigate to the backend folder - The next step is to change the directory to the "frontend"
folder using the command "cd frontend". In the interface shown in Figure A.4, there are
two folders: "backend" and "frontend". To access the "frontend" folder, simply type "cd
frontend".
b. Start development server - The command "npm run dev" is used to start the development
server for the project. It runs the specified script defined in the package.json file with the
name "dev". In Figure A.8, the command prompt interface is displayed, showing the
frontend server being started. To access the server, you can use the URL:
https://localhost:3000.

Figure A.3: Stadium management system folder

64
Figure A.4: backend and frontend folders

Figure A.5: Backend files

65
 Figure A.6: Starting Django server

Figure A.7: Starting the backend server using command prompt

66
Figure A.8: Starting the frontend server using command prompt

67
Appendix B: Test Cases
• Creating Account
Test case ID: CreateAccount01
Test Title: Account Creation
Test Priority: High
Purpose: To verify that users can successfully create an account in the system

Step Description Test Data Expected Actual

Results Results
1 Go to the signup Load the signup True
page page
2. Enter your full name Full name: Samuel Oppong

3 Enter your email Email:

address Samueloppong123@gmail
.com
4 Enter your password Password: ********

5 Enter your phone Phone: 0579434792

number
6 Click on create The system True
account notifies the user
that account has
been created
Table B.1: Test case – Create Account01

Figure B.1 below illustrates the page where the user has successfully created their
account, and the system has displayed a notification confirming the account creation.

68
 Figure B.1: Account created successfully

• Login
Test case ID: Login01
Test Title: Account Login
Test Priority: High
Purpose: To verify that users can successfully login to the system
Step Description Test Data Expected Actual
Results Results
1 Go to the login page Load the login True
page
2 Enter your email Email:
address Samueloppong123@gmail
.com
3 Enter your password Password: ********

4 Enter your phone Phone: 0579434792

number
5 Click on login button The user should True
be able to login
Table B.2: Test case – Login01

69
 Test case ID: Login02
Test Title: Account Login
Test Priority: High
Purpose: To verify login with username and password
Step Description Test Data Expected Actual
Results Results
1 Go to the login page Load the login True
page
2 Enter your email Email:
address Samueloppong123@gmail
.com
3 Enter your password Password: ********

4 Click on login button The system will True

show an error
message
Table B.3: Test case – Login02

Figure B.2 below illustrates the page where the user has logged into the system with invalid
credentials, and the system displays an error message.

Figure B.2: Invalid login attempt occurred.

70
• Assign Permission to staff
Test case ID: Permission01
Test Title: Assign Permission to staff
Test Priority: High
Purpose: To ensure that the system correctly and accurately assigns the appropriate
permission to staff members.
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Admin page True
as an admin
2 Navigate to
authentication and
authorization
3 Click on the “create
group’’ button to
create new group
4 Specify the The system will True
permissions that show an error
should be added to message
the group
5 Select the staff
members you want to
add to the group
Table B.4: Test case – Permission01

• Add a user
Test case ID: User01
Test Title: Add user to the system
Test Priority: High
Test purpose : To verify that user can be successfully added to the system, allowing
them to access and use system functionalities.

71
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Admin page True
as an admin
2 Navigate to Users

3 Click on the “add

user” button to add
user
4 Enter the user Email, Full name, Phone
credentials number, and password
5 Click on the save Successful True
button addition of new
user to the
system
Table B.5: Test case – User01

• Edit user account

Test case ID: edit01
Test Title: Edit user account
Test Priority: High
Test purpose : To verify that users can successfully edit their account information, such
as name, email, and phone number.
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Admin page True
as an admin
2 Navigate to Users

3 Access the list of The admin can True

users and click on the view and edit
specific user you account
want to modify information
Table B.6: Test case – edit01

72
Figure B.3 below illustrates the page where the admin can edit user account information.

Figure B.3: Admin edit user information

• Add event
Test case ID: event01
Test Title: Add event to the system
Test Priority: Medium
Purpose: To verify that the "add event" functionality successfully adds an event to the
system.

Step Description Test Data Expected Actual

Results Results
1 Login to the system Username and password Staff page True
as staff member
2 Navigate to events

3 Click on the “add Clicking on the True

event’’ button "add event"
button will open
a form or page
where you can

73
 enter event
details.
4 Enter the event Title, Price, Capacity, Event
details type, location, image, and
description of the event
5 Click on add event Event being True
successfully
added to the
system
Table B.7: Test case – event01

• Process Refund
Test case ID: refund01
Test Title: Process Refund
Test Priority: High
Test purpose : To verify that the refund process is functioning correctly and successfully
processes refunds for customers.
Step Description Test Data Expected Actual
Results Results
1 Login to the system as a Username and password Admin page True
staff member
2 Navigate to refund

3 Select the transaction Display details True

ID for which you want of customer
to process refund transaction
5 To proceed with the Customer True
refund process, click on transaction ID
the checkbox next to the status changes
"Pay" option and update
the status
accordingly.

Table B.8: Test case – refund01

74
• Create parking lot
Test case ID: parkinglot01
Test Title: Creating parking lot
Test Priority: Medium
Test purpose : To verify that the system successfully creates a new parking lot
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Staff page will True
as a staff member be displayed
2 Navigate to parking
lot
3 Click on create
parking lot button
4 Provide necessary Parking lot name, location, True
details for parking lot
and capacity
5 Click on save Parking lot has True
been created
successfully
Table B.9: Test case – parkinglot01

• Add asset
Test case ID: asset01
Test Title: Add Stadium asset
Test Priority: Medium
Test purpose : To verify the system successfully add asset to the database
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Staff page will True
as a staff member be displayed
2 Navigate to asset

3 Provide necessary Asset name, type, and True

details for the asset
condition

75
 4 Click on save Asset has been True
added
successfully
Table B.10: Test case – asset01

• Add maintenance schedule

Test case ID: maintenance01
Test Title: Add maintenance schedule
Test Priority: Medium
Test purpose : To verify the system successfully add maintenance schedule to the database
Step Description Test Data Expected Actual
Results Results
1 Login to the system Username and password Staff page will True
as a staff member be displayed
2 Navigate to
maintenance
3 Provide necessary Asset name, type, priority,
details for the asset
status, assignee, and date
4 Click on save Maintenance True
schedule has
been added
successfully
Table B.11: Test case – maintenance01

76
Appendix C: Sample Source Codes

Django Command-line Utility for Administrative Tasks

#!/usr/bin/env python
"""Django's command-line utility for administrative tasks."""
import os
import sys
def main():
"""Run administrative tasks."""
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'api.settings')
try:
from django.core.management import execute_from_command_line
except ImportError as exc:
raise ImportError(
"Couldn't import Django. Are you sure it's installed and "
"available on your PYTHONPATH environment variable? Did you "
"forget to activate a virtual environment?"
) from exc
execute_from_command_line(sys.argv)
if name == ' main ':
main()

Django ASGI Application Initialization

import os
from django.core.asgi import get_asgi_application
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'api.settings')
application = get_asgi_application()

Database Configuration for Django with SQLite3

DATABASES = {

'default': {

'ENGINE': 'django.db.backends.sqlite3',

77
 'NAME': BASE_DIR / 'db.sqlite3',

Password Validation

AUTH_PASSWORD_VALIDATORS = [

'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',

},

'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',

},

'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',

},

'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',

},

User API for Listing Users

class UserAPIView(generics.ListAPIView):

permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = User.objects.all().order_by('-id')

serializer_class = UserSerializer

78
Update and delete user API

class UserUpdateAPIView(generics.RetrieveUpdateDestroyAPIView):

permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = User.objects.all()

serializer_class = UserSerializer

lookup_field = 'id'

Event API

class EventAPIView(generics.ListCreateAPIView):

permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = Event.objects.all().order_by('-id')

serializer_class = EventSerializer

parser_classes = (MultiPartParser, FormParser,)

renderer_classes = (JSONRenderer,)

def post(self, request, *args, **kwargs):

serializer = EventSerializer(data=request.data)

if serializer.is_valid():

serializer.save()

return Response({'message': 'Event created successfully'},

status=status.HTTP_201_CREATED)

return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)

class EventDetailAPIView(generics.RetrieveDestroyAPIView):

permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = Event.objects.all()

serializer_class = EventSerializer

lookup_field = 'id'

79
Update Event

class UpdateEvent(views.APIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = Event.objects.all()

serializer_class = EventSerializer

parser_classes = (MultiPartParser, FormParser,)

def patch(self, request, id):

event = Event.objects.filter(id=id).first()

if event is None:

return Response({'message': 'Event not found'},

status=status.HTTP_404_NOT_FOUND)

serializer = EventSerializer(event, data=request.data, partial=True)

if serializer.is_valid():

serializer.save()

return Response({'message': 'Event updated successfully'},

status=status.HTTP_200_OK)

return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)

Get all tickets API

class TicketAPIView(views.APIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

def get(self, request):

tickets = Ticket.objects.filter(is_refund=False).order_by('-id')

refund = Refund.objects.filter(is_paid=True)

transactions = Transaction.objects.all()

total_account = 0

80
 for transaction in transactions:

total_account += transaction.amount

tickets_sales = 0

for ticket in tickets:

tickets_sales += ticket.total

tickets_refund = 0

for refund in refund:

tickets_refund += refund.amount

context = {

'total_account': total_account,

'tickets_sales': tickets_sales,

'tickets_refund': tickets_refund,

'tickets': TicketSerializer(tickets, many=True).data,

return Response(context, status=status.HTTP_200_OK)

Refund API

class RefundAPIView(views.APIView):

permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = Refund.objects.all().order_by('-id')

def get(self, request):

refunds = Refund.objects.all().order_by('-id')

total_amount = 0

pending_amount = refunds.filter(is_paid=False).count()

for refund in refunds.filter(is_paid=True):

81
 total_amount += refund.amount

context = {

'total_amount': total_amount,

'pending_amount': pending_amount,

'refunds': RefundSerializer(refunds, many=True).data,

return Response(context, status=status.HTTP_200_OK)

class UpdateRefundAPIView(generics.UpdateAPIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = Refund.objects.all()

serializer_class = RefundSerializer

lookup_field = 'id'

class PayRefund(views.APIView):

def post(self, request, id):

refund = Refund.objects.get(id=id)

refund.is_paid = True

refund.save()

return Response({'message': 'Refund Paid Successfully'}, status=status.HTTP_200_OK)

Parking API

class ParkingLotAPIView(generics.ListCreateAPIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = ParkingLot.objects.all().order_by('id')

serializer_class = ParkingLotSerializer

filter_backends = [DjangoFilterBackend]

82
 filterset_fields = ['event id']

class ParkingLotDetailAPIView(generics.RetrieveDestroyAPIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = ParkingLot.objects.all()

serializer_class = ParkingLotSerializer

lookup_field = 'id'

class UpdatePqrkingLotAPIView(views.APIView):

# permission_classes = [permissions.IsAuthenticated, permissions.IsAdminUser]

queryset = ParkingLot.objects.all()

def patch(self, request, id):

parking_lot = ParkingLot.objects.filter(id=id).first()

if parking_lot is None:

return Response({'message': 'Parking Lot not found'},

status=status.HTTP_404_NOT_FOUND)

user = User.objects.filter(id=request.data['user']).first()

if user is None:

return Response({'message': 'User not found'},

status=status.HTTP_404_NOT_FOUND)

parking_lot.user = user

parking_lot.is_booked = True

parking_lot.save()

serializer = ParkingLotSerializer(parking_lot)

return Response(serializer.data, status=status.HTTP_200_OK)

83
Asset API

class AssetAPIView(generics.ListCreateAPIView):

queryset = Asset.objects.all().order_by('-id')

serializer_class = AssetSerializer

class AssetDetailAPIView(generics.RetrieveUpdateAPIView):

queryset = Asset.objects.all()

serializer_class = AssetSerializer

lookup_field = 'id'

class MaintanceAPIView(generics.ListAPIView):

queryset = Maintainace.objects.all().order_by('-id')

serializer_class = MaintanceSerializer

class MaintenaceCount(views.APIView):

def get(self, request):

maintainaces = Maintainace.objects.all()

pending = maintainaces.filter(status='Pending').count()

completed = maintainaces.filter(status='Completed').count()

progress = maintainaces.filter(status='In Progress').count()

context = {

'pending': pending,

'completed': completed,

'progress': progress,

return Response(context, status=status.HTTP_200_OK)

class MaintanceDetailAPIView(generics.UpdateAPIView):

84
queryset = Maintainace.objects.all()

serializer_class = MaintanceSerializer

lookup_field = 'id'

85
Appendix D: User Evaluation

Questionnaire

1. How often do you visit the stadium?

a) Daily
b) Weekly
c) Monthly
d) Occasionally
e) Never Visited

2. How easy was it to navigate through the different features and functionalities of the system?
a) Very easy
b) Somewhat easy
c) Neutral
d) Somewhat difficult
e) Very difficult

3. Did you encounter any technical issues or glitches while using the system?
a) No, it worked smoothly without any issues.
b) There were a few minor glitches, but nothing major.
c) Neutral
d) Yes, there were significant technical issues that affected my experience.
e) The system was completely unusable due to technical issues.

4. How responsive and helpful was the customer support provided for the stadium management
system?
a) Very responsive and helpful.
b) Somewhat responsive and helpful.
c) Neutral
d) Not very responsive or helpful.
e) No customer support was available.

5. How well did the system handle ticket sales and revenue management?
a) Very well, it streamlined the ticket sales process and revenue tracking.
b) It was satisfactory, but there were some areas for improvement.

86
 c) Neutral
d) It had some difficulties in managing ticket sales and revenue.
e) Poorly, the system was ineffective in handling ticket sales and revenue.

6. Were you able to easily access and manage information related to events, tickets, and
facilities ?
a) Yes, it was straightforward and convenient to access and manage the information.
b) It was somewhat easy, but there were a few challenges.
c) Neutral
d) It was difficult to access and manage the information effectively.
e) No, the system did not help access and manage event-related information.

7. How satisfied would you be with the ticket refund process?

a) Very satisfied
b) Satisfied
c) Neutral
d) Dissatisfied
e) Very dissatisfied

8. Did you find the stadium management system to be responsive and fast in terms of loading
times?
a) Yes, it was very responsive and fast.
b) It was mostly responsive and fast.
c) It was average in terms of responsiveness and loading times.
d) It was somewhat slow and unresponsive.
e) No, it was very slow and unresponsive.

9. How satisfied were you with the ticket purchasing process?

a) Very satisfied
b) Satisfied
c) Neutral
d) Dissatisfied
e) Very dissatisfied

10. How would you rate the overall user interface of the stadium management system?
a) Excellent

87
 b) Good
c) Average
d) Poor

Evaluation Results
a) b) c) d) e)
Q1 3 1
Q2 2 2
Q3 2 2
Q4 1 1 2
Q5 4
Q6 3 1
Q7 3 1
Q8 1 3
Q9 2 2
Q10 1 3

88