SPORTSPLASH

A
Project Report
on

SPORTSPLASH
BTech-IT, Sem VI

Prepared By:
Savalia Priyanshi Kailashbhai (IT127)
Sangani Kevinkumar Hiteshbhai (IT124)

Guided By:
Prof. Anand K. Patel
Dept. of Information Technology

Department of Information Technology

Faculty of technology,
Dharmsinh Desai University
College road, Nadiad- 387001

April, 2024

1
 CANDIDATE’S DECLARATION

We declare that 6th semester report entitled

“SPORTSPLASH” is our own work conducted under the supervision of the guide
Prof. Anand K. Patel.

We further declare that to the best of our knowledge the report for B.Tech. VI semester
does not contain part of the work which has been submitted either in this or any other
university without proper citation.

Candidate’s Signature:
Candidate’s Name: Savalia Priyanshi Kailashbhai
Student ID: 21ITUOS102

Candidate’s Signature:
Candidate’s Name: Sangani Kevinkumar Hiteshbhai
Student ID: 21ITUOS067

2
 DHARMSINH DESAI UNIVERSITY
NADIAD-387001, GUJARAT

CERTIFICATE

This is to certify that the project carried out in the subject of Project-I, entitled
“SPORTSPLASH” and recorded in this report is a bonafide report of work of
1) Savalia Priyanshi Kailashbhai Roll No. IT127 ID No : 21ITUOS102
2) Sangani Kevinkumar Hiteshbhai Roll No. IT124 ID No: 21ITUOS067
of Department of Information Technology, semester VI . They were involved in
Project work during academic year 2023 -20 24.

Prof. Anand K. Patel

(Project Guide),
Department of Information Technology,
Faculty of Technology,
Dharmsinh Desai University, Nadiad
Date:

Prof. (Dr.) V. K. Dabhi

Head ,
Department of Information Technology,
Faculty of Technology,
Dharmsinh Desai University, Nadiad
Date:

3
 ACKNOWLEDGEMENT

We would like to express our sincere gratitude to the IT Department at Dharmsinh

Desai University for providing us with the platform and resources to undertake our
final year project. This project would not have been possible without the unwavering
support and guidance of our department faculty members, whose expertise and
encouragement propelled us forward.

Special thanks are due to Prof. Anand K. Patel , our project supervisor, for their
invaluable insights, constant motivation, and constructive feedback throughout the
duration of this endeavor. Their dedication and mentorship have been instrumental in
shaping our project and refining our research methodologies.

We extend our heartfelt thanks to the Prof. (Dr.) Vipul K. Dabhi for their leadership
and continuous support throughout our project journey. Their guidance and
encouragement have been invaluable in shaping our academic endeavors.

We extend our appreciation to all the staff members of the [Department Name] for their
assistance and cooperation whenever needed. Their willingness to assist us with
technical issues and administrative matters has been immensely helpful in the smooth
execution of our project.

This project has been a fulfilling learning experience for us, and we are truly grateful
to everyone who has been a part of this journey.

Savalia Priyanshi Kailashbhai

Sangani Kevinkumar Hiteshbhai

4
ABSTRACT.....................................................................................................................................7
TABLES..........................................................................................................................................8
1. List Of Figures...........................................................................................................................8

2. List Of Tables...........................................................................................................................9

1. INTRODUCTION.......................................................................................................................10
1.1 PROJECT DETAILS: BROAD SPECIFICATIONS OF THE WORK ENTRUSTED TO YOU.....10
1.2 PURPOSE........................................................................................................................10
1.3 SCOPE............................................................................................................................10
1.4 OBJECTIVES..........................................................................................................................10
1.5 TECHNOLOGY AND LITERATURE REVIEW....................................................................11
2. PROJECT MANAGEMENT.....................................................................................................12
2.1 FEASIBILITY STUDY........................................................................................................12
2.1.1 TECHNICAL FEASIBILITY...........................................................................12
2.1.2 TIME SCHEDULE FEASIBILITY..................................................................12
2.1.3 OPERATIONAL FEASIBILITY......................................................................13
2.1.4 IMPLEMENTATION FEASIBILITY.............................................................13
2.2 PROJECT PLANNING......................................................................................................13
2.2.1 PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION.......13
2.2.2 PROJECT PLAN................................................................................................14
2.2.3 MILESTONES AND DELIVERABLES..........................................................14
2.2.4 ROLES AND RESPONSIBILITIES.................................................................15
2.2.5 GROUP DEPENDENCIES................................................................................15
2.3 PROJECT SCHEDULING..................................................................................................16
3. SYSTEM REQUIREMENTS STUDY.....................................................................................17
3.1 STUDY OF CURRENT SYSTEM........................................................................................17
3.1.1 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM...................17
3.1.2 USER CHARACTERISTICS............................................................................17
3.1.3 HARDWARE AND SOFTWARE REQUIREMENTS..................................18
3.2 CONSTRAINTS................................................................................................................18
3.2.1 REGULATORY POLICIES.............................................................................18
3.2.2 HARDWARE LIMITATIONS..........................................................................19
3.2.3 INTERFACES TO OTHER APPLICATIONS...............................................19
3.2.4 PARALLEL OPERATIONS.............................................................................19
3.2.5 HIGHER ORDER LANGUAGE REQUIREMENTS....................................19
3.2.6 RELIABILITY REQUIREMENTS..................................................................20
3.2.7 CRITICALITY OF THE APPLICATION......................................................20

5
 3.2.8 SAFETY AND SECURITY CONSIDERATION............................................20
3.3 ASSUMPTIONS AND DEPENDENCIES............................................................................20
4. SYSTEM ANALYSIS................................................................................................................21
4.1 REQUIREMENTS OF NEW SYSTEM..................................................................................21
4.1.1 USER REQUIREMENTS............................................................................................21
4.1.2 SYSTEM REQUIREMENTS...............................................................................22
4.2 FEATURES OF NEW SYSTEM.........................................................................................24
4.3 CLASS DIAGRAM............................................................................................................25
4.4 ACTIVITY DIAGRAM............................................................................................................26
4.5 SEQUENCE DIAGRAM..........................................................................................................27
4.6 USE CASE DIAGRAM............................................................................................................28
4.7 DATA MODELING.................................................................................................................29
4.7.1 DATA DICTIONARY.................................................................................................29
4.7.2 ER DIAGRAM.............................................................................................................31
5. IMPLEMENTATION PLANNING...........................................................................................32
5.1 IMPLEMENTATION ENVIRONMENT (SINGLE VS MULTIUSER, GUI VS NON GUI)...........32
5.2 PROGRAM AND MODULES SPECIFICATION........................................................................32
5.3 CODING STANDARDS...........................................................................................................32
6. TESTING....................................................................................................................................33
6.1 TESTING PLAN.....................................................................................................................33
6.2 TESTING STRATEGY..............................................................................................................33
6.3 TESTING METHODS..............................................................................................................33
6.4 TEST CASES.........................................................................................................................34
7. USER MANUAL........................................................................................................................35
8. LIMITATION AND FUTURE ENHANCEMENT.............................................................44
9. CONCLUSION AND DISCUSSION...................................................................................45
9.1 CONCLUSION.......................................................................................................................45
9.2 DISCUSSION..........................................................................................................................45
9.2.1 SELF ANALYSIS OF PROJECT VIABILITIES................................................45
9.2.2 PROBLEMS ENCOUNTERED AND POSSIBLE SOLUTIONS.....................45
9.2.3 SUMMARY OF PROJECT WORK......................................................................46
REFERENCES...............................................................................................................................47

6
 ABSTRACT

The dynamic sports platform presented in this project embodies a comprehensive

approach to sports management, integrating React for the frontend and Spring Boot
for the backend. This platform serves as a one-stop solution for sports aficionados,
offering a rich array of features including match creation, tournament organization,
and real-time score updates. Leveraging the power of React, the frontend interface
provides users with an immersive experience, allowing them to effortlessly navigate
through various functionalities with intuitive ease. Meanwhile, the Spring Boot
backend ensures robustness and scalability, enabling the platform to handle a
multitude of concurrent users and data-intensive operations.

Furthermore, the platform's architecture is designed with flexibility and extensibility

in mind, allowing for seamless integration of additional features and enhancements.
Future plans include the implementation of player profile management, enabling users
to create personalized profiles and track their sporting achievements. Additionally, the
platform aims to facilitate team integration by allowing users to import existing
teams, fostering camaraderie and competition within the sports community.

By harnessing the latest technologies and adhering to best practices in software

development, this project aims to revolutionize the sports management landscape.
Through continuous innovation and user feedback, the dynamic sports platform
endeavors to become the go-to destination for sports enthusiasts, providing a vibrant
and interactive hub for sports-related activities. Ultimately, the goal is to elevate the
sports experience, fostering a sense of community and camaraderie among users while
delivering unparalleled convenience and utility.

7
 TABLES

1. List Of Figures

Name Page No.

Fig 2.2.1 Agile Model 14

Fig 4.3 Class Diagram 25

Fig 4.4 Activity Diagram 26

Fig 4.5 Sequence Diagram 27

Fig 4.6 Use case Diagram 28

Fig 4.7.2 ER Diagram 31

8
 2. List Of Tables

Name Page No.

Table 2.2.4 Roles and Responsibilities 15

Table 2.3 Project Scheduling 16

Table 6.4 Test Cases 34

9
 1. INTRODUCTION

1.1 PROJECT DETAILS: BROAD SPECIFICATIONS OF THE

WORK ENTRUSTED TO YOU.

Developed a dynamic sports platform utilizing React for frontend and Spring Boot for
backend. Features include match creation, tournament management, and live score
updates. Designed to provide users with a seamless experience for organizing and
following sports events.

1.2 PURPOSE

The purpose of the project is to offer a comprehensive and interactive sports platform
that enables users to efficiently create and manage matches and tournaments while
providing real-time score updates, enhancing engagement and convenience for sports
enthusiasts and organizers alike.

1.3 SCOPE

The project encompasses the development of a dynamic sports platform utilizing

React for frontend and Spring Boot for backend. It includes features for match
creation, tournament management, and live score updates, with a focus on user
authentication, responsive UI, backend administration, scalability, and performance
optimization. Thorough testing and deployment procedures ensure reliability and
functionality.

1.4 OBJECTIVES

Goals:
1. Incorporate future scopes for player data storage and addition of new games.
2. Streamline team management by allowing direct use of existing team data.
3. Ensure scalability and flexibility to accommodate future expansions and
enhancements.
Exclusions:
1. No live match streaming.
2. No financial transactions or betting features.
3. No commentary or in-depth match analysis.

10
1.5 TECHNOLOGY AND LITERATURE REVIEW

1. Employing React.js for frontend development and Spring Boot for backend
development, facilitated by Visual Studio Code (VSCode) for frontend and
IntelliJ IDEA for backend development, to create a dynamic sports platform.

2. Utilizing MySQL as the database management system for storing match,

tournament, player, and team data, while incorporating WebSocket technology
for real-time score updates.

11
 2. PROJECT MANAGEMENT

2.1 FEASIBILITY STUDY

2.1.1 TECHNICAL FEASIBILITY

Viewing our project from a technical point of view (thinking various tools and
technologies being used in developing the system). We have decided that the
following technologies will be more than enough to develop a complete working
system (including tech. & tools used for project tracking, monitoring, etc. along
with development).
For Frontend development: VS Code
For Backend development: Intellij IDEA
Frontend: React JS
Backend: Spring boot
Database: MySql database
For testing: Postman
We are equipped with basic workflows of each tool and tech. and capable to explore
further if required. Each of the above technologies is freely available and some of
the skills are yet to be learned but it is manageable. From this, it is clear that our
project is technically feasible.

2.1.2 TIME SCHEDULE FEASIBILITY

We have planned the steps for the completion of our project in the given duration.
Firstly, we will perform requirement gathering & analysis by the mid of January
2023. We will prepare the SRS document and the GUI design tentatively by
January 2023 ending. The diagrams required for the design as well as the database
design will be tentatively completed by February 2023. For coding and unit
testing, 4 weeks and for system and integration testing another 2 weeks will be
required. Hence tentatively by the end of March 2023. We will be able to
complete the project and ready for its demonstration at starting of April 2023.
Being a 2 members team, we will be able to complete our project in the estimated
time.

12
2.1.3 OPERATIONAL FEASIBILITY

The operational feasibility of project management ensures the effective execution

of the dynamic sports platform development by assessing resource availability,
technical proficiency, system compatibility, scalability planning, user support,
regulatory adherence, risk mitigation, and cost-effectiveness. This encompasses
evaluating essential factors to ensure smooth implementation, leveraging
resources efficiently, maintaining technical excellence, and adhering to regulatory
standards while mitigating risks and optimizing costs throughout the project
lifecycle.

2.1.4 IMPLEMENTATION FEASIBILITY

We will be working on developing a full Web application for the first time. So
we need to learn the basics of the React js and Spring boot. Also, we need to learn
how to connect our project with database MySql and Learn some other things
which can be useful in our project.
Since we are well aware of the basics of React js and Spring boot we just need
to learn how to implement it according to our needs which will take around 2 or 3
weeks and be completed before starting implementation.

2.2 PROJECT PLANNING

2.2.1 PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION

We would be using the Agile model for project development. Agile methods break
tasks into smaller iterations or parts that do not directly involve long-term
planning. The project scope and requirements are laid down at the beginning of
the development process. Plans regarding the number of iterations, the duration,
and the scope of each iteration are clearly defined in advance.
Following are the phases in the Agile model are as follows:
1. Requirements gathering
2. Design the requirements
3. Construction/ iteration
4. Testing/ Quality assurance
5. Deployment
6. Feedback

13
 Fig 2.2.1 Agile Methodology

2.2.2 PROJECT PLAN

1. initiation: Define scope, roles, and tools setup.

2. Planning: Develop schedule, identify dependencies, and risk management.
3. Execution: Frontend and backend development, code reviews, and progress
monitoring.
4. Testing: Unit, integration, and user acceptance testing.
5. Deployment: Prepare, deploy, and provide documentation.
6. Post-Launch: Monitor, address issues, provide support, and document lessons
learned.

2.2.3 MILESTONES AND DELIVERABLES

1. Project Planning and Design: Develop project proposal, system architecture,

and technology stack selection.
2. Frontend Development: Create user interface design, interactive components,
and integrate with backend APIs.
3. Backend Development: Implement RESTful API endpoints, database schema,
and authentication mechanisms.
4. Database Implementation: Setup MySQL database, define data models, and
migration scripts.
5. Integration and Testing: Integrate frontend and backend, conduct
comprehensive testing, and document results.
6. User Acceptance Testing (UAT): Execute UAT, gather feedback, and obtain
stakeholder approval.

14
 7. Deployment and Launch: Deploy the platform to production environment and
provide documentation.
8. Post-Launch Support: Establish support procedures, address issues, and
perform regular maintenance.

2.2.4 ROLES AND RESPONSIBILITIES

Name Analysis Frontend Backend Testing Report

Kevin
Sangani
Priyanshi
Savalia

Table 2.2.4 Roles and Responsibility

2.2.5 GROUP DEPENDENCIES

1. Collaboration Tools: Use Slack or Teams for communication and file

sharing.
2. Version Control: Implement Git on GitHub for code management.
3. Code Reviews: Conduct regular peer reviews for code quality.
4. Meetings: Schedule regular meetings to discuss progress.
5. Knowledge Sharing: Organize sessions for team learning.
6. Documentation: Maintain thorough documentation for clarity.
7. Time Management: Set clear deadlines and manage tasks efficient.

15
 2.3 PROJECT SCHEDULING

Task Name Start Finish December January February March

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Login and 27/12/2023 07/01/2024 1 1
Register

Tournament 08/01/2024 24/01/2024 1

& 1
Team
Implementati
on
Match 31/01/2024 13/02/2024 1 1
Implementati
on
Websocket 15/02/2024 25/02/2024 1 1
and adding
more
feautures
Designing 26/02/2024 11/03/2024 1 1
and 1
deployment
Testing 13/03/2024 30/03/2024 1 1

Table 2.3 Project Scheduling

16
 3. SYSTEM REQUIREMENTS STUDY

3.1 STUDY OF CURRENT SYSTEM

3.1.1 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM

1. Scalability Challenges: Incorporating new features may strain the system's

scalability.
2. Data Management Complexity: Managing player data and team integration
could lead to data inconsistencies.
3. Dependency Risks: Relying on external data sources poses risks of data
availability and compatibility issues.
4. User Adoption Hurdles: New features may require additional user training
for smooth adoption.
5. Security Vulnerabilities: Integrating external data increases the risk of
security breaches.
6. Technical Complexity: Implementing new features may introduce
technical challenges.
7. Maintenance Overhead: Additional features may increase the maintenance
workload.

3.1.2 USER CHARACTERISTICS

Organizers:
These users are responsible for creating and managing sports matches and
tournaments within the platform.
They have privileges to schedule matches, define tournament rules, and manage
participant registrations.
Players:
Players actively participate in sports matches and tournaments organized within
the platform.
They interact with the system to register for events, view match schedules, and
access live score updates during games.
Spectators:
Spectators follow sports events organized on the platform but do not actively
participate as players or organizers.
They use the system to match schedules, access live score updates, and follow
game progress in real-time.

17
3.1.3 HARDWARE AND SOFTWARE REQUIREMENTS

There are no such specific hardware requirements other than basic

requirements such as a computer with good internet connectivity .
Software: -
Operating System: Windows Operating System
Visual Studio Code
Intellij IDEA
Browser
MySql database
Postman
MySql: MySQL is a powerful relational database management system renowned
for its reliability, scalability, and performance. It offers robust data storage and
management capabilities, making it a preferred choice for businesses and
developers worldwide.
Visual Studio Code: Visual Studio Code (VSCode) is a top choice for frontend
development and website creation, offering robust features and extensions for
efficient coding workflows and seamless project management.
Intellij IDEA: IntelliJ IDEA excels as the go-to IDE for Spring Boot
development, offering unparalleled coding assistance and seamless integration
with Spring frameworks. Its advanced features and intuitive interface empower
developers to build high-quality Java applications efficiently.

3.2 CONSTRAINTS

3.2.1 REGULATORY POLICIES

1. Data Protection: Ensure compliance with data protection laws (e.g., GDPR,
CCPA) for handling user data, including personal information collected during
registration and participation.
2. Intellectual Property Rights: Respect copyrights and obtain proper licensing
for third-party content used on the platform to avoid infringement and legal
issues.
3. Compliance Monitoring and Reporting: Implement continuous monitoring and
reporting procedures for regulatory compliance, particularly concerning the
online platform's operations and user data management.

18
3.2.2 HARDWARE LIMITATIONS

There are limitations of this web app, the device must have a browser and JDK
installed on it.

3.2.3 INTERFACES TO OTHER APPLICATIONS

Integration with Player Data Systems:

Develop interfaces to seamlessly sync player data with external systems, such as
sports management databases or player registration platforms, to ensure accurate
and up-to-date player information across platforms.
Game Data Exchange with Sports APIs:
Implement interfaces to interact with sports APIs (e.g., ESPN API) for real-time
game data retrieval and analysis, enhancing the platform's functionality with live
scores, player stats, and game updates sourced from authoritative sports sources.

3.2.4 PARALLEL OPERATIONS

The dynamic sports platform allows concurrent operations such as match creation,
tournament management, and live score updates. Utilizing React for the frontend
and Spring Boot for the backend facilitates parallel processing, ensuring seamless
execution of tasks like player data storage and game expansion while maintaining
platform stability and responsiveness.

3.2.5 HIGHER ORDER LANGUAGE REQUIREMENTS

The platform requires robust concurrency support for smooth operations in match
creation, tournament management, and live score updates. It must scale efficiently
to handle increased data and user load while seamlessly integrating with external
systems for player data storage and sports API access. Additionally, a modular and
extensible architecture is vital to facilitate future enhancements without extensive
redevelopment efforts.

19
3.2.6 RELIABILITY REQUIREMENTS

The platform must guarantee high availability to ensure uninterrupted access to

match creation, tournament management, and live score updates. It should
maintain data integrity to prevent loss or corruption of player data and match
records, fostering user trust. Additionally, implementing fault-tolerant mechanisms
is crucial to mitigate the impact of potential errors or failures on system
functionality and user experience.

3.2.7 CRITICALITY OF THE APPLICATION

Real-Time Functionality:
The application's ability to provide real-time match creation, tournament
management, and live score updates is critical, as any delays or disruptions could
adversely impact user experience and the integrity of sports events.
Data Integrity and Reliability:
Ensuring the integrity and reliability of data, including match records and live
scores, is crucial for maintaining the accuracy and credibility of the platform,
thereby preserving user trust and satisfaction.

3.2.8 SAFETY AND SECURITY CONSIDERATION

Data Encryption:-
Ensure robust encryption for data transmission to safeguard sensitive information
and prevent unauthorized access.
Authentication and Authorization:-
Implement secure authentication methods to verify user identity and enforce
proper access controls, enhancing platform security and protecting against
unauthorized actions.

3.3 ASSUMPTIONS AND DEPENDENCIES

1. Users have sufficient privileges to access the internet.

2. browser on the Device is running smoothly.
3. Database updates are giving expected and accurate results.

20
 4. SYSTEM ANALYSIS

4.1 REQUIREMENTS OF NEW SYSTEM

4.1.1 USER REQUIREMENTS

User Registration and Authentication:

Users should be able to register for accounts and authenticate securely to access
platform features, including match creation, tournament management, and live score
updates.

Intuitive User Interface:

The frontend interface should be user-friendly and intuitive, allowing users to
navigate easily and efficiently create matches, manage tournaments, and view live
score updates without confusion.

Match and Tournament Creation:

Users should have the ability to create matches and tournaments easily, specifying
details such as date, time, location, and rules, to facilitate organized sports events on
the platform.

Live Score Updates:

Users should receive real-time updates on match scores and tournament standings,
enabling them to stay informed and engaged with ongoing sports events.

Accessibility and Compatibility:

The platform should be accessible across various devices and screen sizes, ensuring
compatibility with different browsers and providing a seamless user experience for all
users.

21
4.1.2 SYSTEM REQUIREMENTS

Functional Requirements:
1. User Login:

Input: User enters login credentials (username/email and password).

Output: Successful authentication redirects the user to the home page.
2. User Registration:

Input: User provides registration details such as username, email, and password.
Output: Confirmation of successful registration and redirection to home page.
3. Match Creation:

3.1 User need to select game:

Input: User submits details for a new match, including date, time, and team size.
Output: User need to click on next button. Next button will be changed to edit
button.
3.2:
Input: User need to enter teams name and players name for the teams and you will
get player according to team size.
Output: Confirmation of successful match creation.
Post Condition: Users will see in their profile that the match that has been created
by them. In the Home page by clicking on matches you can see that the match will
be in upcoming portion.
4. Tournament Creation:

4.1 User need to select game:

Input: User need to submit details such as tournament name, start date, end
date, number of teams, team size.
Output: Confirmation of successful tournament creation.it will redirect to that
tournament page.
4.2 User add teams:
Input: User need to select add team in that tournament and add team names.
Output: Confirmation of team created successfully.
4.3 User click create-match option:
Input: User need to filled up details such as teams, start date and start time.
Output: Confirmation of successful match creation.

22
4.4 Matches:
Input: User select matches option.
Output: Get all the matches for that tournament.
Post Condition: Tournament will be added to that user profile who has create
that tournament. Tournament will be added to the home page and tournaments.
4.5 Start Match:
Input: Click on start match option.
Output: User will redirect to the match page where user can add points for
teams.
Post condition: Users can see live scoring of matches in matches section from
home page.
4.6 End Match:
Post condition: Users will be able to see key points of the match.
5. User Dashboard:

Input: User navigates to the home page.

Output: Display of information such as matches, tournaments, contact us.
5.1 Tournaments:
Input: User Click on the Tournaments.
Output: User will get the information regarding all tournaments and particular
game tournament.
Post Condition: By Clicking on the any tournament it will be redirected to the
tournament page.
5.2 Matches :
Input: User Click on matches.
Output: User can see ongoing, upcoming and completed matches.
5.2.1 upcoming matches:
Input: Click on any upcoming match.
Output: User will get redirected to the match page.
5.2.2 ongoing matches:
Input: Click on any ongoing match.
Output: User will get redirected to the match page and can see scores.
5.2.3 complete matches:
Input: Click on any completed match.
Output: User will be redirect to the match page and can see summary of that match.

23
6. Contact US:

Input: User fills out the contact form with message details.
Output: Email is sent to the creators of the website with the user's message.
7. Profile Management:

In the Profile page, User can see matches and tournaments created by them.
Input: User clicks on the logout button.
Output: Session is terminated, and user is redirected to the home page.

Non-Functional Requirements:
1. Performance: Ensure quick response times and scalability to handle concurrent
users and data loads efficiently.

2. Security: Implement robust authentication, encryption, and adhere to industry-

standard security practices to protect user data.

3. Scalability: Design the system to scale seamlessly with user growth and
feature expansion without compromising performance.

4. Reliability: Maintain high reliability with minimal downtime, data integrity

mechanisms, and regular backups to prevent data loss.

5. Usability: Provide an intuitive and user-friendly interface with clear

navigation and helpful documentation for user assistance.

6. Compatibility: Ensure compatibility with various browsers and devices for a

consistent user experience across platforms.

7. Maintainability: Facilitate easy maintenance and updates with well-structured

code, modular architecture, and comprehensive documentation for developers.

4.2 FEATURES OF NEW SYSTEM

Predictive Analytics and Match Insights:

1. Implement predictive analytics algorithms to forecast match outcomes based
on historical data and player/team performance metrics.
2. Offer users match insights and recommendations to help them make informed
decisions when creating or participating in matches and tournaments.

24
Social Sharing and Engagement Features:
1. Enable users to share match results, tournament updates, and player
achievements on social media platforms directly from the platform.
2. Foster community engagement by allowing users to like, comment, and share
content within the platform.

4.3 CLASS DIAGRAM

Fig 4.3 Class Diagram

25
4.4 ACTIVITY DIAGRAM

Fig 4.4 Activity Diagram

26
4.5 SEQUENCE DIAGRAM

Fig 4.5 Sequence Diagram

27
4.6 USE CASE DIAGRAM

Fig 4.6 Use case Diagram

28
4.7 DATA MODELING

4.7.1 DATA DICTIONARY

User:
Attributes:
Email (Email address of the user)
FirstName (First name of the user)
LastName (Last name of the user)
University (University affiliation of the user)
Password (Encrypted password for authentication)
MobileNo (Mobile number of the user)

Tournament:
Attributes:
TournamentID (Unique identifier for each tournament)
TournamentName (Name of the tournament)
TeamSize (Maximum number of players per team)
Teams (List of teams participating in the tournament)
IsDefault (Flag indicating if the tournament is default or custom)
StartDate (Date when the tournament begins)
EndDate (Date when the tournament ends)

Team:
Attributes:
TeamID (Unique identifier for each team)
TeamName (Name of the team)

Player:
Attributes:
PlayerID (Unique identifier for each player)
PlayerName (Name of the player)

29
TeamID (ID of the team to which the player belongs)

Match:
Attributes:
MatchID (Unique identifier for each match)
Team1Score (Score of team 1)
Team2Score (Score of team 2)
StartTime (Start time of the match)
EndTime (End time of the match)
Winner (ID of the winning team)

30
4.7.2 ER DIAGRAM

Fig 4.7.2 ER Diagram

31
 5. IMPLEMENTATION PLANNING

5.1 IMPLEMENTATION ENVIRONMENT (SINGLE VS

MULTIUSER, GUI VS NON GUI)

Single vs Multiuser: The implementation environment for the dynamic sports

platform is multiuser, as it caters to multiple users interacting with the system
simultaneously. Users can create matches, manage tournaments, and view live score
updates concurrently.
GUI vs Non-GUI: The implementation environment utilizes a Graphical User
Interface (GUI) for frontend interaction. Users interact with the system through
intuitive graphical elements and visual representations provided by the React
frontend. This GUI facilitates easy navigation and interaction with the platform's
functionalities, enhancing user experience and usability.

5.2 PROGRAM AND MODULES SPECIFICATION

Frontend Modules (React): User Authentication, Match Creation, Tournament

Management, Live Score Updates, Dashboard, Profile Management, Contact Us.
Backend Modules (Spring Boot): User Authentication, Match & Tournament
Management, Live Score Updates, Database Management, Email Service, Logging &
Error Handling.

5.3 CODING STANDARDS

To make the system coding easy, easy to remember, and reduce the chances of errors,
some techniques are used at the time of coding of the application which is called
coding standard. The coding standard which we adopted during the coding is
explained as follows:
1. Each nested block should be properly indented and spaced.
2. The code should be properly commented on for understanding easily.
3. Comments regarding the statements increase the understandability of the code.
4. Better to avoid the use of digits in variable names. The names of the function
should be written in camel case starting with small letters.
5. The name of the function must describe the reason for using the
function clearly and briefly.

32
 6. TESTING

6.1 TESTING PLAN

The testing technique that is going to be used in the project is White box testing. In
White box testing the Tester knows the internal structure of the code or the program of
the software.

6.2 TESTING STRATEGY

The development process repeats this testing subprocess several times for the
following phases.
a) Unit Testing.
b) Integration Testing
Unit Testing tests a unit of code (module or program) after the coding of that unit is
completed.
Integration Testing tests whether the various programs that make up a system,
interface with each other as desired, fit together and whether the interfaces between
the programs are correct.
Testing is carried out in such a hierarchical manner to ensure that each component is
correct and the assembly/combination of components is correct. Merely testing a
whole system at the end would most likely throw up errors in components that would
be very costly to trace and fix.

6.3 TESTING METHODS

Black Box and White Box Testing:

In black-box testing, a software item is viewed as a black box, without knowledge of
its internal structure or behavior. Possible input conditions, based on the specifications
(and possible sequences of input conditions), are presented as test cases.

In white-box testing knowledge of internal structure and logic is exploited. Test cases
are presented such that possible paths of control flow through the software item are
traced. Hence more defects than black-box testing are likely to be found.

33
 Out of the 2 methods for testing, black box testing and white box testing, we would be
using the white box testing as we are well aware of the internal functionalities of our
application unlike the black box testing, where we require a 3rd party to test our cases
and the internal details are hidden from him.

6.4 TEST CASES

Entity Test Case Expected Output Actual Output Result

Login / Validation Successfully Login/ Successfully Login/ Pass

Registartion Successfully Successfully
Registered Registered
Home Page View Home View Homepage View Homepage Pass
Details Successful Details Successful

Add Tournament Add Tournament Pass

Tournament Created Tournament Created
Successfully Successfully

Add Team Add Team Team added Team added Pass

Successfully Successfully

Add Player Add Player Player added Player added Pass

Successfully Successfully

Create Match Create Match Match created Match created Pass

Successfully Successfully

WebSocket Implement WebScoket Real -Time Score Real-Time Score Pass

Updation Successful Updation Successful

34
 7. USER MANUAL

User Manuals are manuals that enable the user of a system or application to
understand the working of the system and help them to use them efficiently. It is
usually written by a technical writer, although user guides are written by
programmers, product or project managers, or other technical staff, particularly in
smaller companies.
Follow below mentioned steps to work with the app:

Home Page:

 This is Home Page. Click on the create for login/register.

35
  Now, Click on the create button , You will get two options create match and
create Tournament.

Create Match:

 Click on the Create Match , you will get cards for selecting game.

36
 After selecting game , you will get dialogue box for adding match
information.

 Click on the submit button and you will be redirected to that match page.

37
 Click on the start match, Enter the required score for Badminton Match.

38
 You can see Live Score in the Matches.

 After end of Match.

39
Create Tournament:

 Click on the Create Tournament.

 By Selecting on the Game, You will get the dialogue box for adding
tournament information.

40
 Click on the add team.

 Click on the Create-Match.

41
 Click on the Create ,Match will be created.

 Clicking on the card, you can start the match.

42
Contact :

Profile:

43
 8. LIMITATION AND FUTURE ENHANCEMENT

• Limitations:

1. Compatibility Issues: Ensuring seamless user experience across diverse

platforms is critical for widespread accessibility.

2. Complexity of Real-Time Updates: Managing WebSocket connections or

long-polling mechanisms introduces intricate system architecture challenges.

3. Scalability Challenges: Accommodating increased user traffic and data volume

necessitates careful planning and optimization for sustained performance.

4. Security Concerns: Robust security measures are essential to safeguard

sensitive user data and prevent unauthorized access or breaches.

 Future Enhancement:

1. Player Profile Management: Enable users to create and manage personalized

profiles, enhancing user engagement and interaction.
2. Team Management Integration: Streamline team creation and participation by
integrating existing teams from our database and external resources, fostering
community engagement.
3. Notification and Reminder System: Implement a robust system to notify users
about upcoming events, improving user engagement and participation.
4. Social Features Integration: Foster community interaction through social
features like chat and forums, enhancing user engagement and retention.
5. Expanded Game Options: Diversify gaming experiences by adding support for
additional sports and games, catering to a broader audience

44
 9. CONCLUSION AND DISCUSSION

9.1 CONCLUSION

According to us, this project gave all of us the confidence to believe in ourselves and
a great experience of how to work as a team. It also boosted our requirement
gathering, system analysis, designing aspects, technical coding as well as time
management skills. Also we learned how to work together as a team & collaborate for
making ends meet for our web app. We also got an insight into how we would have to
work in future at job or startup & how we have to contribute for the good of the entity
we are working.

9.2 DISCUSSION

9.2.1 SELF ANALYSIS OF PROJECT VIABILITIES

According to us, this project is absolutely a good start for gaining hands-on
experience on projects. It is useful if it is managed according to the goal for which it
is made.

9.2.2 PROBLEMS ENCOUNTERED AND POSSIBLE SOLUTIONS

Problems:
1. Maintenance of Website: The website faces technical challenges related to
regular maintenance tasks, updates, and ensuring optimal performance over
time.
2. Data Redundancy: Technical issues arise concerning redundant data storage,
leading to inefficiencies in data management and storage utilization.
3. Effective Teamwork: Non-technical challenges emerge in fostering effective
collaboration and coordination among team members, impacting project
progress and productivity.
Solutions:
1. Maintenance of Website: Implement automated maintenance scripts and
regular performance audits to streamline upkeep tasks and ensure consistent
functionality.
2. Data Redundancy: Employ database normalization techniques and data
cleanup processes to optimize storage efficiency and eliminate redundant data
entries.

45
 3. Effective Teamwork: Foster open communication channels, establish clear
roles and responsibilities, and encourage teamwork through regular meetings
and collaborative tools.

9.2.3 SUMMARY OF PROJECT WORK

It is a great achievement to successfully complete the project. The prior

knowledge of software engineering has helped immensely in overcoming the various
roadblocks. We have done work with pre-planned scheduling related with time
constraints and weekly progress in project development. Also we received guidance
from Prof. Anand K. Patel at all stages of our project which helped in overall
betterment of the project.
All in all, it was a beautiful experience which taught us many things needed to
succeed further in life during our jobs.

46
 REFERENCES

 Stackoverflow: https://stackoverflow.com

 Youtube: YouTube

 DevUI: https://www.devui.io/

 Npm: https://www.npmjs.com/

 Draw.io: https://draw.io/

 Geeksforgeeks: https://www.geeksforgeeks.org/

 Repository Link: https://github.com/Kevin0403/SportSplashServer

 https://github.com/Kevin0403/SportSplash

47