Sports Management System

BACHELOR OF
SCIENCE IN
COMPUTER SCIENCE

FYP-Proposal
By
SHAH ZAMAN 2019-GCUF-070281
TAHIR ALI 2019-GCUF-078030
Project Advisor
Sir Rameez
Raja

DkEPARTMENT OF COMPUTER SCIENCE

Lahore College of Arts Science & Technology
Affiliated with

Government College University Faisalabad 2023

 Government College University Faisalabad Page 1

1. Introduction......................................................................................................................................................1
1.1 General Information...................................................................................................................................2
1.2 Purpose.........................................................................................................................................................3
1.3 Document Conventions..............................................................................................................................4
1.4 Project objective.........................................................................................................................................5
1.5 Project Scope..............................................................................................................................................6
2. Overall Description..........................................................................................................................................7
2.1 Product Perspective...................................................................................................................................8
2.2 Product features.........................................................................................................................................9
2.3 User Classes and Characteristics.............................................................................................................10
2.4 Operating Environment ..........................................................................................................................11
2.5 Design and Implementation Constraints................................................................................................12
2.6 User Documentation ................................................................................................................................13
2.7 Assumptions and Dependencies ............................................................................................................. 14
3. System features................................................................................................................................................15
4. Externalinterfacerequirements......................................................................................................................16
5. Other Non-Functional Requirements............................................................................................................17
5.1 Performance Requirements ......................................................................................................................18
5.2 Safety Requirements .................................................................................................................................19
5.3 Security Requirements ..............................................................................................................................20
5.4 Software Quality Attributes ..........................................................................................................……....21
 1. Introduction

Project objectives for a sports management system may vary depending on the
specific requirements and goals of the organization implementing the system. However,
here are some common project objectives for a sports management system:
 Streamline Administrative Processes: The primary objective is to automate and
streamline administrative tasks such as registration, scheduling, team management,
and financial processes. This reduces manual effort, minimizes errors, and improves
overall efficiency.
 Improve Participant Experience: Enhance the experience for participants, including
athletes, coaches, parents, and fans. The system should provide easy online
registration, accessible schedules, efficient communication channels, and user-
friendly interfaces to ensure a positive and seamless experience.
 Increase Okperational Efficiency: Increase the efficiency of operations within the
sports organization. This includes optimizing resource allocation, reducing scheduling
conflicts, improving communication, and simplifying financial management
processes.

1.1 General Information

Project Name: SPORTS MANAGEMENT SYSTEM Starting Date: 01/03/2021.

_

Controlling Agency: LCAST Final Date:

ared by: SHAH ZAMAN

TAHIR ALI

1.2 Purpose

Project objectives for a sports management system may vary depending on the
specific requirements and goals of the organization implementing the system. However,
 Chapter 1 Introduction

here are some common project objectives for a sports management system:
 Streamline Administrative Processes: The primary objective is to automate and
streamline administrative tasks such as registration, scheduling, team management,
and financial processes. This reduces manual effort, minimizes errors, and
improves overall efficiency.
 Sports organization. This includes optimizing resource allocation, reducing
scheduling conflicts, improving communication, and simplifying financial
management processes.
 Enhance Data Management: Implement a centralized and secure database for
storing and managing participant information, registration details, financial records,
and other relevant data. The objective is to ensure data integrity, privacy, and easy
access for authorized personnel.
 Improve Communication and Collaboration: Facilitate effective communication and
collaboration among administrators, coaches, officials, and participants. The system
should provide tools for seamless communication, centralized notifications, and
real-time updates to foster collaboration and coordination.

1.3 Major Features:

Project objectives for a sports management system may vary depending on the
specific requirements and goals of the organization implementing the system.
However, here are some common project objectives for a sports management system:

 Streamline Administrative Processes: The primary objective is to automate and

streamline administrative tasks such as registration, scheduling, team management,
and financial processes. This reduces manual effort, minimizes errors, and
improves overall efficiency.

 Improve Participant Experience: Enhance the experience for participants, including

athletes, coaches, parents, and fans. The system should provide easy online
registration, accessible schedules, efficient communication channels, and user-
friendly interfaces to ensure a positive and seamless experience.

 Increase Operational Efficiency: Increase the efficiency of operations within the

sports organization. This includes optimizing resource allocation, reducing
scheduling conflicts, improving communication, and simplifying financial
management processes.

 Enhance Data Management: Implement a centralized and secure database for

storing and managing participant information, registration details, financial records,
and other relevant data. The objective is to ensure data integrity, privacy, and easy
access for authorized personnel.

 Improve Communication and Collaboration: Facilitate effective communication and

collaboration among administrators, coaches, officials, and participants. The system

5
 should provide tools for seamless communication, centralized notifications, and
real-time updates to foster collaboration and coordination.

1.5 Project Objective:

Project objectives for a sports management system may vary depending on the
specific requirements and goals of the organization implementing the system.
However, here are some common project objectives for a sports management
system:
1. Streamline Administrative Processes: The primary objective is to automate and
streamline administrative tasks such as registration, scheduling, team management,
and financial processes. This reduces manual effort, minimizes errors, and improves
overall efficiency.
2. Improve Participant Experience: Enhance the experience for participants, including
athletes, coaches, parents, and fans. The system should provide easy online
registration, accessible schedules, efficient communication channels, and user-
friendly interfaces to ensure a positive and seamless experience.
3. Increase Operational Efficiency: Increase the efficiency of operations within the
sports organization. This includes optimizing resource allocation, reducing
scheduling conflicts, improving communication, and simplifying financial
management processes.
Agency Goals Project Objectives
A web-based an d m ob il e application Manage reservation, seating efficiently
allows the user to book event online and arrange all day activities.

People do not need to go agent to reserve Build a safe and secure payment
sports event. They just have to open the gateway module.
app check availability the required and
simply reserve the seat.

This app will help to save To make easy online booking system
time. simple, reliable user friendly
Improve existing system
 Chapter 1 Introduction

1.4 Project Scope:

The project scope of a sports management system defines the boundaries and
deliverables of the project. It outlines the features, functionalities, and capabilities
that will be included in the system. Here is an example of the project scope for a
sports management system:
• User Registration and Profile Management:
o Online registration for participants, coaches, officials, and other stakeholders.
o Management of user profiles with personal details, contact information, and medical
records.
Scheduling and Fixture Management:
Creation and management of schedules for games, practices, tournaments,
etc. .
 Avoidance of scheduling conflicts and efficient resource allocation.
 Real-time updates and notifications to participants about schedule changes.
Team and Player Management:
 Roster management for teams, including player assignments, positions, and roles.
 Performance tracking and evaluation of playersk.
 Injury tracking and management.
Communication tools for coaches, team managers, and players.

7
 Government College University Faisalabad Page 5
2 Overall Description:

2.1 Product Perspective

Online event management system provides a group of works with interface environment. Also,
there will be a database that will keep all the records that user did while visiting the page.

2.2 Product Features:

 Login panel
 Calendar
 Different language
 Online check in
 Discount management
 Multi payment options
 Language translator
 Reports
2.3 User Classes and Characteristics
Every web based software is not usable for everyone .Every software is developed to facilitate
specific user and there are some classes and characteristics to differentiate our audience from
everyone.

User Classes
Our intended audience is all those individuals who want to reserve their seats online and those
organizations who want to implement this system in their workplace. This system will use near our
university area so these places can improve the sports system with the SMS system.

Characteristics

Every individual should at least know some basic background related to that field. A user of any age
will be facilitated with all functionalities without any discrimination.

2.4 Operating Environment

The online event operating system is a web-based application. We use ORACLE APEX 20.2 for
the implementation of our application. Moreover, we use PHP, J-QUERY JAVA-SCRIPT as
programming languages, ORACLE, PL/SQL database, and HTML, CSS for design.

2.5 Design and Implementation Constraints

We will design the whole system in three interfaces and implement the functionalities on it with
detailed working. We divided this project into different modules and will work on it in proper sequence.
Some points show the sequence and diagram which will present designing of the main project.

 We will develop on Sports Management System (SMS) which we further divided into three
interfaces.
 In these interfaces, there will be a separate dashboard for every interface.
 There will be a specific login system from which users have to pass through for usage9of further
functionality.
 Furthermore, there will be the option to reserve a event by using different languages.
  There will be the option for users to reserve a location for more than one week.

 We will work on a security system for interfaces if required.

2.5 User Documentation

User Documentation is an important part of the overall product delivered to your customer. It helps
end-users be more successful with your product or service. We have 4 basic modules of user
documentation.

These are as follow:

• Dashboard.
• Match Booking
• Language Section.
• Log-in/Registration.

Dashboard:
In the section of the dashboard, we have activities, profile, transactions, reservation, notification, and
other activities related to manage websites.
Booking:
There is a complete description for the user to book match easily anywhere anytime. We provide
different durations for event reservations.

Language Section:
This site gives you varieties of languages like English, Urdu, and many more.

Log-in/Register:
The user has to log in or register before going to their interfaces. We will assign a unique ID and If
they don’t have any specific id then they have to register themselves first then they can be login.

2.7 Assumptions and Dependencies

Our product needs the following third party products:
 We will use the MySQL server to store the database.
 We will use Oracle which is the framework of BPM to develop the product.
 We will develop the front end with the help of CSS, HTML, and Query.
 The operations of optimization in SMS depend on the number of interfaces and functionalities
of modules.
 Existence of Internet Service to all users.
 Government College University Faisalabad Page 5

3. System Features

3.1 Login System

3.1.1 Description and Priority

Provide a user with a page to log in to the dashboard.

Priority: Medium

3.1.2 Stimulus/Response Sequences

Stimulus: User clicks on Login Link.

Response: Login Page is displayed.
Stimulus: User Enters Username and Password.
Response: Username and Password are validated from MySQL Database.
Stimulus: User Clicks on Login Button or Home page.
Response: Home Page is displayed or if Username and Password are correct else an
Error message is displayed.
3.1.3 Functional Requirements
R001: The system will incorporate a mechanism to authenticate its users.
R002: The system will verify and validate all user input and would notify in case of error detection and
would help the user in error correction.
R003: The system will allow sharing of files in the system.
R004: The system will allow quick messages to be exchanged without face-to-face interaction.

3.2.3 Functional Requirements

REQ-1: The user will be able to click and view the link.
REQ-2: The user will be able to view the activities associated with each booking.
.
3.3 Book
3.3.1 Description and Priority
Provide a user with a page to view event reservations and to view activities associated with that
reservations. Priority: High

3.3.2 Stimulus/Response Sequences

Stimulus: User clicks on sports Link.
Response: Reservations are displayed
Stimulus: User clicks on the sports required accordingly their requirement.
Response: Booking is confirmed by clicking ok.
3.3.3 Functional Requirements

REQ-1: The user will be able to click and view the booking link.
REQ-2: The user will be able to view the activities associated with each booking.
11
3.4 Cancellation

3.4.1 Description and Priority

Provide a user with a page to view book and to view activities associated with that booking
Priority: Medium
3.4.2 Stimulus/Response Sequences
Stimulus: User clicks on cancellation Link.
Response: Cancellation is made.
Stimulus: User can click return payments.

Response: The Payments are transferred back to their account.

3.4.3 Functional Requirements

REQ-1: The user will be able to click and cancel the booking.
REQ-2: The user will be able to view the activities associated with each cancellation.

3.5 View User Profile

3.5.1 Description and Priority

The user will be able to see the user profile.

Priority: Medium
3.5.2 Stimulus/Response Sequences

Stimulus: User clicks on the dashboard My Profile.

Response: The user Profile Page is displayed

3.5.3 Functional Requirements

REQ-1: The user will be able to view the user Profile

3.6 Location by Google Maps:

3.6.1 Description: The Employee and users can set their location in the SMS.
Priority: High

3.6.2 Stimulus/Response Sequences:

Stimulus: User clicks on booking profile, and Admin clicks on user’s profile.

Response: The system will display the location of booking area.

3.5.3 Functional Requirements:

REQ-1: Admin should be able to view the location of event through Google Maps.
 Government College University Faisalabad Page 5

3.7 Logout

3.7.1 Description and Priority

The user will be able to Logout.

Priority: High

3.7.2 Stimulus/Response Sequences

Stimulus: User clicks on dashboard Logout option.

Response: User is Logout and Index Page is displayed

3.7.3 Functional Requirements

REQ-1: The user will be able to logout from the system

13
 4. External Interface Requirements

4.1 Admin Interfaces

This is the Interface for Admin. Admin will control all functionalities of the website from his interface.
He has the authority to add or remove employees from his slot. He will manage both interfaces of the
employee and the user. Assigning unique IDs and passwords to employees also include in his duties.
He will respond to solve queries from the employee end and will manage the security of interfaces
also.

4.2 Employee Interfaces

This Interface will not be access able by any random user. Not every individual can take a role as an
employee in our system. If any person will be interested to apply to be an employee on our website,
then he has to apply a request for it first. Our management will receive his CV and will finalize, that is
he eligible to be an employee on our platform or not. If that person will be selected as an employee
then we will provide him a unique id and password, without it, he can’t enter it in the employee
interface. After accessing the interface, he can manage different functionalities .

4.3 User Interfaces

Our system will be designed as a web-based that has the main user interface. The format of the main
screen will be standard and flexible. The system will be user-friendly designed. Pages will be
consistently connected to each other. Operations that can be done with the system will be repeatable.
The design of the pages would allow users to do this.

5. Other Non-functional Requirements

5.1 Performance Requirements

PR001: The system will provide an attractive graphical interface for the user because our system
would be user-friendly, consistent, and provide a language translator.
PR002: The system will allow its user to access by using the app.

5.2 Safety Requirements

SR001: The system would be able to take backup every day.

SR002: System database is kept private.
SR003: Database is accessible to only authorized persons.

5.2 Security Requirements

SR001: Online book reservation system would be secure from unauthorized persons.
SR002: User information is our first priority.
SR003: We use the data encryption method for end-toned encryption.
 Government College University Faisalabad Page 5

5.4 Software Quality Attributes

In the context of software quality attribute, software quality refers to two related but distinct notions:

1. Software functional quality reflects how well it complies with or conforms to a given design, based
on functional requirements or specifications. That attribute can also be described as the fitness for
purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile
product. It is the degree to which the correct software was produced.
2. Software structural quality refers to how it meets non-functional requirements that support the
delivery of the functional requirements, such as robustness or maintainability. It has a lot more to do
with the degree to which the software works as needed
There are the following Software quality attributes:
k
a) AVAILABILITY

Availability rules play a huge role in many different areas of functionality in SMS
Availability rules can be as simple or complex as you need them to be, and a deeper understanding of
how they can be combined will unlock a lot of power in how you make your SMS available to your
customer.

b) PORTABILITY

Portability is the ability to engage with or make use of booking in more than one setting. This website
contains portability. Users can easily find availability and travel at any time and any place. Their portal
can be easily log-in to any device with their URL and their IDs.

c) USEABILITY

A poorly designed User Experience is like a child in a sweet shop finding they can’t reach any of the
sweets they want on the shelves. It is disheartening and frustrating to say the least!
We have to put our customer’s right at the centers and consider their needs first and foremost. Yes,
data security, back-end interoperability, and rich feature lists are all essential, but if we don’t provide a
User experience that’s unpleasant, easy-to-use.

d) MAINTAINABILITY

The probability that a given maintenance action for an item under given usage conditions can be
performed within a stated time interval when the maintenance is performed under stated conditions
using stated procedures and resources. Maintainability has two categories, serviceability (the ease of
conducting scheduled inspections and servicing) and reparability (the ease of restoring service after a
failure).”

15