1.

Introduction
The Video Analysis Tool is a comprehensive software system designed to extract highlights from cricket
match footage, making it easier for sports enthusiasts and analysts to access key moments in the game.
This document outlines the detailed requirements for the development and functionality of the Video
Analysis Tool. The system is designed to offer an efficient and user-friendly solution for extracting
highlights and scoring details from cricket match videos. It provides users with a set of tools for
analyzing cricket matches, extract text-based scores, and generate concise highlights.

This chapter serves as a blueprint for the Video Analysis Tool, covering various aspects, such as existing
system limitations, proposed system features, functional and non-functional requirements, system flow,
and use cases. The detailed specifications within this document will guide the development team in
creating a powerful and reliable software system that meets the needs of cricket enthusiasts and
analysts.

The Video Analysis Tool is expected to revolutionize the way cricket match analysis is conducted, making
it more accessible and efficient for users of all levels, from casual fans to professional analysts. The
system's core functionalities include text recognition, and highlight extraction. The proposed system
aims to enhance the cricket analysis experience by providing a comprehensive set of features that
address the limitations of existing systems.

As we delve into the detailed requirement specifications, we will explore:

1. System Overview: An overview of the purpose and functionality of the system.

2. Functional Requirements: Detailed descriptions of the system's functional features.
3. Non-functional Requirements: Specifications for performance, usability, and quality.
4. Use Cases: Scenarios depicting user interactions with the system.
5. Flow Diagram: Visualization of the system's data flow.
6. User Interface Design: A brief description of the user interface.

2. System Overview

The Video Analysis Tool is designed to be a cutting-edge software system that caters specifically to the
field of cricket match analysis. The system's primary purpose is to offer users a set of comprehensive
tools and features for extracting highlights, and obtaining detailed text-based scores from cricket match
videos. It is crucial to understand the core components and functionalities that constitute the Video
Analysis Tool:
 1. Text Recognition: The Video Analysis Tool includes a text recognition module capable of
extracting text-based scores and commentary from the match footage. This provides users with
detailed information about the match progress and significant events.

2. Highlight Extraction: The system excels in the extraction of highlights from cricket matches.
Users can specify their preferences for highlight criteria, such as wickets, boundaries, or
significant overs. The system then autonomously generates concise and engaging highlight clips.

3. User-Friendly Interface: The Video Analysis Tool offers an intuitive and user-friendly interface
that allows users to interact with the software effortlessly. It is designed to be accessible to
users with varying levels of technical expertise.

4. Efficient Performance: The system is optimized for optimal performance on compatible

hardware, ensuring smooth operations and a seamless user experience. It minimizes lags and
interruptions to maintain user immersion.

5. Customization: Users have the flexibility to customize highlight criteria and preferences,
tailoring the system to their specific needs which will be based on interest or variety. This
feature enhances the user's ability to focus on areas of interest.

The system will undergo continuous development and improvement to meet the evolving needs of
cricket analysts and enthusiasts. It aims to be a versatile tool, suitable for various user levels, from
beginners looking to explore the intricacies of cricket analysis to professionals requiring in-depth insights
into match performances.

The Video Analysis Tool provides a new paradigm for cricket match analysis by combining advanced
technologies, user-friendly interfaces, and customizable features. It promises to make cricket analysis
more engaging and accessible for users, revolutionizing the way cricket enthusiasts and analysts
approach match footage analysis.
3. Functional Requirements

The functional requirements of the Highlight Generator Tool encompass the core capabilities and
features that the system offers to users. These functionalities ensure that the system fulfills its primary
purpose of assisting cricket enthusiasts and analysts in in-depth match analysis. Additionally, it's worth
noting that the system is in the process of potentially incorporating umpire gesture recognition for
highlight creation, although this feature is still under development and not guaranteed for the initial
release.

Text Recognition:

 The system must be capable of extracting text from the scorecard.

Highlight Extraction:

 Users must be able to specify highlight criteria, such as wickets, boundaries, or Important
Events.
 The system should autonomously generate highlight clips based on the specified criteria.

User-Friendly Interface:

 The system should provide an intuitive and user-friendly interface that facilitates easy
navigation.
 Users, regardless of their technical background, should find the system's interface accessible
and easy to use.

Efficient Performance:

 The system must optimize performance to minimize lags, ensuring a seamless user experience.

Customization:

 Users should have the flexibility to customize highlight criteria and preferences based on their
analysis needs.
 Customization features should enable users to focus on specific areas of interest as well as
variety within the match footage.
Umpire Gesture Recognition (Potential Feature):

 The system may incorporate umpire gesture recognition for the creation of highlights.
 The implementation of this feature is under development and will be considered for future
releases.

These functional requirements define the core capabilities of the Video Analysis Tool, ensuring that it
meets the needs of cricket analysts, enthusiasts, and researchers. While the system is already a robust
platform for match analysis, ongoing development may lead to further enhancements, such as the
potential inclusion of umpire gesture recognition.

4. Non-Functional Requirements

In addition to the functional aspects of the Video Analysis Tool, non-functional requirements outline the
quality attributes and performance expectations of the system. These non-functional requirements
ensure that the system not only delivers valuable features but also meets the highest standards of
performance, usability, and reliability.

Optimal Performance:

 The system must provide optimal performance on hardware that meets its specifications, with
minimal lags or disruptions during use.
 Users should experience smooth and responsive interactions with the application, even when
handling extensive match footage.

User-Friendly Interface:

 The application's user interface must be intuitive and user-friendly, allowing users to navigate,
customize, and access features naturally.
 Users, regardless of their familiarity with cricket analysis tools, should find the interface easy to
use.

Quality Assurance:
  The system must provide a high-quality user experience, ensuring that users can rely on the
accuracy and precision of its analysis.
 All analysis results, including frame extraction and text recognition, must be of a high standard,
meeting the expectations of cricket analysts.

Scalability:

 The system should be designed with scalability in mind, allowing it to accommodate a growing
user base and increasing volumes of match data.

Compatibility:

 The Video Analysis Tool must be compatible with common operating systems and browsers,
providing users with flexibility in their choice of platforms.

Potential Umpire Gesture Recognition (Future Consideration):

 If umpire gesture recognition is implemented, it should meet high accuracy standards in

recognizing and translating gestures.
 The potential feature must not compromise the system's overall performance or
responsiveness.

These non-functional requirements collectively emphasize the importance of providing an exceptional

user experience while ensuring that the Cricket Highlight Generator Tool operates efficiently, securely,
and reliably. These attributes are fundamental to the system's success in the cricket analysis domain.
5. Flow Diagram

The flow diagram represents the flow of actions and the interplay between different objects and items
which comprise the whole system

Figure 1: Flow Diagram

Use Case 1: Start Application

Use Case ID UC-01

Use Case Name Start Application

Actors User (Cricket Enthusiast)

Data Application

Trigger User opens the web application

 Use Case ID UC-01

Pre-condition The web application is accessible

Assumptions The user has a compatible web browser

Normal Flow of Events

1. The user initiates the application by opening the web application in their web
browser. This action launches the main application interface, allowing the user to
Description interact with the system.

Main Success
Scenario The user accesses the web application.

Post-Condition The main application interface is displayed in the user's web browser.

This is the initial step in using the system, and it sets the stage for subsequent
Comments interactions and tasks.

Use Case 2: Select a Cricket Video

Use Case ID UC-02

Use Case Name Select a Cricket Video

Actors User (Cricket Enthusiast)

Data Application, Cricket Video

 Use Case ID UC-02

Trigger User clicks on the "Select Video" button

Pre-condition The web application is accessible

Assumptions The user has a compatible web browser; Cricket video files are available for selection

Normal Flow of Events

1. The user clicks on the "Select Video" button within the application. This action opens
a file dialog for the user to select a cricket video from their computer's directory.

Description 2. The user selects a cricket video.

Alternate Flow of Events

1. If the user cancels the file dialog, no video is selected.

Exceptional Flow of Events

1. If the selected file is not a valid cricket video, the application may display an error
message and prompt the user to select a valid video.

Main Success
Scenario The user successfully selects a cricket video.

Post-Condition The selected cricket video is ready for further processing within the application.

Comments This use case is essential for providing input data for generating highlights from the
 Use Case ID UC-02

chosen cricket video.

Use Case 3: Generate Highlights

Use Case ID UC-03

Use Case Name Generate Highlights

Actors User (Cricket Enthusiast)

Data Application, Selected Cricket Video, Extracted Frames

Trigger User clicks on the "Generate Highlights" button

Pre-condition A cricket video is successfully selected

Assumptions The user has selected a cricket video

Description Normal Flow of Events

1. The user clicks on the "Generate Highlights" button within the application after
selecting a cricket video.

2. A new interface displays options for selecting the "Frames Per Second (FPS)" for
frame extraction. The user can choose from options such as 5 FPS, 10 FPS, 15 FPS, 20
FPS, 25 FPS, and 30 FPS.

3. The user selects a desired FPS for frame extraction.

 Use Case ID UC-03

4. The application begins the process of extracting frames from the selected cricket
video at the specified FPS.

5. The frames are saved in a directory named "Frames" within the user's computer.

Main Success The user successfully selects the FPS and initiates the process to generate highlights
Scenario from the selected cricket video.

The frames from the cricket video are extracted and saved within the "Frames"
directory. The user is now ready to proceed with image preprocessing and highlight
Post-Condition generation.

This use case is a critical step in preparing the cricket video for the highlight
Comments generation process. It provides the extracted frames for further processing.

Use Case 4: Generate Image

Use Case ID UC-04

Use Case Name Generate Image

Actors User (Cricket Enthusiast)

Data Application, Extracted Frames

Trigger User clicks on the "Generate Image" button

Pre-condition Frames are successfully extracted

 Use Case ID UC-04

Assumptions The user has frames extracted from the selected cricket video

Normal Flow of Events

1. The user clicks on the "Generate Image" button within the application.

2. The application randomly selects and displays a frame from the directory where all
the frames were extracted.

Description 3. The user views the generated image.

Main Success
Scenario The user successfully generates and views an image from the extracted frames.

The user can choose to either confirm the image for further processing or regenerate
Post-Condition another image if not satisfied with the previous selection.

This use case allows the user to inspect the quality of the frames extracted from the
Comments cricket video and proceed with the highlight generation process.

Use Case 5: Confirm Image

Use Case ID UC-05

Use Case Name Confirm Image

 Use Case ID UC-05

Actors User (Cricket Enthusiast)

Data Application, Generated Image

Trigger User clicks on the "Confirm" button

Pre-condition An image has been generated and displayed

Assumptions The user has generated an image and is satisfied with it

Normal Flow of Events

1. The user views a generated image and decides it is suitable for further
processing.

2. The user clicks on the "Confirm" button within the application to confirm the
selected image.

Description 3. The application proceeds to the next step in the process.

Main Success The user confirms the image, indicating their satisfaction with the selected frame
Scenario for further processing.

The confirmed image is used for further processing in the highlight generation
Post-Condition process.

This use case allows the user to finalize their selection of a frame for highlight
Comments generation.
Use Case 6: Proceed with Scoreboard Detection
Use Case ID UC-06

Use Case Name Proceed with Scoreboard Detection

Actors User (Cricket Enthusiast)

Data Application, Confirmed Image

Trigger User clicks on the "Proceed" button

Pre-condition An image has been confirmed by the user

Assumptions The user has selected and confirmed an image

Normal Flow of Events

1. The user confirms an image for further processing within the application.

2. The user clicks on the "Proceed" button to initiate the next step in the process.

3. The application begins the process of scoreboard text detection and recognition
(using Tesseract OCR) on the confirmed image.

4. A progress bar displays the status of the text detection process, indicating the
progress in percentage.

Description 5. When the process reaches 100%, the user proceeds to the next step in the process.

Main Success The user confirms the image and successfully initiates scoreboard text detection and
Scenario recognition.
 Use Case ID UC-06

The application has completed scoreboard text detection and recognition, and the
Post-Condition user is ready to proceed with generating cricket highlights.

This use case is a crucial step in the process, as it involves detecting and recognizing
Comments scoreboard text to be used in the highlight generation.

Use Case 7: Generate Cricket Highlights

Use Case ID UC-07

Use Case Name Generate Cricket Highlights

Actors User (Cricket Enthusiast)

Data Application, Confirmed Image, Scoreboard Data, Video Footage

Trigger User clicks on the "Generate Highlights" button

Pre-condition Scoreboard data has been successfully detected and recognized

Assumptions The user has initiated scoreboard text detection, and the process is complete
 Use Case ID UC-07

Normal Flow of Events

1. The user has confirmed an image and completed scoreboard text detection and
recognition.

2. The user clicks on the "Generate Highlights" button to start the process of
generating cricket highlights.

3. The application combines the confirmed image, recognized scoreboard data, and
the original video footage to create highlight clips.

4. The highlights are generated based on user preferences (e.g., variety, interest)
selected in the next step.

5. The generated cricket highlights are saved in a new folder named "Final Video"
within the project directory.

Description 6. The user can access and view the created highlights from this folder.

If the user has not initiated scoreboard text detection or the process is not complete,
Alternate Flow of the application will prompt the user to complete the necessary steps before
Events generating highlights.

Main Success The user successfully generates cricket highlights from the confirmed image,
Scenario scoreboard data, and video footage.

Highlight clips are generated and saved in the "Final Video" folder, ready for user
Post-Condition access.

This use case represents the culmination of the user's interactions with the
Comments application, resulting in the creation of cricket highlights.
Use Case 8: Regenerate Image
Use Case ID UC-08

Use Case Name Regenerate Image

Actors User (Cricket Enthusiast)

Data Application, Video Footage Frames, Confirmed Image

Trigger User clicks on the "Regenerate Image" button

Pre-condition The user has confirmed an image but wishes to generate a new one.

Assumptions The user has initiated scoreboard text detection, and the process is complete.

Description Normal Flow of Events

1. The user has confirmed an image and completed scoreboard text detection and
recognition.

2. The user clicks on the "Regenerate Image" button to generate a new image for
extracting the scorecard.

3. The application randomly selects a frame from the video footage frames directory
to generate a new image.

4. The new image is displayed for the user to confirm, or they can choose to
regenerate again.
 Use Case ID UC-08

5. The user confirms the generated image for scoreboard text detection.

If the user has not initiated scoreboard text detection or the process is not complete,
Alternate Flow of the application will prompt the user to complete the necessary steps before
Events generating a new image.

Main Success
Scenario The user successfully generates a new image for extracting the scorecard.

The new image is available for scoreboard text detection, and the previous image
Post-Condition remains unchanged.

This use case allows the user to replace the previously confirmed image with a new
Comments one if they are not satisfied with the initial selection.

Use Case 9: Choose FPS for Frame Extraction

Use Case ID UC-09

Use Case Name Choose FPS for Frame Extraction

Actors User (Cricket Enthusiast)

Data Application, Video Footage

Trigger User selects the frame per second (FPS) option for frame extraction.

Pre-condition The user has selected a video for processing.

 Use Case ID UC-09

Assumptions The video has been successfully selected by the user.

Normal Flow of Events

1. The user has selected a video for processing.

2. The user clicks on the "Select Video" button and chooses a video file from their
computer.

3. After selecting the video, the user is prompted to choose a frame per second (FPS)
option for frame extraction (e.g., 5 FPS, 10 FPS, etc.).

4. The user selects their desired FPS option from the available choices.

5. The application begins the process of extracting frames from the video at the
Description chosen FPS.

Alternate Flow of If the user does not select an FPS option, the application will prompt the user to
Events choose one before proceeding with frame extraction.

Main Success The user successfully selects an FPS option for frame extraction, and the application
Scenario initiates frame extraction at the chosen rate.

Frame extraction commences at the user's chosen FPS, and the extracted frames are
Post-Condition available for further processing.

This use case allows the user to define the frame extraction rate, which impacts the
granularity of frame analysis and ultimately the quality of generated cricket
Comments highlights.
Use Case 10: View Cricket Highlights
Use Case ID UC-10

Use Case Name View Cricket Highlights

Actors User (Cricket Enthusiast)

Data Application, Generated Cricket Highlights

Trigger User wants to view the generated cricket highlights.

Pre-condition Cricket highlights have been successfully generated and saved.

Assumptions The user has successfully completed the process of generating cricket highlights.

Normal Flow of Events

1. The user has generated cricket highlights successfully, and they are saved in the
"Final Video" folder within the project directory.

2. The user opens the application and clicks on the "View Highlights" or a similar
button.

3. The application provides access to the saved cricket highlights.

Description 4. The user can watch and enjoy the highlights at their convenience.

Alternate Flow of If the user attempts to view highlights before generating them, the application will
Events prompt the user to complete the generation process first.

Main Success The user successfully accesses and views the generated cricket highlights.
 Use Case ID UC-10

Scenario

Post-Condition The user can watch the highlights, and they remain available for future viewing.

This use case allows the user to enjoy the cricket highlights generated by the
Comments application after completing the generation process.