Sports Club
Sports Club
Project Report
On
Sports Club Management System
Submitted for
Partial fulfillment of the Bachelor in Computer
Application (BCA-Sem-6)
Submitted By Guided By
Bansi B. Patel Mr. Kiran Fatepara
Seat No : 25260451 Asst. Prof.
MARCH-APRIL-2023
Compile by
Bhumika Parmar
Bansi Patel
PREFACE
~I~
SPORTS CLUB MANAGEMENT SYSTEM
ACKNOWLEDGEMENT
First of all, I would like to thank the Almighty god without whom this task
would have not been achieved. I express my sincere and profound gratitude
to our principal of Adarsh BCA College Mr. Sanjay Hadiyal for their
encouragement and support to do my project in our computer lab. My
special thanks to my guide Mr. Kiran Fatepara, who gave me the needed
information and support for the successfully completion ofthis project. And
helped us with their suggestion to make the project better. I take this
opportunity to thank all the staff members who rendered their help directly
to finish my project in time. Last but not the at least, I would like to express
my hearty thanks to my parents, without whom I would not have come to
this level in my life. My hearty thanks to my friends and well wishers who
supported and encouraged me to complete this project successfully.
Bhumika G. Parmar
Bansi B. Patel
~II~
SPORTS CLUB MANAGEMENT SYSTEM
INDEX
No. Title Page no.
Chapter:1 (Introduction)
1.1 Background 4
1.2 Objective 6
1.3 Purpose 7
1.4 Scope 8
1.5 Applicability 9
Chapter:2 (Requirement and Analysis)
2.1 Problem definition 11
2.2 Requirement specification 12
2.3 Hardware software requirement 13
2.4 Planning and scheduling 14
Chapter:3 (System Design)
3.1 Overall system design using designing tools 18
3.2 Data dictionary 32
3.3 Input / output design 49
Chapter:4 (Testing and Implementation)
4.1 Testing approach used 77
4.2 Test cases 81
4.3 Implementation approaches 85
Chapter:5(conclusion)
5.1 Conclusion 87
5.2 Limitation of system 88
5.3 Future scope of system 89
5.4 Bibliography 90
~III~
SPORTS CLUB MANAGEMENT SYSTEM
LISTS OF FIGURES:-
~IV~
SPORTS CLUB MANAGEMENT SYSTEM
LISTS OF TABLES: -
~V~
SPORTS CLUB MANAGEMENT SYSTEM
Chapter-1 (Introduction)
Information to Project
Background
Objective
Purpose
Scope
Applicability
Introduction
A Sports club management system project that provides and manages various
sports club activities such as member registration, registration for games events
and tournaments etc.
The sports club management system is built keeping in mind various daily
activities of the club.
Project Profile
1.1 Background
Front End
ASP.NET:-
Back End
SQLServer– 2005: -
SqlServer is a relational model database server produced by Microsoft. It is
made up several different client and server programs that make up the entire products.
There is no need to install SQLServer software. It is inbuilt in Visual Studio. There are
two way to working with SQLServer wizard
and coding.
1.2 Objective
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.
The software categorizes its visitors into different games and presents them with the
respective functionality as per their level of access.
A new user can register for club membership and book the registration for desired
tournament. A new user can also enroll in the activities of the sports club.
The admin is the only person that can approval a tournaments, schedule and activities.
The tournament is presented by selecting the team by the admin.
The admin can keep the system updated all the time for the players so that the players
don’t have to face any problem while the players sports and can get the update
information all the time.
1.3 Purpose
The main purpose of building this management system is to manage the whole
system online so that all the work goes in a very systematic manner.
The system stores and sends all the members detail to the admin for request.
In this system, the main role is of players who can become the members of this
club by doing registration and then can attend the sports activities. Players can
view their profile.
Sports club management system is prepared for providing all the necessary
things which is needed by the sports player.
This system will also keep the online record of all participate sports events in
their database so that there is no any loss of data take place.
The system is easy to use and saves humans efforts and cost.
1.4 Scope
The website will provide a competitive and it will facilitate the game to the
player. As it is web based it can provide services in almost each and every city of
India.
1.4 Applicability
Sports club exist to promote and develop interest in a sport or physical activity.
Besides keeping the player physically strong, the sports club serves to join the
sport team and lead towards the goals.
Sports club players are apply to use the playing ground and participate in events
and tournaments.
Problem definition
Requirement Specification
Hardware software requirement
Planning and scheduling
We can say that earlier all the system was handled manually in which the
administrator had to maintain the register which leads to loss of data and security
problem issue was being faced.
Currently, the process of managing the sports club is file based and manual.
For example, a new user wants to enroll in a training batch he/she has to visit the
club and fill up the registration form. The form then passes through a hierarchy of
club members before approval. It takes time as well as effort from a user’s
perspective.
This is just a single case. Same problem persists in all the major operation of the
club.
So now, the management has decided to design an online system so that all the
things get automatically updated and kept safe in the database.
Functional Requirement
Function requirements define the specific functions that the system performs, with
the data operated on by the functions. The functional requirement is presented in
scenarios that depict an operational system from the perspective of its end users.
Included are system features and an enumeration of all the specific requirements
associated with these features.
Nonfunctional Requirement
Usability
o The system must be quickly accessible by both manager and chefs.
o The menus of the system must be easily navigable by the users with
buttons that are easy to understand.
Reliability
o The system must successfully add any recipe, ingredients, vendors or
special occasions given by the user and provide estimations and
inventory status in relevance with the newly updated entities.
Performance
o All the function of the system must be available to the user every time
the system is turned on.
Packaging
o The packaging must come with a manual that details the use of the
system and also the instruction on how to use the program.
Planning
Requirements
Analysis
Design
Coding
Testing
Maintenance
Analysis
Design
Designing of master page forms and other design aspect will complete up
to 35 days period I get confused a lot in the case of choosing designing
aspect such temples for Homepage and Master page.
Designing of database consume a human time.
Various type of table I have to arrange with its data type and fields.
Coding
Testing
I have completed all testing of web site with algorithm and query in time
10-12 days
Schedule
Project plan
Designing of
master page
and creating
Forms
DECEMBER Designing of Implement the Implement the Designing
Database and first and second coding of all Diagrams such
Tables. chapter of Admin forms as UML
documentation. diagrams
Chapter-3(System Design)
Introduction: -
Design is the first step in the development phase for any techniques and
principles for the purpose of defining a device, a process or system in sufficient detail to
permit its physical realization.
Once the software requirements have been analyzed and specified the software
design involves three technical activities-designs, coding, implementation and testing
that are required to build and verify the software.
The design activities are of main importance in this phase, because in this
activity, decisions ultimately affecting the success of the software implementation and
its ease of maintenance are made. These decisions have the final bearing upon
reliability and maintainability of the system. Design is the only way to accurately
translate the customer’s requirements into finished software or a system.
UML Diagram
UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product
after analysis. The goal from this is to produce a model of the entities involved in the
project which later need to be built. The representation of the entities that are to be
used in the product being developed need to be designed.
Use case diagram consists of actors, use cases and their relationship. The diagram
is used to model the system of an application. A single use case diagram captures a
particular functionality of a system. Hence to model the entire system, a number of use
case diagram are used.
Following are different elements that are used in use case diagram.
Notation Symbols
Use case
Actor
Communication
Include
Exclude
Oval
System Boundary
User Side:-
Membership
Add
Membership
Team
Registration
Show
Schedule
Player
Registration
R
Tournaments
User
Game
Facilities
Feedback
Logout
Admin Side:-
Membership
Gallery
Add Games
Add/Update
Tournaments
Facilities
Schedule
View Detail
Admin
Feedback
Contact Us
Logout
Activity Diagram
Activity diagram is basically a flowchart to represent the flow from one activity
to another activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using
different elements such as fork, join, etc.
Notation Symbols
Starting
Activity
Decision
Stop
Action/Control
Flow
Transaction(fork)
Joint transaction
User Side:-
Start
Login
No
Yes
Valid
Logout
Stop
Admin side:-
Start
Login
No Yes
Valid
Maintenance Website
Logout
Stop
Class Diagram
Class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modeling of object-
oriented systems because they are the only UML diagram, which can be mapped
directly with object-oriented language.
The purpose of the class diagram is to model the static view of an application. Class
diagrams are the only diagrams which can be directly mapped with object-oriented
language and thus widely used at the time of construction.
• The name of the class diagram should be meaningful to describe the aspect of the
system.
• Each element and their relationships should be identified in advance.
• Responsibility of each class should be clearly identified.
• For each class, minimum number of the properties should be specified, as
unnecessary properties will make the diagram complicated.
• Use notes whenever required to describe some aspect of the diagram. At the end
of the drawing it should be understandable to the developer.
• Finally, before making the final version, the diagram should be drawn on plain
paper and reworked as many times as possible to make it correct.
Notation Symbols
Class Class
Class
Generalization
Class Class
Package
Class
Interface
Contact us
- name: string
User Login - email: string
- eid: string - phone: int
- pass: string - sub: string
- mess: string
+ login () + add ()
+ add () + view ()
+ edit ()
+ delete()
+ delete ()
Registration
- name: string
- gender:string
- eid: string
- pass: string
- contact: int Admin
- address: string - eid : string
+ accept () - pass: string
+ reject () + login ()
+ add ()
+ edit ()
Player Registration + delete ()
- pid: int
- fullname: string
Feedback - unm: string
- gender: string
- name: string
- desin: string
- email: string
- add: string
- phone: int
- con: int
- opinion: string
- join_dt: int
+ add ()
- height: float
+ edit ()
- weight: int
+ delete ()
- g_name: string
+ add()
+delete()
+display ()
Structure Chart
Admin User
Show game
Player Team
Registration Registration
Data tables:-
Admin login:-
Column Name Data Type Description
User Login:-
Column Name Data Type Description
Sub Gallery:-
Name Data Type Description
Gallery:-
Tournaments:-
Column Name Data Type Description
Player registration:-
Column Name Data Type Description
Add Schedule:-
Column Name Data Type Description
Game:-
Column Name Data Type Description
Join Membership:-
Column Name Data Type Description
Team Details:-
Column Name Data Type Description
Contact Us:-
Column Name Data Type Description
Feedback:-
Column Name Data Type Description
Facilities:-
Column Name Data Type Description
Listbox:-
Column Name Data Type Description
Admin Side
This is page for admin login. Admin can login from entering a email id and password .by
providing correct username and password an admin switch to home page.
This is admin master page. There are use to master page are equal to all
pages are designs. In master page are menu and logout.
This is add gallery image page. Admin can add the gallery image then user
can show the gallery.
This is a add sub gallery page. Admin can add the sub gallery image.
View Gallery:-
This is a view gallery page. Admin can show the added game’s image.
View Membership:-
This is a view membership page. Admin can view member joined in the
club.
Add Games:-
This is a add games page. Admin can add the game then user can show the
different games.
View Games:-
This is a view games page. Admin can view the added different games.
Add Facilities:-
This is an add facilities page. Admin can add the facilities for users then
user use the facilities.
View Facilities:-
This is a view facilities page. Admin can view the added facilities.
Add Tournaments:-
This is a add tournaments page. Admin can add the tournaments then user
can show the tournaments.
Check Tournaments:-
This is a check tournaments page. Admin can view the added tournaments.
Add Schedule:-
This is page for add schedule. Admin can add the schedule then user can
show the upcoming events.
Check Schedule:-
This page is a check schedule. Admin can view the upcoming events of the
club.
User Detail:-
This page is a user detail. Admin can view the user registration detail.
Team Detail:-
This page is a team detail. Admin can view team registration detail.
Player Detail:-
This is a player detail page. Admin can view the registered players in the
club.
Feedback:-
This page is a feedback page. Admin can view the feedback by the users.
Contact Us:-
This page is a contact us page. Admin can show the user queries.
User Side
User Login:-
This is user login page. User can enter from user id and password for login.
This is user login before page. They can view all menus before user login.
Registration Page:-
This is a user home page. The user can access all the menus in sports club.
Game:-
This is a game page. User can view the various games and it’s information.
About Membership:-
This is a about membership page. User can view the detail of membership.
Join Membership:
This is a join membership page. User can become a member of the sport
club by taking appropriate membership.
Facilities:-
This page is a facilities. User can view the available facilities in the sports
club.
Team Registration:-
This is a team registration page. The user can register their team in sports
club.
Schedule:-
This is a schedule page. User can view the schedule of upcoming events.
Player Registration:-
This is a player registration page. The user can register their information as
a player.
Tournaments:-
This is a tournaments page. The user can view the upcoming tournaments.
This is a show player detail page. The player can find his lost data.
Gallery:-
This is a gallery page. The user can view the images of the sports.
About Us:-
This is an about us page. The user can view the all information of the sports
club.
Feedback:-
This is a feedback page. User can share the own opinion for sports club.
Contact Us:-
This is a contact us page. The user can contact the sports club for own
query.
Black-Box Testing
Black box testing also called behavioral focuses on the functional requirements of the
software.
That is black box testing enables the software engineer to device sets of input
conditions that will fully exercise all functional requirements for a program.
When we can test the system whose inside working or coad are not available for
inspection or testing.
Interface errors.
Incorrect or missing function.
Errors in database access.
Performance errors.
Initialization errors.
White-Box Testing
White-Box testing is concerned with testing the implementation of the program.
The intent of this testing is to exercise the different programming structures and data
structures used in the program.
White-Box testing, sometimes also called glass-box testing is a test case design method
that uses the control structure of the procedural design to derive test cases.
Two types of path testing are 1.Statment based testing 2.Branch based testing.
While White-Box testing can be applied at the unit, integration and system levels of the
software testing process, it is usually done at the unit level.
Testers examine the software code and documentation but don’t execute the program.
Static test starts early in the product development during the verification process.
GUI Testing
These test GUI (Graphical user in textboxes, buttons, layouts, colors, fonts, font size.
GUI Testing is time consuming and this is test by client instead of developers.
A software testing method which is combination of black box testing and white box
testing this called gray box testing.
Gray box testing is a technique to test the application with having a limited knowledge
of the internal working of an application.
In software testing, the phrase the more you know, the better carries a lot of weight
while testing an application.
In grey-box testing, the tester has access to design documents and the database. Having
this knowledge, a tester can prepare better test data and test scenarios while making a
test plan.
Test description: “User enters the Email id and Password fields, presses Login
button”, player contacts with server, server contacts with the database, database
updates and sends result to the user.
Test Setup/pre-Conditions: SQL must be in running state, All the mandatory fields
must be entered.
The user will register to access “Login successfully”, Display main menu.
application.
Pass:Yes ,Condition pass: Yes Fail: No
Test description: “User enters the required fields, presses Register button”, client
program contacts with server, server contacts with the database, database updates
and sends result to the user.
Test Setup/pre-Conditions: SQL should be in running state, All the mandatory fields
must be entered.
The user will register to access “Registered successfully”, Display main menu.
application.
Pass: Yes, Condition pass: Yes Fail: No
Test description: “User clicks the player registration link button, and then enters the
required details, player contacts with server, server contacts with the database,
database updates and sends result to the user.”
Requirements Verified: yes
Test Setup/pre-Conditions: SQL should be in running state, All the mandatory fields
must be entered.
The user will add the details to the “yes”, Display main menu.
database.
Pass: Yes, Condition pass: Yes Fail: No
Test description: “User clicks the team registration link button, and then enters the
required details, player contacts with server, server contacts with the database,
database updates and sends result to the user.”
Requirements Verified: yes
Test Setup/pre-Conditions: SQL should be in running state, All the mandatory fields
must be entered.
The user will add the details to the “Register Successfully”, Display main menu.
database.
Pass: Yes, Condition pass: Yes Fail: No
Direct cutover
Direct cutover method is an implementation process that involves essentially
“switching off” the current system entirely and “switching on”
the new system to take its place all at once.
Pilot
Pilot method involves setting up the system for a small group of users and
participants, while the remaining majority of users and participants still interact
with the current system.
It is a combination of the direct cutover and parallel operation method.
In this method, a working version of the system is implementation in one part of
the organization, such as a single work area or single department.
Phase-In
Phase-In method can allow you implement the system at in stages or modules.
It can be used when it is not possible to install a new system throughout an
organization all at once.
Chapter-5(conclusion)
Conclusion
Limitation of system
Future scope of system
Bibliography
5.1 Conclusion
5.4 Bibliography
Webliography
www.w3schools.com
www.google.com
www.youtube.com
www.onlineproject.com