A

PROJECT REPORT
ON
“Web Application For”

“Sports Management System”

Designed By

Mr. Rahul Gautam Kambli.

Submitted To

In the Partial Fulfillment of

B.Sc. Computer Science (Third year)

Under Guidance of

Asst. Prof. P. N. Talankar.

Through

THE HEAD,
DEPARTMENT OF COMPUTER SCIENCE
S.R.M. COLLEGE, KUDAL.

2021-2022

[Type text]Page 1
 DECLARATION

To,

The Head,

Department of Computer Science,

S. R. M. College, Kudal.

Respected Sir,

I undersigned, hereby declare that the project on “Sports club management ”

is developed under the guidance of our lecturer Prof. P.N.Talankar.

The conclusion in this report is based on the data, which is

collected by me. I am declaring that this is my original work. I have not copied
any materials, which are useful to my work, or other reports that are submitted
to the S. R. M. COLLEGE, KUDAL this year.
I do undersign that if my work is found to be copied, then I
am liable to punishment as per the university rule.

DATE:

PLACE: KUDAL. (Mr Rahul Gautam Kambli )

[Type text]Page 2
 K.M.S.P. MANDAL’S
SANT RAWOOL MAHARAJ MAHAVIDYALAYA,
KUDAL.
(NAAC ACCREDITATION “B” GRADE)

CERTIFICATE

This is certify that Mr. Rahul Gautam Kambli has completed his work on
Project Report Titled,

“Sports Club Management ”

As per the syllabus prescribed for T. Y. BSc (Computer Science) of Mumbai

University, Mumbai. It is also certified that this is his own work completed
during academic year 2021 – 2022. The work done is satisfactory and is
presented as per the specifications.

PROJECT GUIDE EXTERNAL EXAMINIER HEAD OF DEPARTMENT

DATE :

PLACE : KUDAL.

ACKNOWLEDGEMENT
[Type text]Page 3
Many people have helped me during my project and each of their contribution

has been valuable. The timely completion of this project is mainly due to the

interest and worth helping of Asst.Prof. P. N. Talankar, Asst.Prof. K. A.

Kubal and their help will be remembered forever.

I would like to thank them to Guide me during my project work. I

would like to thank all those who directly and indirectly helped in Completion

of this Project.

PREFACE

[Type text]Page 4
This report contains the basic logic used for software
development along with the diagrams so that the logic may be
apprehended without difficulty. For detail information, screen
layouts provided with the report can be viewed.

Although this report is prepared with at most care, there may

be some errors for the project is subjected to further
enhancement as per the requirements of organization.

1. Project Title

Sports Club Management System

2. Introduction & Objectives

Sports club management system is developed keeping in mind

the regular day-to-day operations of a sports club. The club’s
entire operation is automated using this software.

3. Relevance & Society Benefits

Healthy bodies, healthy minds. Through the development of

healthy physical activity habits, children and youth are not
only supporting healthy bodies, but are also likely to show
improved performance in school. .
=====
Sports clubs provide an opportunity for children and youth to
learn skills that will help them in school, future careers and
personal relationships.
[Type text]Page 5
=====

FEASIBILITY STUDY
To analyze whether the software will meet organizational requirements
Feasibility is defined as the practical extent to which a project can be performed
successfully. To evaluate feasibility, a feasibility study is performed.

[Type text]Page 6
To determine whether the software can be implemented using the current
technology and within the specified budget and schedule A feasibility study is a
preliminary investigation of a proposed system to decide whether the system
can run smoothly with the organization.

To determine whether the software can be integrated with other existing

software. Benefits that are expected and to decide will the organization go for it.

Three Types of feasibility study

1. Economic Feasibility

2. 2. Technical Feasibility

3. Operational Feasibility

1. Economic Feasibility:
Economic feasibility is also one of the most important aspects to be
considered while development of an application. To develop this project, I do
not required any hardware. I can afford the software required for the technology
which I will use.

2. Technical Feasibility:

Technical feasibility is also important as it emphasize on the technical

requirements for the system. My project is desktop application so its require
minimum I3 processor or above that , minimum 2GB ram on computer. Thus
looking at requirements we can say that the application is technically feasible.

3.Operational feasibility:
In the proposed system all the working is done in best & right manner
.The system will fulfill all requirements of customers, thus the system is
operationally feasible.

[Type text]Page 7
 STAKEHOLDER

1. Admin
2. Customer

Scope and future

enhancement
[Type text]Page 8
 The scope for this project is to build a solution in form
of an intranet that will fulfill the first set of objectives
mentioned in order to, from the role of an administrator,
perform effectively the club management tasks.

Over the time, the following releases of the solution

developed will increase the scope of the current one in both
technical-functional terms and targeted clubs.

1. Manage the activity of many sports at a time.

2. The user will consume less amount of time when
compared to manual paper work through the
automated system.
3. To find out the application of sports club management
system.
4. To provide information and manage the system regarding
sports event of the club.

[Type text]Page 9
 REQUIREMENT

SPECFICATION

[Type text]Page 10
 Requirement gathering

A. Fact finding Technique:

To study the system we require facts. Fact is also termed as data or information.
A specific method use for collecting a data is also called fact finding technique.

Interview, questionnaires, record review, observation are the different fact

finding technique use by analyst. Analyst uses more than one technique for
collecting correct and accurate data.

Interview:

This technique use to collecting information from individual or from group.

Interview Techniques:

● Structured Interview:

In this type of technique fixed format interview in which all

question are prepared beforehand and put in the same order to each
interview. Although this style lacks the free flow a friendly
conversation. It provides a precision and reliability require in
certain situation. In this type of techniques interview period may be
short. It is also called direct interview.

● Unstructured Interview:
In this type of technique different type of question are asked and
there are specific area. Interview without any set format but in
which interviewer may have some key questions formulated in
advanced. Unstructured interview allow question based on
interview’s response and proceed like friendly. Is also called as
non-directive interview.

[Type text]Page 11
 Requirement Specification

Requirement:
❖ User identification:
- System requires user to identify him/her using user
name and password.

❖ Login ID:
- Any user who uses the system shall have an username
and password.

❖ Modification:
- Any modification (insert and update) for database
shall be synchronized and done by user.

Technologies used
Software Specification:
Operating System: Windows 2000/XP/Vista

Front End : HTML & CSS

[Type text]Page 12
 Database : MySQL

Server: XAMPP

Design Tool: PHP

Hardware :

Processor : Intel Core i5

Memory : 8 GB RAM
Storage : 1 TB Hard Disk Space

SYSTEM DESIGN

Web Server -

[Type text]Page 13
schema diagram:
A database schema is the skeleton structure that represents the logical view of
the entire database. It defines how the data is organized and how the relations
among them are associated. It formulates all the constraints that are to be
applied on the data.
A database schema defines its entities and the relationship among them. It
contains a descriptive detail of the database, which can be depicted by means of
schema diagrams. It’s the database designers who design the schema to help
programmers understand the database and make it useful.

[Type text]Page 14
 ENTITY RELATIONSHIP DIAGRAM

Entity – Entities are person, places, events, objects or concepts.

Relationship – a relationship is a naturally occuring association among entities.

[Type text]Page 15
Types of Relationships –
1) Mandatory Relationship.
2) Optional Relationship.
3) Binary Relationship.
4) Ternary Relationship.
5) Unary Relationship.

The traditional approach places a great deal of emphasis on data storage

requirements for the new system. The model used to define the data storage
requirements is called the Entity Relationship Diagram.
Rectangles represents the data entities.
Lines connecting the rectangles show relationship among the data
entities.
ER Diagram is the high level conceptual diagram, which is based on the
perception of real world that consist of set of basic objects called entities.

So objects of ER Model are,

a) Entity Set
b) Relationships
c) Attributes

Entity is basic object of ERD, which is thing in real world with an

interdependent existence. i.e. it is distinguishable from other objects.
Among entities relationship is shown. Relationship is of type one-one,
one-many, many-one, many-many. It is also called Cardinality.
Each entity is described by set of properties called Attributes.

[Type text]Page 16
[Type text]Page 17
 DAta flow diagram(dfd)

[Type text]Page 18
 USE CASE Diagram
Use case describes the behavior of a system from a user’s standpoint by using
actions & reactions. They allow the definition of the system’s boundary & the
relationships between the system & the environment.

Use cases associated with object-oriented technique provide a complete

approach for the whole project lifecycle, from specification to implementation.
A use case corresponds to a specific king of system use. It is an image of a
system’s functionally, which is triggered in response to the simulation of an
external actor.

How to draw use case diagram -

1) Identify actors of the system.

[Type text]Page 19
 2) After identifying the role of the actors next developed the list of flow of
activities as the starting point for identifying various scenarios.

Symbols used for use case diagram-

[Type text]Page 20
 Activity DIAgRAM
[Type text]Page 21
An activity diagram is a variant of state chart diagram organized according to
actions, and mainly targeted towards representing the internal behavior of a
method or a use case. An activity is represented by a rounded rectangle.

How to develop activity diagram:

1] Identify swim length.

2] Identify input message.
3] Describe message from external actor to system using message notation.
4] Identify and add any special condition on the input messages including
iteration
and true or false condition.
5] Identify and add the output return messages.

Symbols used for Activity Diagram :

[Type text]Page 22
[Type text]Page 23
 Object Diagram

[Type text]Page 24
system Tables
Database tables:-

Admin_login:-

Name Type
Admin_id Int(20)
Admin_email Varchar(50)
password Varchar(50)

Entry register tournament:-

Name type
R_id Varchar(250)

[Type text]Page 25
Game_name Varchar(250)
Game_type Varchar(50)
Name Varchar(50)
email Varchar(50)
contact Varchar(50)
Apply_date Varchar(50)
description Varchar(250)

Feedback:-

name type
id Int(20)
name Varchar(20)
email Varchar(20)
subject Varchar(25)
about Varchar(100)

Player_details:-

name type
P_id Int(20)
Player_name Varchar(250)
Participate_game Varchar(250)
P_designation Varchar(50)
P_type Varchar(50)
Team_name Varchar(50)
P_image Varchar(250)

Schedule:-

[Type text]Page 26
name type
S_id Int(20)
S_date date
S_time Varchar(50)
groupA_team_name Varchar(50)
groupB_team_name Varchar(50)
Game_name Varchar(50)

Team_details:-

Team_id Int(20)
Team_name Varchar(50)
Team_captain Varchar(50)
Total_player Int(50)
Participate_player Int(50)
Extra_player Int(50)

Tournament:-

T_id Int(20)
game_name Varchar(250)
game_type Varchar(50)
Total_player Varchar(50)
Start_date date
End_date date
place Varchar(250)
Entry_fees Double(9,2)
Wining_price Double(9,2)

[Type text]Page 27