Chapter 1: Introduction

1.1. Introduction
Cricpedia is an essential offline platform dedicated to cricket enthusiasts, where users
can access manually updated scores, fixtures, and the latest happenings in the world
of cricket. Although Cricpedia doesn’t feature a traditional job portal, it still provides
immense value by offering a hub for cricket fans and professionals to stay connected
with the sport. It’s a place where players, coaches, analysts, and cricket administrators
can find detailed, up-to-date information on matches and schedules that can help them
stay engaged with the cricketing community.
While Cricpedia doesn’t directly connect employers with job seekers like a traditional
job portal, it helps by keeping users informed about all things cricket—making it
easier for individuals to network within the cricketing world, attend games, and even
learn about new opportunities in the sport through updated fixtures and match scores.
Employment in the cricket industry, whether as a player, coach, or administrator, is
key to personal growth and societal integration. Having a central source of
information like Cricpedia helps individuals stay on top of the sport’s evolving
landscape, empowering them to make informed decisions about their careers.
Cricpedia, in this context, contributes by offering valuable cricket-related updates,
fostering connections, and giving individuals the tools they need to pursue meaningful
careers within the cricketing world.
1.2. Problem Statement
In the context of Nepal, many job seekers have to face hurdles.
 The website lacks real-time score and fixture updates, causing users to miss
important match results and upcoming games.
 Absence of a comprehensive and organized database for cricket events, along
with an inefficient search system, leads to outdated and difficult-to-find match
information.
 Lack of cricket-related news, including updates on team changes, player
performances, and upcoming tournaments, leaves users without valuable
insights into the sport.
 The manual updating process of scores and fixtures can be time-consuming
and prone to delays, leading to potential frustration for users who seek timely
information.

1
1.3. Objectives
1. To provides detailed, manually updated scores, upcoming fixtures, and player
statistics, ensuring users can access accurate cricket information.
2. To offers an intuitive interface for easy navigation of scores, fixtures, and
player stats, enhancing the user experience.
3. An admin panel to ensure smooth operation by managing manual updates and
maintaining the accuracy of content.
4. Data integrity and security to be prioritized, ensuring correct updates for
scores, fixtures, and player data for reliable cricket information.
1.4. Scope and Limitation
Scope
 Cricpedia allows admin to post detailed updates on match scores, upcoming
fixtures, and player stats, including match details, player performance, and
schedules.
 Users can easily navigate and view cricket-related information like scores,
fixtures, and stats through a simple, user-friendly interface.
 Admin manage the manual updates, ensuring accurate and timely posting of
content like scoreboards, player data, and match schedules.
 A structured file management system organizes cricket-related images, stats,
and content, ensuring easy access and efficient content display.
Limitation
 The job portal's security measures, while robust, may still be vulnerable to
Cricpedia relies on manual updates, which may lead to delays in posting
scores and fixtures.
 The website lacks real-time data, meaning users might miss live updates or
immediate changes.
 Limited interactivity, as users cannot contribute or update content themselves.
 Absence of a login system restricts personalized features like saving
preferences or following specific teams/players.
 The website does not offer detailed news or articles related to cricket beyond
scores, fixtures, and player stats.

2
1.5. Report Organization
This chapter is one of five that make up the report paper. The second chapter
provides definitions, an overview of relevant current systems, and a discussion of
their benefits and drawbacks. system analysis and design, including the requirements
and feasibility analyses, are presented in Chapter 3.The implementation is shown in
Chapter 4, along with explanations about testing and debugging. Chapter 5 provides a
brief explanation of the Conclusion, Limitations, and Future Enhancement.

3
 Chapter 2: Background Study and Literature Review
2.1. Background Study
The internet has revolutionized how we engage with cricket, just as it has with job
hunting. Cricpedia has become an essential resource for cricket fans and professionals
by providing real-time scores, fixtures, and player stats, replacing traditional sources
like newspapers or live event tracking.

Our aim is to enhance Cricpedia by analyzing user preferences and feedback to

improve its functionality and user experience. By understanding user needs, we can
add features that make accessing cricket information more efficient and user-friendly.

Additionally, Cricpedia promotes environmental sustainability by reducing the need

for paper-based cricket scorecards and printed schedules, contributing to a digital-first
approach. The platform also supports economic growth by providing job opportunities
in roles like web development, content creation, and customer service, stimulating a
healthy cricket ecosystem.
2.2. Literature Review
During our project investigation, we examined various cricket-focused websites and
apps. What became apparent is the limited availability of features, creating difficulties
in accessing real-time information and discovering relevant cricket content.
Among the platforms we explored, such as CricBuzz and ESPNcricInfo, there was a
noticeable absence of key features that are crucial for cricket enthusiasts. Users
expressed dissatisfaction with some aspects of these platforms, which emphasizes the
need for a more user-friendly solution within the cricket information ecosystem.

CricBuzz: CricBuzz is one of the most widely used and rapidly growing cricket
portals, offering a convenient platform for users to follow live scores, player stats, and
match updates. Notably, it provides detailed scorecards and match commentary, but
could benefit from more refined search options and interactive features. [1]

ESPNcricInfo: ESPNcricInfo stands out as a leading cricket portal, offering

comprehensive coverage of matches, player statistics, and cricket news. With a wide
range of features, it excels in providing match previews, reports, and expert

4
commentary. However, it could improve on streamlining its navigation and offering
personalized content. [2]
Upon evaluating these platforms, it became clear that while they offer excellent
content like live updates and player stats, there are areas for improvement in user
experience, search functionality, and interactivity. Enhancing these features would
improve the usability and engagement of cricket websites, providing users with a
more comprehensive and enjoyable cricket experience.

5
 Chapter 3: System Analysis and Design
3.1. System Analysis
Systems Analysis and Design is an active field in which analysts repetitively
learn new approaches and different techniques for building the system more
effectively and efficiently. The primary objective of systems analysis and design is to
improve organizational systems. This tutorial provides a basic understanding of
system characteristics, system design, and its development processes. It is a good
introductory guide that provides an overview of all the concepts necessary to build a
system. [3]
We have chosen the Agile methodology for CricPedia as it allows us to be
flexible and responsive to user feedback and changing trends in cricket. Agile enables
us to continuously improve the platform, adding new features or refining existing
ones based on user needs, making it more engaging and user-friendly.
By breaking the development process into smaller, manageable tasks, Agile ensures
quick adaptations and frequent feature updates, which keeps the website relevant and
up-to-date. This approach helps maintain a collaborative workflow, ensuring that we
consistently deliver value to users, whether it's live scores, fixtures, or player stats.
Agile's focus on flexibility, iteration, and improvement makes it ideal for developing
a dynamic and responsive cricket portal that evolves with the fast-paced nature of the
sport.

Figure 1: Agile Methodology

6
3.1.1. Requirement Analysis
To make our system work, it needs to fulfill the following requirements:
i. Functional Requirements
 Users can easily access the website to view match scores, upcoming fixtures,
and player stats, with no need for registration.
 Admin manually update match scores, fixtures, and player statistics to ensure
accurate and timely information.
 The website allows users to browse and filter match schedules and player
statistics based on teams or players.
 Admin manage all updates and content through an efficient admin panel to
ensure accuracy.
 The website is designed with a responsive layout, ensuring users have a
smooth browsing experience on both desktop and mobile devices.
 Notifications alert users to new updates, such as upcoming fixtures or player
stats changes.
 Simple and user-friendly navigation makes it easy for users to quickly find
scores, fixtures, and player details.

Figure 2: Use case

7
 ii. Non-Functional Requirements
 Availability: The website will be available offline, providing constant access
to scores, fixtures, and player stats.
 Security: Data will be managed securely, with no user registration or
personal information stored.
 Performance: The website will be optimized for fast loading and smooth
navigation on both desktop and mobile devices.
 Reliability: The website will be consistently updated by admin to ensure
accurate and dependable information for users.
3.1.2. Feasibility Analysis
A feasibility study involves evaluating and analyzing a proposed project or system to
determine its viability. Before proceeding with the development of the system, we
conducted the following feasibility studies to assess whether the system could be built
according to the specified requirements within the allotted time. [4]
i. Technical Feasibility
The purpose of this study is to evaluate the technical requirements and feasibility
of the CricPedia website. Since the platform uses existing technologies for offline
updates and does not require live API integrations, developing and maintaining
the system presents no significant technical challenges.
ii. Operational Feasibility
Our Cricpedia project makes sense because it is easy to use for cricket fans,
providing seamless access to match scores, upcoming fixtures, and player stats.
We have carefully considered the resources needed to maintain accurate and up-
to-date information, ensuring they align with our goal of delivering a reliable and
user-friendly platform for cricket enthusiasts.
iii. Economic Feasibility
The purpose of this study is to determine how the organization and system will
be affected financially. Since Cricpedia is an offline platform and does not
require live APIs or external integrations, the cost to build and maintain the
system is minimal. The only ongoing expense is for periodic updates and internet
connectivity to manually refresh match scores, fixtures, and player stats.

8
iv. Schedule Feasibility
The most crucial evaluation for Cricpedia's success is ensuring the project is
completed on time. If the project is not finished as scheduled, it will not meet
user expectations. To determine the feasibility of completing the project within
the allotted time frame and with the available resources, we regularly assess the
scope of work. For scheduling feasibility, we utilized a Gantt chart to plan and
track the progress of the Cricpedia website development.

Table 1: Gantt Chart

3.1.3. Data Modeling (E-R Diagram)
The model for this project (Cricpedia) is represented by an ER (Entity Relationship)
diagram. The project's entity-relationship diagram illustrates the relationships between
key components such as users, matches, fixtures, player stats, and scores. It visually
maps out how data is structured and connected, ensuring efficient management and
display of match information, player details, and upcoming fixtures on the website.

9
 Figure 3: ER diagram
3.1.4. Process Modeling (DFD)
Data Flow Diagrams depict the movement of data from external entities into the
system and from one process to another within the system. [5] The following are the
current system's Data Flow Diagrams (DFD) for Cricpedia. Each process in the
system is first illustrated as a Context Level DFD, followed by a Detailed DFD. The
Context Level DFD provides a high-level overview of the system’s input, output, and
data flow, focusing on the interaction between the user, the website, and data storage.
The Detailed DFD offers a deeper view of the interactions between the system’s
subprocesses, showcasing how match information, player stats, and fixtures are
managed and displayed. This is further explained in the figure below.

Figure 4: Context diagram

10
Note: datas includes articles, squad, scoreboard, player stats and fixtures.

Figure 5: DFD level 1

11
3.2. System Design
3.2.1. Architectural Design
The next design phase for Cricpedia will involve planning the website’s
architecture. In this phase, the user interface and data will be organized
separately. The business layer, responsible for processing match data, player
stats, and fixtures, will be independent from the website’s front-end views.
Data will be stored in a structured database, and PHP will be used to query this
database and handle server-side scripting. Other components related to the
management of match data, user interactions, and content will have their
respective layers. The figure following illustrates the website’s architecture.

Figure 6: Three Tier Architecture

12
3.2.2. Database Schema Design

Figure 7: Database Schema Diagram

3.2.3. Interface Design

Before starting the actual design phase of Cricpedia, we first create interface
designs to visually represent how users will interact with the website. These
designs highlight essential features like viewing the scoreboard, browsing
upcoming fixtures, and checking player stats. By following our Functional
Decomposition Diagram, these early interface designs serve as a guide for the
layout and functionality of the web pages. This process ensures the user
interface is intuitive, easy to use, and meets the needs of our users, providing a
seamless experience while accessing cricket-related information.

13
 Figure 8: UI design of Cricpedia (Interface Design)

Figure 8 depicts Cricpedia's user interface design, which focuses on appearance and
usability. The interface includes a fixtures button to view upcoming matches with
full squad details, a scoreboard button for detailed match scorecards, a player stats
button displaying batting and bowling records, and an articles section with cricket-
related content. These features enhance user engagement and fulfill Cricpedia’s
objectives effectively.

3.2.4. Physical DFD Design

Note: datas includes articles, squad, scoreboard, player stats and fixtures.
Figure-9: DFD Diagram

14
 Chapter 4: Implementation and Testing
4.1. Implementation
4.1.1. Tools Used
The various system tools used in developing both the front-end and back-end of the
Cricpedia website are discussed below:
Front-end:
 HTML5: HTML is used to structure the content on the web pages, providing
the foundation for displaying information like scoreboards, fixtures, and
player stats.
 Tailwind CSS: Tailwind is a utility-first CSS framework used for designing
the layout and styling of the pages. It allows for a highly customizable and
responsive design for Cricpedia.
 JavaScript: JavaScript is used for interactive elements, such as updating
scores or navigating through fixtures, ensuring dynamic and smooth user
interactions.
Back-end:
 PHP: PHP is a server-side scripting language that handles the server logic for
Cricpedia, processing requests like displaying match information or player
stats. It integrates seamlessly with the front-end and provides the necessary
functionality for dynamic content.
 MySQL: MySQL is used to manage and store data related to matches, player
statistics, and fixtures. It serves as the relational database management system,
ensuring the data is organized and easily accessible for the website. MySQL's
powerful querying capabilities support the efficient retrieval of information to
be displayed to users.
This combination of technologies ensures that Cricpedia runs smoothly, providing a
responsive and user-friendly platform for cricket fans to access the latest match
information.
4.1.2. Implementation Details of Modules
After finalizing the design and addressing any issues that arose during the design
process, we proceeded to implement the Cricpedia application. Implementing a
website of this nature requires significant resources, and detailing the entire process is

15
beyond the scope of this paper. However, key aspects of the implementation are
described below:
 Admin Panel: This module provides information to the admin, including
details about users, matches, and player statistics. Admin can manage content,
update scoreboards, and remove or edit match data.
 Match & Fixture Management: This allows admin to add or modify fixtures,
update match scores, and display player stats. It is the core module for keeping
the website’s content updated.
 Player Stats: This feature enables the admin to manage player profiles, update
performance statistics, and ensure that data on players is accurate and current.
 User Interface: The user interface provides a seamless navigation experience,
allowing users to browse fixtures, view player stats, and check the latest match
scores.
 Static Data Display: Since Cricpedia operates offline, all match scores,
fixtures, and player stats are pre-loaded into the system and are displayed to
the users when they visit the site.
These key aspects allow Cricpedia to function efficiently, providing cricket fans with
up-to-date information about matches, players, and fixtures, even without live data
updates.
4.2. Testing
Testing is performed to evaluate the behavior of Cricpedia as a fully integrated
platform, based on its functional and non-functional requirements. Before
deployment, thorough testing is essential to ensure the application runs smoothly and
meets all specifications. Various test cases will be written to assess the website.
Testing includes performance checks, functionality, database loading times, response
time, server handling, and user interaction. Ensuring that the site delivers accurate
data, fast loading speeds, and a seamless experience for users will be a key focus.
Additionally, testing will address aspects such as match score display, fixture updates,
and player statistics management to ensure a reliable and user-friendly experience.

16
 4.2.1. Test Cases for Unit Testing (Manual Testing)
Table 2: Viewing Player Stats
Test Case Test Data Expected Actual Status
Description Result Result

PS 1: User Player: Virat Kohli Display stats for Virat Expected Pass
attempts to view Kohli including runs,
player stats for a average, and strike
valid player rate
PS 2: User Player: Display message expected Pass
attempts to view "NonExistentPlayer" Player not found
player stats for an
invalid player

Table 3: Viewing Fixtures

Test Case Test Data Expected Actual Status
Description Result Result

F 1: User attempts Date: "Upcoming Display a list of Expected Pass

to view upcoming Fixtures" upcoming cricket
fixtures matches with date,
time, and venue
F 2: User selects a Fixture: India vs Display match Expected Pass
fixture to view Australia, 2025-03- details including
details 20 teams, date, time,
and location

17
 Table 4: Viewing Scoreboard
Test Case Test Data Expected Actual Status
Description Result Result

S 1: User views Match: India vs Display match Expected Pass

past match Pakistan, 2024-12-10 scorecard including
scorecards batting and bowling
stats
S 2: User attempts Match: South Africa Display message No Expected Pass
to view scoreboard vs England, 2025- data available
for a match with 03-21
no data yet

Table 5: Admin Login

Test Case Test Data Expected Actual Status
Description Result Result

A LOG 1: Admin Username: admin Display message expected Pass

enters a wrong Password: 1234 **Invalid Email or
email password

A LOG 2: Admin Username: admin Admin expected Pass

enters correct Password: admin123 log in successful
email and
password

18
 Chapter 5: Conclusion and Future Recommendation
5.1 Lesson Learnt/Outcome
The goal of Cricpedia is to create a user-friendly platform that provides detailed
player stats, match fixtures, and scoreboards. With an intuitive interface and
responsive design, users can easily access stats, browse upcoming fixtures, and view
past match results. Cricpedia aims to deliver accurate, up-to-date cricket information,
offering an engaging experience for cricket fans across all devices.
5.2 Conclusion
In conclusion, Cricpedia is an offline platform designed to provide cricket enthusiasts
with detailed player stats, match fixtures, and scoreboards. With the completion of
Cricpedia, users can easily access cricket information without the need for live
updates. We met all our objectives, adhering to the plan while incorporating key
features.
The use of HTML, CSS, and PHP for this project allowed us to create a responsive,
interactive platform with smooth backend functionality.
Throughout the development, we followed the Agile model, enabling us to adapt
based on user feedback and keep the platform user-friendly. Although the website
does not feature live updates, Cricpedia provides valuable and comprehensive cricket
data. Future iterations will focus on enhancing user experience and adding additional
features.

5.3 Future Recommendation

In the future, we plan to improve Cricpedia to make it more user-friendly and
accessible:
1. Enhance mobile access for users on the go.
2. Implement advanced search filters for easy match and player navigation.
3. Add video highlights and match replays.
4. Improve security measures for safer browsing.
5. Offer personalized player and team dashboards.
6. Expand coverage to include international cricket events.
7. Provide comprehensive player and team analytics.
8. Incorporate feedback and ratings for a better user experience.

19
Appendix

Figure 12: Home Page

Figure 13: Admin Dashboard

20
 Reference
[1] https://www.espncricinfo.com/. About ESPNCRICINFO [Online]. Available:).
https://www.espncricinfo.com/home
[2] https://www.cricbuzz.com/, Know about Cricbuzz [Online]. Available:).
https://www.cricbuzz.com/home
[3] https://www.tutorialspoint.com/, System Analysis and Design Tutorial [Online].
Available:). https://www.tutorialspoint.com/system_analysis_and_design/index.htm
[4] https://www.investopedia.com/, What Is a Feasibility Studyus [Online].
Available:).https://www.investopedia.com/terms/f/feasibility-study.asp
[5]https://www.lucidchart.com/, What is a data flow diagram?us [Online].
Available:).https://www.lucidchart.com/pages/data-flow-diagram

21