CP-II Project Report on

PlayTracker
at
U. V. Patel College of Engineering

Internal Guide : Prepared By:

Prof. Manan Thakkar Mr. Himanshu Modi(21012011051)
Mr. Aditya Mishra(21012011050)
Mr. Krish Darji(21012011016)
Ms. Vedanshee Patel(21012021092)

B.Tech Semester V
(Computer Engineering/Information Technology)
December 2023

Submitted to,
Department of Computer Engineering / Information Technology
U.V. Patel College of Engineering
Ganpat University, Kherva – 384 012
 U.V. PATEL COLLEGE
OF
ENGINEERING

DD/MM/YY

CERTIFICATE

TO WHOM SO EVER IT MAY CONCERN

This is to certify that Mr. Himanshu Modi student of B.Tech. Semester

V (Computer Engineering) has completed his full semester Capstone
Project work titled “PlayTracker” satisfactorily in partial fulfillment of
the requirement of Bachelor of Technology degree of Computer
Engineering of Ganpat University, Kherva, Mehsana in the year 2023-
2024.
Sign
Dr. Pare Head, Computer
Engineering
Prof. Manan Thakkar

U.V. PATEL
COLLE
GE OF
ENGINEERING

DD/MM/YY

CERTIFICATE
 TO WHOM SO EVER IT MAY CONCERN

This is to certify that Mr. Aditya Mishra student of B.Tech.

Semester V (Computer Engineering) has completed his full
semester Capstone Project work titled “PlayTracker” satisfactorily in
partial fulfillment of the requirement of Bachelor of Technology
degree of Computer Engineering of Ganpat University, Kherva,
Mehsana in the year 2023-2024.
 U.V. PATEL COLLEGE
OF
ENGINEERING

DD/MM/YY

CERTIFICATE

TO WHOM SO EVER IT MAY CONCERN

This is to certify that Mr. Krish Darji student of B.Tech. Semester V

(Computer Engineering) has completed his full semester Capstone Project
work titled “PlayTracker” satisfactorily in partial fulfillment of the
requirement of Bachelor of Technology degree of Computer Engineering of
Ganpat University, Kherva, Mehsana in the year 2023-2024.
 U.V. PATEL COLLEGE
OF
ENGINEERING

DD/MM/YY

CERTIFICATE

TO WHOM SO EVER IT MAY CONCERN

This is to certify that Ms. Vedanshee Patel student of B.Tech. Semester V

(Information Technology) has completed her full semester Capstone
Project work titled “PlayTracker” satisfactorily in partial fulfillment of the
requirement of Bachelor of Technology degree of Information Technology
of Ganpat University, Kherva, Mehsana in the year 2023-2024.

College Project Guide

Sign Dr. Devang Pandya,

Head, Information Technology
 Acknowledgement

I am deeply grateful to Prof. Manan Thakkar for his exceptional mentorship and unwavering support
throughout this project. His profound knowledge, dedication, and encouragement have been pivotal in
shaping its success. I consider myself fortunate to have had the opportunity to work under his guidance,
and I am truly inspired by his passion for teaching and research.I also want to express my sincere
appreciation for his patience and willingness to answer my questions, which has significantly contributed
to my learning and understanding of the subject matter. Prof. Thakkar's guidance has been instrumental in
making this project a rewarding and enriching experience.
 Abstract
Cricket is a popular sport that is followed by millions of people around the world. However, it can be
difficult to keep track of the scores of matches, especially if you are not able to watch them live. This is
where PlayTracker comes in. PlayTracker is a cricket scoreboard manager website that offers a user-
friendly and personalized experience. With mobile responsiveness, users can access live scores and
updates seamlessly on any device. The search functionality allows quick access to specific matches or
players. Push notifications keep users informed of crucial match events. Engaging polls and surveys
gather valuable insights from cricket enthusiasts. Weather updates help users plan for outdoor matches.
Player performance graphs provide in-depth analysis. Ball-by-ball commentary playback allows fans to
relive past moments. Meanwhile, official player rankings offer up-to-date performance standings. With
user accounts, fans can follow their favorite teams and access personalized content. Our website caters to
local cricket hosted matches, creating a sense of community and delivering an enriching cricket
experience.

We utilize HTML, CSS, and React.js for building an interactive and user-friendly frontend. Our
backend is powered by Node.js, ensuring efficient and reliable server-side operations. For the database,
we employ a NoSQL solution to handle large amounts of data, ensuring scalability and flexibility for our
cricket scoreboard manager website. The platform offers three distinct roles: Modulo Spectator, staying
updated on live matches with push notifications; Scorekeeper, ensuring accurate live score updates; and
Admin, overseeing the website's smooth functioning.
 Table of Content
ACKNOWLEDGEMENT…......................................................................................................................I
ABSTRACT…............................................................................................................................................II
CHAPTER–1–INTRODUCTION….........................................................................................................1
1.1 Project Overview…………………………………………………………………………….,…1
1.2 Project Background…..................................................................................................................1
1.3 Purpose.…………………………………………………………………………………………1
1.3.1 Problem…......................................................................................................................2
1.3.2 Aim…............................................................................................................................3
1.3.3 Objective........................................................................................................................3
1.4 Scope............................................................................................................................................3
1.5 Impect,Significance and Contribution…......................................................................................4
CHAPTER-2- LITERATURE REVIEW…...............................................................................................5
2.1 Cricket Score Display Project…..................................................................................................5
2.2 Cricket Score Card System…......................................................................................................5
2.3 Cricket Score Card Management System(c/c++).........................................................................5
2.4 Cricket Database Management System........................................................................................5
2.5 Automated Cricket Scoarecard Using Machine Lerning..............................................................6
2.6 Cricket Score Display and Commentary System.........................................................................6
2.7 Cricket Score Management System.............................................................................................6
2.8 Live Cricket Score Alert Using Python........................................................................................7
2.9 Cricket Scoarecard Using C# and MySql.....................................................................................7
2.10 Cricket Score Application..........................................................................................................8
Literature Survay Table.....................................................................................................................9
CHAPTER-3 SOFTWARE REQUIRMENT SPESIFICATION(SRS)................................................10
3.1 Functional Requirments.........................................................................................................................10
3.1.1 Module Admin…....................................................................................................................10
3.1.1.1 Sign Up For Admin…..............................................................................................10
3.1.1.2 sign In For Admin…................................................................................................10
3.1.1.3 Manage Users….......................................................................................................11
3.1.2 Module User…........................................................................................................................11
3.1.2.1 Sign Up For User......................................................................................................11
3.1.2.2 Sign In For User.......................................................................................................11
 3.1.2.3 Profile Update…......................................................................................................11
3.1.2.4 Host Match…...........................................................................................................11
3.1.2.5 View Matches….......................................................................................................11
3.1.3 Module Scorekeeper…............................................................................................................12
3.1.3.1 Host match…............................................................................................................12
3.1.3.2 Score Entry…..........................................................................................................12
3.1.3.3 Score Verification…................................................................................................12
3.1.3.4 Score History….......................................................................................................12
3.1.3.5 Notification…..........................................................................................................13
3.2 Non- Functional Requirments…............................................................................................................13
3.2.1 Reliability…............................................................................................................................13
3.2.2 Security…................................................................................................................................13
3.2.3 Efficiency…............................................................................................................................13
3.2.4 Usability…..............................................................................................................................13
3.3 Other Functionality…............................................................................................................................14
CHAPTER-4 DIAGRAMS........................................................................................................................17
4.1 Use Case Diagram......................................................................................................................17
4.2 Class Diagram…........................................................................................................................19
4.3 Sequence Diagram……………………………………………………………………………..21
4.4 Activity Diargram…………………………………………………………………………...…23
4.5 State Diagram………………………………………………………………………………….24
CHAPTER-5 PROTOTYPES...................................................................................................................25
5.1 Sign Up Page..............................................................................................................................25
5.2 Login Page..................................................................................................................................26
5.3 Home Page……………………………………………………………………………………..27
5.4 Today’s Schedule………………………………………………………………………………28
5.5 Home Page for Result................................................................................................................29
5.6 Upcomin Schedule……………………………………………………………………………..30
5.7 Match Scorecard…....................................................................................................................31
5.8 List of Teams………………………………………………….………………………………..32
5.9 Points Table………………………………………………….…………………………………33
5.10 Team Details-Scorekeeper……………………………………………………………………34
5.11 Score Update Page…………………………………………………………………………….35
CONCLUSION……………………………………………………………………………………………36
FUTURE WORK……………………………………………………………………………………….…37
REFERENCES WEBSITE……………………………………………………………………………….38
List of Diagrams:

Diagram-1 Use Case Diagram………………………………………………………………14

Diagram-2 Class Diagram…………………………………………………………………..15
Diagram-3 Sequence Diagram………………………………………………….………...…21
Diagram-4 Activity Diagram………………………………….…………………………….22
Diagram-5 State Diagram……………………………………...……………………………23
List Of Prototypes:
Prototype-1 Sign Up Page……………...…………………………………………………...24
Prototype-2 Login Page…………………………...………………………………………...25
Prototype-3 Home Page………………………………………....…………………………..26
Prototype-4 Today’s Schedule……………………………………………………………....27
Prototype-5 Home Page for Schedule……………………………………………………….28
Prototype-6 Upcoming Schedule………..…………………………………………………..29
Prototype-7 Match Scorecard……………………………………………………………….30
Prototype-8 List of Teams…………………………………………………………………..32
Prototype-9 Points Table……………………………………………………………………33
Prototype-10 Team Details-Scorekeeper…..……………………….………………………34
Prototype-11 Score Update Page…………..……………….……………………...……….35
 List Of Tables:

Table-1 Literature Survey Table..............................................................................................8

CHAPTER–1–INTRODUCTION

1.1 Project Overview

PlayTracker is a modern app and website for cricket fans, transforming how
scoreboards are handled. Whether it's a casual game or a big match, it's your handy cricket
companion, making real-time scorekeeping simple and adding fun to the game. From local
matches to the big leagues, PlayTracker takes over from old-fashioned methods, making
cricket scoreboard management a breeze.
With PlayTracker, no more fussing with scorebooks. Its easy interface and live updates
help players and fans alike. Cool features keep things accurate, giving you the match's quick
picture. Whether you're a player or a keen follower, PlayTracker makes cricket better, fitting
for friendly games or serious contests. Wave goodbye to pen-and-paper – PlayTracker doesn't
just simplify scoring, it makes it exciting.

1.2 Project Background:

The PlayTracker Cricket Scoreboard Management app/website was born from our love
for cricket and the need for a better way to keep track of scores. Traditional scorekeeping had
its problems, like mistakes and missing exciting moments. So, we came up with a simple and
user-friendly digital solution, PlayTracker. Our goal was to give players, teams, and fans
instant updates on runs, wickets, overs, and other important stats during matches. We wanted
to make cricket scoring easy and fun, capturing all the action accurately and sharing it
effortlessly. With PlayTracker, we're bringing the excitement of the game closer to everyone
and making sure no thrilling moment goes unnoticed. Whether you're at the stadium or
following from afar, PlayTracker ensures you're always in the loop and part of the cricketing
excitement.

1.3 Purpose:

PlayTracker, our groundbreaking Cricket Scoreboard Management app, is designed

with a clear mission: to make cricket more accessible and exciting for everyone. By
simplifying the process of tracking live scores, runs, wickets, and overs, PlayTracker
 eliminates the confusion that often surrounds scorekeeping. Players, teams, and fans, both
experienced and new, can now engage with the game effortlessly, fostering a sense of
togetherness within the cricket community.
With PlayTracker, every hit to the boundary and every wicket that falls is translated into a
shared experience. It's more than just an app; it's a bridge between the cricket field and the
stands, connecting players and spectators through real-time updates. Its intuitive interfac
makes scoring easy for players and provides instant insights for fans, ensuring that the excitement of
cricket is accurately captured and celebrated by all.

1.3.1 Problem

Inaccuracies and Human Errors:

The manual nature of traditional Cricket Scoreboard Management leads to inherent inaccuracies
and potential human errors. The process of recording runs, wickets, and overs on paper is prone to
miscounts and misinterpretations. The fast-paced nature of the game, coupled with the need for quick
updates, increases the likelihood of mistakes creeping into the recorded statistics. These errors can impact
the accuracy of player and team performance data, affecting the overall credibility of the match records.

Time Delays and Missed Moments:

Manual scorekeeping introduces time delays in updating scores, as scores must be recorded,
calculated, and transcribed before being made available to players and spectators. This delay can result in
significant moments, such as boundaries, wickets, or milestones, being missed or inaccurately
documented. The disconnect between the real-time action on the field and the manual scorekeeping
process hampers the immediate relaying of game-changing events, undermining the excitement and
authenticity of the match experience.

Complexity and Confusion:

Translating handwritten records and calculations into a clear and understandable format can be
complex. Communicating scores to players, teams, and spectators requires careful attention to detail, and
even minor errors in conveying the data can lead to confusion. This complexity can impede the enjoyment
of the game, as spectators struggle to understand the current state of the match. The process of converting
manual tallies into meaningful insights often leads to less engagement and less accurate understanding of
player and team performance.

Lack of Real-time Updates:

The traditional method inhibits the seamless sharing of real-time updates during the match. Scores
must be calculated, verified, and communicated manually, resulting in a delay between the actual on-field
events and the availability of accurate scores. This delay in sharing updates hampers the immediacy of the
cricket experience, preventing players and fans from fully immersing themselves in the excitement of the
game as it unfolds.

Inefficient Data Sharing:

The manual approach to scorekeeping complicates the sharing of match data across different
platforms. Converting handwritten scores into digital formats for online sharing can be time- consuming
and error-prone. As a result, the accessibility of match updates is hindered, limiting the reach of cricket to
a wider audience. The lack of efficient data sharing prevents the sport from fully leveraging modern
communication tools to engage fans and promote the game's global appeal.

The traditional Cricket Scoreboard Management method's reliance on manual processes poses these
challenges, impacting accuracy, real-time updates, and data sharing. The PlayTracker Cricket Scoreboard
Management project aims to address these issues by introducing a modernized approach that streamlines
scorekeeping, enhances accuracy, and provides real-time updates for an engaging and immersive cricket
experience.

1.3.2 Aim

The aim of the PlayTracker Cricket Scoreboard Management project is to make keeping track of
cricket scores super easy and accurate. We want to use modern technology to replace the old way of
writing scores on paper, which can be slow and sometimes wrong. Our aim is to create a simple and user-
friendly app that shows real-time updates of runs, wickets, overs, and other important game details. This
will make watching and playing cricket more exciting and clear for everyone involved.

1.3.3 Objective

The objective of the PlayTracker Cricket Scoreboard Management project is to develop a user-
friendly and efficient digital platform that enables seamless real-time tracking of cricket scores. By
eliminating the challenges posed by manual scorekeeping, the project seeks to enhance the accuracy,
speed, and accessibility of game statistics, providing players, teams, and spectators with instant updates
on runs, wickets, overs, and other crucial match information. This digital solution aims to elevate the
cricketing experience, making it more engaging and enjoyable for participants and fans alike.
1.4 Scope

The PlayTracker Cricket Scoreboard Management project is poised to reshape how cricket scores are
managed and enjoyed. This initiative involves creating a dynamic app/website that simplifies real-time
scorekeeping for various cricket matches, from casual to professional. What makes this project unique is
its emphasis on user customization, allowing individuals to tailor their score-viewing experience
according to their preferences. The user- friendly design and cross-device compatibility will ensure that
cricket enthusiasts can effortlessly engage with the game's live scores. Ultimately, this project seeks to
unite players and fans by making cricket scorekeeping accessible, interactive, and enjoyable for all.

1.5 Impact,Significance and Contribution:

Impact:
The PlayTracker Cricket Scoreboard Management project ushers in a transformative impact by
revolutionizing the way cricket scores are managed. This not only ensures accuracy in tracking scores,
runs, and wickets but also extends its benefits to players, teams, and fans. This heightened accuracy
further elevates the value of match statistics, fostering a culture of fairness and transparency within the
cricketing arena.

Significance:
At its core, the project's significance lies in the modernization of cricket engagement. By
introducing a streamlined approach to scorekeeping, players can immerse themselves fully in the game,
unhindered by administrative complexitiesThis innovative transformation strengthens the bonds within
the cricket community, propelling enthusiasts towards deeper involvement and a heightened sense of
shared experience.

Contribution:
The PlayTracker project contributes significantly by simplifying the intricate art of cricket
scorekeeping. By offering real-time access to comprehensive data, players are empowered to analyze their
performance and make informed improvements. This translates into better strategizing for teams,
facilitating enhanced performance on the field. For fans, the app/website becomes a portal of active
engagement, encouraging them to interact with the game as it unfolds. This inclusive approach amplifies
cricket's global appeal, democratizing access to the sport's essence and statistics, and nurturing a thriving
community of players and enthusiasts around the world.
CHAPTER-2 :- LITERATURE REVIEW:

2.1 Cricket Score Display Project:

The Cricket Score Display Project is a simple C programming application built for efficiently
managing and displaying cricket match statistics[1]. It employs functions for data storage, file handling,
and user input validation[1]. The main menu provides options to create a new score sheet, view previous
ones, or exit the program. Users can input competition details, player statistics, and more, with the
flexibility to edit the data as needed[1]. This project ensures organized and well-formatted data storage
and retrieval, serving as a useful reference for file handling in C and offering opportunities for users to
customize and expand it to meet their programming requirements, thereby enhancing their coding
skills[1].

2.2 Cricket Score Card System:

The "Cricket Score Card System" project is developed using PHP as the primary programming
language, MySQL as the database management system, and likely incorporates common front-end
technologies like HTML, CSS, and JavaScript for user interfaces[2]. It employs web server software (e.g.,
Apache or Nginx) for hosting, user authentication mechanisms for registration and login, and possibly
real-time updates through technologies like WebSockets or server-sent events[2]. The system likely
focuses on data security measures, including encryption and input validation, and may generate reports
using PHP libraries[2]. Responsive design principles ensure accessibility across different devices, and the
development process likely includes testing and quality assurance practices to ensure reliability and
functionality[2].

2.3 Cricket Score Card Management System (C/C++):

The "Cricket Score Card Management System" project is a web application developed using C/C++
as the programming platform, HTML for user interface design, and MySQL for database management[3].
This system efficiently manages and displays cricket match data, including runs, wickets, overs, and
player statistics[3]. It not only reduces manual data entry and human errors but also provides a user-
friendly platform for cricket score management, making it a valuable tool for cricket enthusiasts and
scorekeepers[3].
2.4 Cricket Database Management System:

To create a cricket database management system, you would employ a technology stack comprising
PHP or a similar server-side scripting language, along with an RDBMS like MySQL for data storage[4].
HTML, CSS, and JavaScript would be used to develop user- friendly web interfaces for displaying team
and match details, as well as managing user accounts[4]. User authentication and captain assignments
could be handled through PHP authentication libraries[4]. Implementing security measures and testing
frameworks would ensure data protection and system reliability[4]. This technology stack would facilitate
the management of teams, matches, umpires, and team captains efficiently and securely[4].

2.5 Automated Cricket Scorecard System Using Computer Vision and Machine
Learning:

The "Automated Cricket Scorecard System" project, developed by Md. Asif Shahjalal, Zubaer
Ahmad, Rushrukh Rayan, and Lamia Alam from the Chittagong University of Engineering and
Technology, utilizes computer vision and machine learning technologies to automate the process of
updating the cricket scorecard[5]. This innovative system leverages a static camera to capture gestures
made by cricket umpires, allowing for real-time interpretation and scorecard updates[5]. By recognizing
specific hand gestures using Haar- cascade-classifier and logistic regression techniques, this system
eliminates the need for manual scorecard updates, reducing the duration of the game and enhancing the
accuracy of the scoring process[5]. This project addresses a critical need in the game of cricket, making it
more efficient and accurate, particularly in regions like Bangladesh where cricket is immensely
popular[5].

2.6 Cricket Score Display and Commentary System:

This project aims to create a cricket score display system that provides real-time updates of cricket
matches, along with commentary[6]. Cricket is a beloved sport for many, and this system will cater to
enthusiasts who want to stay updated on matches, even when they can't watch them live[6]. It will stream
video feeds of cricket matches and provide official text commentary, allowing users to follow the game's
progress easily[6]. Whether someone is stuck at the office or busy with other tasks, they can check the
commentary regularly to get updates on the match, including scores and team line-ups posted during the
game[6].

2.7 Cricket Score Management System:

The Cricket Score Management System project, developed in the C programming language, is a
console-based application utilizing file handling to store cricket match data, including runs, wickets,
overs, and extras[7]. This system provides information such as runs, wickets, batsman and bowler names,
overs, extras, bowler economy, and batsman strike rate, along with the game's start and end times[7]. It
features a user-friendly interface with options to create a new scoresheet, open an existing one, or exit the
program[7]. The code is designed to run in the Code::Blocks IDE and allows users to input match details,
bowler information, overs, and other match-related data[7]. This project serves as a valuable resource for
programming beginners looking to gain practical experience in C, and it primarily employs the C
programming language within the Code::Blocks IDE, making use of file handling for data storage and
retrieval[7].

2.8 Live Cricket Score Alerts using Python:

The Live Cricket Score Alerts project, implemented in Python, aims to display real-time cricket
score updates[8]. It fetches live cricket data from online sources and presents it in a user-friendly
interface, showing essential match details such as team names, live scores, locations, and match times[8].
To develop this project, a basic understanding of libraries like tkinter, requests, BeautifulSoup (bs4), and
Pillow (PIL) is required[8]. This project's technology stack includes Python, tkinter for the graphical user
interface, requests for handling HTTP requests, BeautifulSoup (bs4) for parsing HTML, and Pillow (PIL)
for image processing[8].

2.9 Cricket Score Card using C# and MySQL:

The Cricket Score Card project, developed with a technical stack comprising C# and MySQL, offers
a sophisticated and data-driven solution for cricket score management[9]. Leveraging C#'s object-oriented
capabilities and MySQL's relational database management system, this system efficiently stores and
retrieves match scores, player statistics, and team data[9]. The integration of C# ensures a user-friendly
interface and robust application logic, while MySQL provides a secure and scalable backend for storing
cricket-related information[9]. This technical stack is ideal for building cricket score management systems
with advanced data handling and real-time updates[9].

2.10 Cricket Score Application:

The Cricket Live Score & Match Management System is a web application designed to provide
real-time cricket match scores and match-related information to users, particularly those without access to
television or cable services[10]. The system employs a modern technology stack, including React.js and
Node.js with Express.js for the front-end and back- end development, MongoDB for data storage,
WebSocket for real-time updates, Passport.js for authentication, and Amazon Web Services (AWS) for
hosting[10]. Users can log in to view live cricket scores and an upcoming match timetable, while an
admin account is responsible for updating scores[10]. This application aims to enhance cricket enthusiasts'
accessibility to live scores and match schedules, ensuring a seamless online cricket-watching
experience[10].
Literature Survey Table:

Project Title Description Technology Stack

Cricket Score Display Project[1] C programming application for C Programming
efficient cricket match statistics
management. Allows creating, viewing
score sheets, and data editing.
Cricket Score Card System[2] PHP-based web system with MySQL PHP, MySQL, HTML, CSS,
for cricket score management. Features JavaScript
user authentication, real-time updates,
and data security.
Cricket Score Card Management Web app in C/C++ for cricket data C/C++, HTML
System (C/C++)[3] management, reducing manual errors.
Enhances user-friendliness for cricket
scorekeepers.
Cricket Database Management PHP-based cricket database PHP, MySQL, HTML, CSS,
System[4] system for team and match details. JavaScript
Includes user authentication and data
protection measures.
Automated Cricket Scorecard Innovative system using computer Computer Vision, Machine
System[5] vision and machine learning to Learning (Haar-cascade-
automate cricket scorecard updates, classifier,
improving accuracy and speed.
Logistic Regression)
Cricket Score Display Real-time cricket score display and Not specified
and Commentary commentary system for enthusiasts.
System[6] Streams video feeds and provides text
commentary.
Cricket Score Console-based C application for cricket C Programming
Management score storage and retrieval. Features
System[7] user-friendly interface and data entry
options.
Live Cricket Score Alerts using Python project for displaying real-time Python,tkinter,requests,
Python[8] cricket score updates with GUI. BeautifulSoup (bs4), Pillow
Fetches data from online sources and (PIL)
provides match details.
Cricket Score Card using C# and C# and MySQL-based system for C#, MySQL
MySQL[9] cricket score management. Ensures a
user-friendly interface and robust data
handling.
Cricket Score Application[10] Web application using React.js and React.js,Node.js, Express.js,
Node.js with MongoDB for cricket MongoDB,WebSocket,
 score and match information. Ensures Passport.js, AWS Hosting
real-time updates and user
authentication.

[Table 1 : Literature Survey Table]

CHAPTER-3 SOFTWARE REQUIRMENT SPECIFICATION:
3.1 Functional requirements

3.1.1 Module Admin

3.1.1.1 SignUp for Admin:

- Input: The admin shall provide their username, name, email, and password during signup.
- Process: Validate the provided credentials for uniqueness and correctness. Create an admin
account if the credentials are valid.
- Output: The system shall allow an admin to sign up using valid credentials.

3.1.1.2 SignIn for Admin:

- Input: The admin shall enter their registered email and password to log in.

- Process: Authenticate the provided email and password against the stored admin credentials
in the database.
- Output: The system shall provide a login interface for admins to sign in.

3.1.1.3 Manage Users:

- Input: The admin shall be able to view, add, edit, and delete user profiles. User profiles
shall include details such as name, roll number, and contact information.
- Process:
For "View": Retrieve user profiles and team information from the database and display
it to the admin.
For "Add": Validate and insert new user profiles and team details into the database.
For "Edit": Validate and update existing user profiles and team details in the database.
For "Delete": Confirm admin's intent to delete user profiles and associated team data
 before removing them from the database.
Send notifications to users about upcoming matches, score updates, or any critical events
using email or SMS.-
Output: The admin shall be able to manage user profiles and teams effectively.
3.1.2 Module User:

3.1.2.1 SignUp for User:

- Input: Users shall provide their username, name, email, and password during registration.
- Process:Validate the provided credentials for uniqueness and correctness. Create a user account
if the credentials are valid.
- Output:The system shall allow users to create an account using valid information.

3.1.2.2 SignIn for User:

- Input: Users shall enter their registered email/username and password to log in.

- Process: Authenticate the provided email/username and password against the stored user
credentials in the database.
- Output: The system shall provide a login page for users to access their accounts.

3.1.2.3 Profile Update:

- Input: Users shall have the capability to update their profiles, including names and passwords.
- Process: Validate and update user profiles and passwords in the database based on user input.
- Output: User profiles shall be updatable.

3.1.2.4 Host Match:

- Input: Users shall have the capability to update their profiles, including names and passwords.
- Process: Validate and store match details in the database, create a new match entry.

- Output: Users shall have the ability to host a cricket match.

3.1.2.5 View Matches:

- Input: Users shall view upcoming and ongoing matches hosted by other users, including match
details such as date, time, location, participating teams, and scores.
- Process: Retrieve match information from the database and display it to users.

- Output: Users shall be able to view match information effectively.

3.1.3 Module Scorekeeper:

3.1.3.1 Host Match:

- Input: Scorekeepers shall have the capability to create and host matches, providing match details
such as date, time, location, participating teams, and match format.
-Process: Validate and store match details in the database, creating a new match entry specifically
for scorekeeping purposes.
-Output: Scorekeepers shall have the ability to host cricket matches and serve as scorekeepers
during the matches they create.

3.1.3.2 Score Entry:

-Input: During a match, scorekeepers shall input and update the scores, wickets, and other relevant
statistics for each team.
-Process: Validate and record score data in real-time during the match, updating the match's
scorecard.
-Output: The system shall display real-time scores and statistics for ongoing matches, making them
accessible to all users.
3.1.3.3 Score Verification:

-Input: After the match, scorekeepers shall review and verify the accuracy of the recorded scores and
statistics.
-Process: Allow scorekeepers to cross-check and validate the match scores and statistics
before finalizing and saving them.

-Output: The system shall ensure the accuracy and reliability of match scores and statistics.

3.1.3.4 Score History:

-Input: Users shall have access to the historical scores and statistics of matches hosted by
Scorekeepers.
-Process: Retrieve and display past match scores, statistics, and summaries from the database.
-Output: Users shall be able to view the history of scores and statistics for matches hosted by
scorekeepers.
 3.1.3.5 Notifications:

-Input: Scorekeepers and participants shall receive notifications regarding match updates, including
score changes, milestones, and match outcomes.
-Process: Implement a notification system that sends updates to relevant users based on match events.
-Output: Users shall receive timely notifications to stay informed about ongoing and completed
matches.

3.2 Non-functional Requirements:

3.2.1 Reliability:

The system's reliability, as per requirement, mandates that it should be available 24/7 with a 99%
uptime, and data integrity should be maintained through regular backups. This means that users can expect
high availability of the system and trust that their data will be secure and consistent.

3.2.2 Security:

In terms of security, as outlined in requirement, the system will ensure that access to administrative
functions is restricted through robust authentication mechanisms. Additionally, it will only allow
authorized personnel to access user data. This emphasizes the importance of safeguarding user
information and maintaining the confidentiality and integrity of sensitive data.

3.2.3 Efficiency:
Efficiency, as described in requirement 3.2.3, will be achieved through optimized database queries to
ensure that data retrieval is as efficient as possible. This means that the system will perform tasks swiftly
and minimize any delays in retrieving information, enhancing the overall user experience.

3.2.4 Usability:

For usability, requirement 3.2.4 necessitates a more interactive and user-friendly user interface. This
ensures that users find the system easy to navigate and interact with, ultimately enhancing their overall
experience. In summary, the system is expected to provide high availability, data security, efficient
performance, and user-friendly interfaces to meet these specified reliability, security, efficiency, and
usability requirements.
3.3 Other Functionality:

Live Score Updates:

-Input: Real-time match data.

-Process: The system updates scores and statistics.
-Output: Users can view live match scores and statistics.

Search Matches/Players:

-Input: User enters match/player name or keywords.

-Process: The system searches the database.
-Output: Users find specific matches or player profiles.

Push Notifications:

Input: Match events and user preferences.

Process: The system sends notifications to users.
Output: Users receive real-time updates on match events.

Polls and Surveys:

Input: User participation in polls/surveys.

Process: The system collects user responses.
Output: Insights and feedback from cricket enthusiasts.

Weather Updates:

Input: Location and match date/time.

Process: The system fetches weather data.
Output: Users receive weather forecasts for outdoor matches.

Player Performance Graphs:

Input: Player statistics and match data.

 Process: The system generates performance graphs.
Output: Users can analyze player performance visually.

Ball-by-Ball Commentary Playback:

Input: Historical match data and user request.

Process: The system retrieves commentary data.
Output: Users can replay past match moments.

Official Player Rankings:

Input: Player statistics and rankings data.

Process: The system updates rankings regularly.
Output: Users access up-to-date player standings.

Follow Favourite Teams:

Input: User selects favorite teams.

Process: The system tracks team performance.
Output: Users receive updates on their favorite teams.

Role-Based Access (Modulo Spectator, Scorekeeper, Admin):

Input: User role selection.

Process: The system grants role-specific privileges.
Output: Users have role-based access to website features.

Mobile Responsiveness:

Input: Access from various devices.

Process: The website adapts to different screen sizes.
Output: Seamless user experience on mobile devices.

Data Storage (NoSQL Database):

Input: User and match data.

 Process: Data is stored, retrieved, and updated.
Output: Efficient data management for scalability.

Data Scalability:

Input: Increasing data volume.

Process: The system handles large data sets.

Output: Ensures performance as the user base grows.

Efficient Backend (Node.js):

Input: User requests and data retrieval.

Process: Backend processes data and serves requests.
Output: Reliable server-side operations for seamless user experience
CHAPTER-4 DIAGRAMS

4.1 Use Case Diagram:

[Diagram 1: Use case diagram for cricket scoreboard manager]

The Diagram shows a cricket scoreboard manager application. The application is used to track the score
of a cricket match, as well as the individual performances of the players. The application has a number of
features, including:

⮚ A live scorecard that shows the current score of the match, as well as the individual scores of the
 players.

⮚ A player performance tracker that shows the individual runs scored, wickets taken, and overs bowled

by each player.

⮚ A weather tracker that shows the current weather conditions at the match location.

⮚ A ball-by-ball commentary that provides commentary on the match as it unfolds.

⮚ A match statistics tracker that shows the match statistics, such as the highest scorer, the best bowler,

and the winning team.

⮚ The application is used by cricket fans, coaches, and players to track the score of matches, as well as

to analyze the performances of players. The application is also used by broadcasters to provide live
commentary and statistics of matches.
4.2 Class Diagram:

[Diagram 2: Class diagram]

⮚ User Account: Represents registered users with attributes like username, password, email, and

preferences. They can receive notifications and follow teams.

⮚ Match: Describes cricket matches with details such as matchID, teams, date, location, and

weather. Each match has a scoreboard.

⮚ Player: Represents cricket players with attributes like playerID, playerName, and team

affiliation. They have associated stats.

⮚ Team: Represents cricket teams with teamID, teamName, and a list of players. Users can

follow and access team information.

⮚ Scoreboard: Belongs to a match and holds scores, commentary, and player stats. Keeps users

updated on the progress of a match.

⮚ Notification: Messages sent to User Accounts, with content and recipients. Users can
 customize their notification preferences.

⮚ Player Stats: Contains statistics for individual players, including matches played, runs scored,

and wickets taken.

⮚ Performance: Records player performance in specific matches, linked to playerID and matchID.

⮚ User Account-Notification Relationship: Users can receive notifications, and each notification

is associated with a User Account.

⮚ Team-Player Relationship: Teams have players, and players belong to specific teams,

facilitating team and player management within the system.

⮚ This class diagram outlines the essential components and relationships of the PlayTracker

cricket scoreboard manager website, enabling users to follow matches, teams, and players
while receiving updates and notifications.
4.3 Sequence Diagram:
 [Diagram 3 : Sequence diagram]
The sequence diagram explains how a notification service works, especially when it comes to signing up for
notifications and getting those notifications. It all begins when a user decides they want to get notifications
through an app. They tell the app, which then asks the notification service to make it happen. Once the
notification service says, "Okay, you're subscribed," it records that the user wants notifications. Later on,
when the user's app checks if there are any new notifications, the notification service looks in its database. If
it finds any notifications waiting for the user, it sends them to the app. The app shows these notifications to
the user. This diagram simplifies how the notification service functions, but in real life, these services can do
more complicated things, like scheduling notifications and sending them to multiple devices.

4.4 Activity Diagram:

 [Diagram 4: Activity diagram]

⮚ The cricket score recording process flow diagram shows the steps involved in recording the score of a

cricket match. The process begins with the user initiating the score recording process. The user then
enters the runs scored, the number of wickets taken, and the over number. The program then validates
the input to ensure that it is valid. If the input is valid, the program updates the scorecard and displays
the updated score. If the input is not valid, the program displays an error message and prompts the
user to re-enter the input.

4.5 State Diagram:

 [Diagram 5 : State diagram]

The Cricket Scoreboard Management System, as depicted in the state diagram, offers cricket
enthusiasts a versatile tool for following live match scores and effectively overseeing cricket games. Users
commence by selecting a match from the "Main Menu," where the system then provides real-time updates on
the batting team, bowler, and runs scored. Users have the liberty to pause and resume the match, with the
option to "End Match" or "Quit Without Saving" when paused, with a confirmation step for the latter. Upon
confirmation, the system saves the match and exits. Additionally, users can create new matches or load
previously saved ones, simplifying the process of monitoring and managing cricket games. This system is a
valuable asset for cricket aficionados, commentators, and match organizers, streamlining the management of
cricket events.
CHAPTER-5: PROTOTYPES:

5.1 Sign Up Page:

[Prototype 1: PlayTracker Sign-Up Form]

The PlayTracker sign-up form, titled "Sign up to PlayTracker," presents a user- friendly interface
against a light blue background. It comprises essential elements, including input fields for the user's first
name, email address, and password, all with a white border and a light gray background. To create an
account, users must also check the "I agree to the Terms of Service and Privacy Policy" checkbox, and
they can initiate the account creation process with the "CREATE AN ACCOUNT" green button. For
those who already have an account or prefer to log in, there's an "OR" link leading to the PlayTracker
login page, with clear and legible black text throughout the form.
5.2 LogIn Page:

[Prototype 2: PlayTracker Login Page]

The PlayTracker login page, titled "SIGN IN," features user-friendly elements such as input fields
for email address and password (with password security), a "Remember Me" checkbox for convenience,
and a "Forgot Password?" link for password recovery. Users initiate the login process with a prominent
"PROCEED" button. Additionally, an "OR" link directs users to the PlayTracker home page,
accommodating those who do not wish to log in immediately or are new to the platform.
5.3 Home Page

[Prototype 3: Homepage]

The homepage welcomes users with a curated selection of the most exciting and highly-anticipated
matches. These top matches are showcased prominently, featuring essential information like teams, match
timings, and venues. This engaging presentation ensures that users can quickly discover and access the
most compelling cricket events right from the moment they land on the site.
5.4 Today’s Schedule

[Prototype 4:Today's Matches]

The "Today's Matches" page offers a convenient and dynamic overview of all the matches
scheduled for the current day. Users can quickly access details such as match timings, participating
teams, venues, and more. This real-time information ensures that users never miss a moment of the day's
cricket action, keeping them engaged and informed.
5.5 Home Page for Result

[Prototype 5: Match Results]

The "Match Results" page provides a comprehensive compilation of recent cricket match
outcomes. Users can easily access details such as final scores, winning teams, top performers, and
match summaries. This page serves as a go-to resource for fans to catch up on the latest results and
relive the excitement of past matches.
5.6 Upcoming Schedule

[Prototype 6: Upcoming Matches Schedule]

The Schedule page provides a neatly organized display of upcoming matches. Users can easily
access information about match dates, times, teams, and venues. This user-friendly interface ensures fans
stay informed about the exciting events on the horizon.
5.7 Match Scoreboard

[Prototype 7:Scoreboard]

The Scoreboard presents a comprehensive view of the match in a table format. It prominently
displays the team names at the top, followed by vital match statistics, including scores, overs, strike rates,
and individual batting and bowling data. The bottom of the table unequivocally declares the game's
winner, offering a concise yet detailed summary of the match's outcome.
5.8 List of Teams

[Prototype 8:List of Teams]

This page proudly displays the impressive lineup of teams that partook in the intense Specific
Tournament. Each of these teams, comprised of both seasoned contenders and emerging talents, showcased
their remarkable skills and unwavering sportsmanship throughout the competition. Whether it was their
breathtaking matches or exceptional teamwork, these teams etched unforgettable moments in the
tournament's history. Together, they formed a diverse and dedicated cohort, contributing to the Specific
Tournament's legacy, making it an unforgettable spectacle of sporting excellence.

5.9 Points Table

 [Prototype 9:Points Table]

The Points Table webpage provides a concise and up-to-date summary of the ongoing competition.
Here, you can easily track the performance of all participating teams, with details on their wins, losses,
draws, points earned, and net run rates. It's your go-to destination for a quick overview of how each team is
faring in the tournament. Whether you're a passionate fan or just looking for the latest standings, this
webpage offers a clear and organized presentation of the tournament's progress.

5.10 Team Details-Admins

 [Prototype 10:Team Details]

The Team Details webpage is designed to gather and display essential information about each team in
the competition. It allows users to input and view details such as the team name, player names, and player
roles, specifically whether a player is a Batsman, Bowler, or an All-Rounder. This user-friendly interface
simplifies the process of managing team data and provides quick access to player profiles, helping enthusiasts
and team managers stay updated on the roster for an enhanced viewing experience.

5.11 Score-update Page

 [Prototype 11:Score-update Page]

The Score Update Page serves as a vital tool for administrators to keep live scores up-to-date during
matches or events. This webpage provides a secure and efficient platform for authorized administrators to
input and instantly publish score updates, ensuring that spectators, fans, and participants can access real-
time information about ongoing games. The intuitive interface of the Score Update Page streamlines the
process of score entry, making it easy for administrators to manage and report scores swiftly and accurately,
enhancing the overall experience for everyone involved in the event.

Conclusion:
The PlayTracker Cricket Scoreboard Management project represents a significant leap forward in the
world of cricket by modernizing and simplifying the way scores are recorded and shared. It addresses the
longstanding challenges of inaccuracy, time delays, complexity, and limited real-time updates associated
with traditional manual scorekeeping methods. By creating a user-friendly and customizable digital
platform, PlayTracker not only enhances the accuracy and accessibility of cricket statistics but also brings
players and fans closer together through shared real-time experiences. This project's impact, significance,
and contribution extend beyond the boundaries of the cricket field, fostering a sense of togetherness,
transparency, and enthusiasm within the cricketing community while promoting the global appeal of the
sport. PlayTracker is not just a tool; it's a game-changer, redefining how we engage with and celebrate the
thrilling world of cricket.
 Future Work:

The future work for PlayTracker includes improving the prototype and diagrams, as well as adding new
features and functionality. We plan to make the prototype more user-friendly and intuitive, and to add
more detailed diagrams that illustrate the system architecture. We also plan to add new features such as
the ability to create custom tournaments, track player statistics, and generate reports. We believe that
these improvements will make PlayTracker an even more valuable tool for cricket fans and organizers.
References:

[1] Cricket Score Display Project Using C Language, Adarsh Kumar Singh(2023)
Site:Studytonight,visitedon:August/10/2023,url:https://www.studytonight.com/
c-projects/cricket-score-display-project-using-c-language

[2] Cricket Score Card System, K.KALAISELVAN, Dr.V.KAVITHA, Dr.N.REVATHY ,

(2019), Site:academia, visited on: August/12/2023, url: https://www.academia.edu/4045
6062/CRICKET_SCORE_CARD _SYSTEM_

[3] Cricket score card management system project on C/C++, Harsha

Vardhini(2022),Site: kashipara, visited on: August 15
2023,url:https://www.kashipara.com/project/ idea/c- c-/
cricket-score-card- management-system_3281.html

[4] Cricket Database Management System, K. VENKATAMAHESH(2021),Site:

studocu,visited on: August/20/2023,url:https://www.studocu.com/in/document/lovely-
professional-university/dbms/cricket-database-management-system-ca- project/41272005

[5] An Approach to Automate the Scorecard in Cricketwith Computer Vision and Machine
Learning, Md. Asif Shahjalal, Zubaer Ahmad, Rushrukh Rayan, Lamia Alam(2017)Site:
researchgate,visitedon:August/22/2023,url:https://www.researchgate.net/publication/
322997072_An_approach_To_a_automate_the_scorecard_in_cricket_with_computer_vision_and
_machine_learning

[6] Cricket Score Display, Jameervali Dudekula,Lakshman Atmakuri,Dinesh Kottakota

(2021),Site: coursehero visited on: August/28/2023,url:https://www.coursehero. com
/file/147057510/project
[7] Cricket Score Management System in C with Source Code, adonesevangelista (2022), Site:
itsourcecode,visited on: August/29/ 2023,url: https://itsourcecode.com/free-projects/c-projects
/cricket-score-management-system-in-c-with-source- code/? expand _article=1

[8] Live Cricket Score Alerts using Python,Site: data-flair.trainingvisited on: August/31/23
url:https://data-flair.training/blogs/python-live-cricket-score-alerts/

[9] Cricket Score Card using C# and MySQL,Site: sourcecodester,visitedon:August/1/23

url:https://www.sourcecodester.com/downloadcode?nid=4642&title=Cricket+Score+Card

[10] Cricket Live Score & Match Management System Code Shoppy.,Site: codeshoppy ,visited
on: September/5/2023, url:https://codeshoppy.com/shop/product/cricket- association-mobile-
application/