ICRIC (CRICKET CLUB SYSTEM)

A PROJECT REPORT

Submitted by

Mayank Singh Senger

(1600101166)

Jyotsana Srivastava
(1600101553)

In partial fulfillment of requirements for the award of the degree

of

Master of Computer Application

INTEGRAL UNIVERSITY LUCKNOW

MAY 2022
 INTEGRAL UNIVERSITY

CERTIFICATE

Certified that this project “I CRIC (CRICKET CLUB SYSTEM)” is the bonafide

work of “MAYANK SINGH SENGER and JYOTSANA SRIVASTAVA” who

carried out the project work under my supervision.

Dr.Tasneem Ahmed
Assistant Professor
Depart of Computer Application
Integral University, Lucknow
 INTEGRAL UNIVERSITY

CERTIFICATE

Certified that this project “I CRIC (CRICKET CLUB SYSTEM)” is the bonafide

work of “MAYANK SINGH SENGER and JYOTSANA SRIVASTAVA” who

carried out the project.

Mr.Sudheer Kumar Singh Dr. Mohammad Faisal

(Project Coordinator) (Head of Department)

Department of Computer Application Department of Computer

Application
Integral University, Lucknow Integral University, Lucknow
 DECLRATION

“I hereby declare that this submission is my own work and that”, to the best of
my knowledge and belief, it contains no material previously published or written by
another person nor material which has been accepted for he award of any other
degree or diploma of the university or other institute of higher learning, except where
due acknowledgement has been made in the text”.

Date:

(MAYANK SINGH SENGER) (JYOTSANA SRIVASTAVA)

1600101166 1600101553
 ACKNOWLEDGEMENT

We are grateful to the teacher’s and faculties of our department for the completion of our
Project Report on “I Cric (Cricket Club System)” under the guidance of Dr.Tasneem
Ahmed (Project Guide), Dr.Sandeep Kumar Nayak (Lab Associated Professor), and Mrs.
Saman Khan (Lab Instructor).

They have made sincere efforts to make the report more meaningful, complete, compact
and comprehensive. Its great pleasure to let your know that I have put my feelings and
knowledge into practice.

At last, we give special thanks to our batch mates, faculty members of Departments
Computer Application, our parents & everyone for their valuable suggestions & support
without which this Project report could not be completed.

JYOTSANA SRIVASTAVA

MAYANK SINGH SENGER

 ABSTRACT

The proposed ICric (Cricket Club Management System) is completely

automated. The proposed system allows the user to book ground for

various days, request for club membership and register for t h e various

training batches. Less effort is required for maintaining the database of

club using this software. Margin of error will be reduced and regulating

members will be a breeze by using this software. The end users can register

for membership, book ground, register for different training batches and

receive notices from the management. The managerial functions are

carried out by the Admin. Admin can approve the bookings done by end

users, send notices to the online notice board, check different members of

the club and the users registered for various training batches.
 INDEX

S.No. Index Page

No.
Chapter 1 INTRODUCTION 1-6

1.1 Introduction 1

1.2 Aim 1

1.3 Drawback of current manual system 2

1.4 Establish the need of new system 3-4

1.5 Proposed System 5

Chapter 2 HARDWARE AND SOFTWARE 7

REQUIREMENTS
2.1 For Development Purpose 7

2.2 For Application Purpose 7

Chapter 3 PROBLEM IDENTIFICATION

Chapter 4 FEASIBILITY 8-14

3.1 Software Development Life Cycle Model 8

3.2 GENERAL OVERVIEW 9

3.3 Flow Chart 10

3.4 ER Diagram 11

3.5 DFD Diagram 12-14

IMPLEMENTATION DETAILS 15 - 20

4.1 FRONT END 15 - 20

Chapter 5 TESTING AND IMPLEMENTATION 21- 31

5.1 UNIT TESTING 21 - 22

5.2 INTEGRATION TESTING 23 - 24

 5.3 SOFTWARE VERIFICATION AND VALIDATION 25 -
27
5.4 Black-Box Testing 28

5.5 White-Box Testing 29 -

30
5.6 SYSTEM TESTING 31

Chapter 6 RESULTS 32 -
34
Chapter 7 ADVANTAGES 35

Chapter 8 CONCLUSION 36

BIBLIOGRAPHY 37
 CHAPTER 1: INTRODUCTION

1.1 INTRODUCTION

I Cric Cricket club management project designed with the motive of managing a cricket club. This
software system consists of various online booking and management functionaries needed by a
cricket club. It provides various options like ground bookings, member registrations, notice posting,
member registration, batch registration, Schedules, League, Series, Player Statistics and more. This
software system assures efficient management and maintains the functioning on a cricket club.

1.2 AIM
The aim of the project is to provide the complete information of the National and International
Cricket
Tournaments statistics. The information is available Country wise, and Player wise. The project
have following Master Screens.
 Country
 Player Details
 Team Members
 Matches

By entering the data of the each match. We can get all type of reports instantly. Which will be
useful to call back history of each player, Also the team performance in each match. We can get a
report on numbers of matches win, and last. Graphical Display of the data also provided, so one get
graph instantly whenever it is required. We are using bar graphs here. In the future, we can make in
many types. The bar graphs provided to so Runs scored by each player in match. The bar Graphs
also provided for each player to so his performance in all matches he played. So graphs helps to
analyze the information faster also, it is attractive compare to the data display.
The modules of the project are as shown below.
 Country Detail Entry Screen
 Player Details Entry Screen
 Team Members Entry Screen
 Match Detail Entry Screen
Page No. 1
 Match Ball by Ball Entry Screen
 Player wise details screen
 Player performance in the played matches
 Match wise Comparison Screen
 Players wise, Runs Score, Wickets taken Etc.,

This project is very use for Cricket match broadcasters to get information quickly. Also for Cricket
lovers who very much interested in Cricket Statistics. The project written in Asp.net with C#,
JavaScript, The back end for the project is SQL Server. The project is designed very user friendly
such that even people who knows only the basic operation of the computer can use this software. So
no technical expertise is required to use this software.

An iCric is a software developed to simplify the services easily accessible to every cricket
administrator, organizer, team manager, player, fan and follower so they can experience cricket like
never before! With the help of this software, we can manage league, series, team, grounds, match
schedules and match updating. In addition, Priorcric includes reporting of matches like over
commentary, summary, scoreboard, Playing XI player info, live scoreboard. It has reporting for
batting records, bowling records, highest run scored records, most 4 runs stats, most 6 runs stats ,
best bowling stats records

Page No. 2
1.3 DRAWBACK OF CURRENT MANUAL SYSTEM

1.The current manual system has a lot of paper work and it does not deal with users that are not part of
any leagues or series.

2.To maintain the records of players statistic and role manually handled by paper.

3.With the increase in database, it will become a massive job to maintain the database.

4.Requires large quantities of file cabinets, which are huge and require quite a bit of space in the office,
which can used for storing records for previous details.

5.The retrieval of records of previously registered players will be a tedious job.

6.Lack of security for the records, anyone disarrange the records of your system.

7.If someone want to check the details of their previous stats, the previous system does not provide any
necessary detail of this type.

1.4 ESTABLISH THE NEED OF NEW SYSTEM

1.Problem of Reliability: Current system is not reliable. It seems to vary in quality from one month to
the, next. Sometimes it gives good outputs, but sometimes the output is worst.

2. Problem of Accuracy: There are too many mistakes in reports.

3.Problem of timeliness: In the current system the reports and output produced is mostly late and in
most of the cases, it is useless because it is not on time.

4.Problem of Validity: The output and reports mostly contains misleading information. The user
information is sometimes not valid.

5.Problem of Economy: The current system is very costly. We have to spend lots of money to keep
the system up to going, but still not get the desired results.

6.Problem of Capacity: The current system is suffering from problem of capacity also. The staff for
the tournaments is very less and the workload is too much. Few peoples cannot handle all the work.

Page No. 2
1.5 PROPOSED SYSTEM
1.Player Details: The new proposed system stores and maintains all the player details.

2.Calculations: The new proposed system calculates stats and scorings automatically and it is very
fast and accurate.

3.Registers: There is no need of keeping and maintaining records, stats, scoring and register manually.
It remembers each record and we can get any report related to players and series at any time.

4.Speed: The new proposed system is very fast with 100% accuracy and saves times.

5.Work force: The new proposed system needs less work force. Less people can do the large work.

6.Efficiency: The new proposed systems complete the work of many salesperson in less time.

7.Past details: The new proposed system contains the details of every past matches and players
records for future assistance.

8.Reduce redundancy: The most important benefit of this system is that it reduced the redundancy of
data with the data.

9.Workload: Reduces the workload of the data store by helping in easy updated of the products and
providing them the necessary details together with automatic record management.

10. Easy statement: Series-end and match-end statements easily taken out without getting headaches
on browsing through the day end statements.

Page No. 3
NEED:

I have designed the given proposed system in the ASP to automate the process of day-to-day activities
of Cricket Clubs like New Player Registration, team adding, match scheduling, match entries, league
creation and maintenance, etc., online facilities to the multiple user etc.

The complete set of rules and procedure related to Cricket Clubs day to day activities and generating
report is called “CRICKET CLUB MANAGEMENT SYSTEM (I Cric)”.My project gives a brief idea
regarding automated Cricket Club activities.

The following steps that give the detailed information of the need of proposed system are:

Performance: During past several decades, the Cricket club management system is supposed to
maintain manual handling of all the club daily activities. The manual handling of the record is time
consuming and highly prone to error. To improve the performance of the Cricket club management
system, the computerized Cricket club management system (I Cric) is to be undertaken. The
computerized Cricket club project is full computerized and user friendly even that any of the user can
see the player’s report and the series matches.

Efficiency: The basic need of the project is efficiency. The project should be efficient so that whenever
a new team or player is added, and automatically their records are maintained by our system , records
may be matches or player runs records, fielding records and bowling records etc., And if any player is
injured we can also change he player inside the match in the our system.

Control: The complete control of the project is under the hands of authorized person who has the
password to access this project and illegal is not supposed to deal with. All the control is under the
administrator the other members have the rights just see the records not to change any transaction or
entry.

Security: Security is the main criteria for the proposed system. Since illegal access may corrupt, the
database and it will affect not only the Cricket Clubs but also it affects the Players records. Therefore,
security has to be in this project.

Page No. 4
 CHAPTER 2: HARDWARE AND SOFTWARE REQUIREMENTS

2.1 FOR DEVELOPMENT PURPOSE:

 Hardware requirement

Number Description
1 4GB RAM or more
2 Intel i3 or AMD Ryzen3 (or Faster)
3 At least 160 GB of the free hard disk space

 Software requirement

Number Description Type

1 Operating System Windows 8 / Windows 10
2 Language Asp.net with C#
3 Database MySQL
4 IDE Visual Studio
5 Browser Google Chrome

2.2 FOR APPLICATION PURPOSE:

 Hardware

Number Description
1 Desktop or Mobile.
2 At least 256MB RAM.
3 At least 100 MB ROM.

  Software

Number Description
Page No. 5
1 Web browser.
 CHAPTER 3: PROBLEM IDENTIFICATION

Problem areas discovered in current operation

 Could not track player records of multiple matches.

 No Series handling management.

 Required workforce for any operation.

 Lack of automated player enquiry system

 No player acceptation and rejection records for team.

 No Batting records for series and leagues.

 No Bowling records for series and leagues.

 No fielding records for series and leagues.

 No accurate calculation of records.

 Handling multiple, Leagues are very difficult.

 Data miss match also happens.

 Not all records can be access by outsiders.

 Maintaining records becomes so difficult and time taken problem.

Lack of immediate retrievals: -

The information is very difficult to retrieve and to find particular information like- E.g. – To find
out about the previous matches records, previous series records, players records on league team
records. This results in convenience wastage of time.

Lack of immediate information storage:-

The information generated by various manual in paper that takes time and efforts to be stored at
right place.

Lack of prompt updating:-

Various changes to information like player name or details, team details are difficult to make as
paper work is involved.
CHAPTER 4: FEASIBLITY STUDY
Page No. 6
A feasibility study is a high-level capsule version of the entire System analysis and Design Process.
The study begins by classifying the problem definition. Feasibility is to determine if it is worth
doing. Once an acceptance problem definition has generated, the analyst develops a logical model
of the system. A search for alternatives analyzed carefully.

There are four parts in feasibility study.

 Operational Feasibility
 Technical Feasibility
 Economic Feasibility
 Legal Feasibility

Technical Feasibility

This involves questions such as whether the technology needed for the system exists, how difficult
it will be to build, and whether the firm has enough experience using that technology. The
assessment based on outline design of system requirements in terms of input, processes, output,
fields, programs and procedures. This can be qualified in terms of volume of data, trends, frequency
of updating in order to introduce the technical system. The application is the fact that it has
developed on windows XP platform and a high configuration of 1GB RAM on Intel Pentium Dual
core processor. This is technically feasible .The technical feasibility assessment focused on gaining
an understanding of the present technical resources of the organization and their applicability to the
expected needs of the proposed system. It is an evaluation of the hardware and software and how it
meets the need of the proposed system.

During the technical feasibility step, the following must completed.

 Test for technical feasibility

 Examine the operational requirements
 Identify potential safety and environmental hazards
 Conduct a preliminary production feasibility assessment
 Conduct a preliminary manufacturing assessment
 Estimate engineering prototype costs

Page No. 7
Operational Feasibility

Operational feasibility is the measure of how well a proposed system solves the problems, and takes
advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development. The operational
feasibility assessment focuses on the degree to which the proposed development projects fits in with
the existing business environment and objectives with regard to development schedule, delivery
date, corporate culture and existing business processes. To ensure success, desired operational
outcomes must imparted during design and development. These include such design-dependent
parameters as reliability, maintainability, supportability, usability, reducibility, disposability,
sustainability, affordability and others. These parameters required to be a considered, at the early
stages of design if desired operational behaviors are to be a realized. A system design and
development requires appropriate and timely application of engineering and management efforts to
meet the previously mentioned parameters. A system may serve its intended purpose most
effectively when its technical and operating characteristics engineered into the design. Therefore,
operational feasibility is a critical aspect of systems engineering that needs to be an integral part of
the early design phases.

The essential questions that help in testing the operational feasibility of a system include
following:     
 Does current mode of operation provide adequate throughput and response time?
   Does current mode provide end users and managers with timely, pertinent, accurate and useful
formatted information?
 Does current mode of operation provide cost-effective information services to the business?
 Could there be a reduction in cost and or an increase in benefits?
 Does current mode of operation offer effective controls to protect against fraud and to
guarantee accuracy and security of data and information?
 Does current mode of operation make maximum use of available resources, including people,
time, and flow of forms?
 Does current mode of operation provide reliable services
  Are the services flexible and expandable?
 Are the current work practices and procedures adequate to support the new system?
 If the system is developed, will it be a used?

Page No. 8
  Manpower problems
 Labor objections
 Manager resistance
 Organizational conflicts and policies
 Social acceptability
 Government regulations
  Does management support the project?
   Are the users not happy with current business practices?
 Will it reduce the time (operation) considerably?
 Have the users been involved in the planning and development of the project?
  Will the proposed system really benefit the organization?
 Does the overall response increase?
 Will accessibility of information be lost?
 Will the system affect the customers in considerable way?
 Legal aspects

Economic Feasibility

Establishing the cost-effectiveness of the proposed system i.e. if the benefits do not outweigh the
costs then it is not worth going ahead. In the fast-paced world today, there is a great need of online
social networking facilities. Thus, the benefits of this project in the current scenario make it
economically feasible. The purpose of the economic feasibility assessment is to determine the
positive economic benefits to the organization that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This assessment typically involves a
cost/benefits analysis.

Possible questions raised in economic analysis are:

 Is the system cost effective?
 Do benefits outweigh costs?
 The cost of doing full system study
 The cost of business employee time
  Estimated cost of hardware

Page No. 9
  Estimated cost of software/software development
 Is the project possible, given the resource constraints?
 What are the savings that will result from the system?
 Cost of employees' time for study
 Cost of packaged software/software development
 Selection among alternative financing arrangements (rent/lease/purchase)

Legal Feasibility

A feasibility study is an assessment of the practicality of a project or system. A feasibility study

aims to objectively and rationally uncover the strengths and weaknesses of an existing business or
proposed venture, opportunities and threats present in the natural environment,
the resources required to carry through, and ultimately the prospects for success. In its simplest
terms, the two criteria to judge feasibility are cost required and value to be an attained.

A well-designed feasibility study should provide a historical background of the business or project,
a description of the product or service, accounting statements, details of
the operations and management, marketing research and policies, financial data, legal requirements
and tax obligations. Generally, feasibility studies precede technical development
and project implementation. A feasibility study evaluates the project's potential for success;
therefore, perceived objectivity is an important factor in the credibility of the study for potential
investors and lending institutions. It must therefore be a conducted with an objective, unbiased
approach to provide information upon which decisions can based.

Page No.
10
 CHAPTER 5: SYSTEM ANALYSIS AND USER REQUIREMENTS

The software requirement specification is a produced at the culmination of the analysis task. The
function and performance allocated to software as part of system engineering are refined by
establishing a complete description, a detailed functional description, a representation of system
behavior, an indication of performance requirement and design constraints, appropriate validation
criteria and other information requirements.

The Introduction of software requirements specification states the goals and objectives of the
software, describe it in context of the computer-based system. Actually, the information may be
nothing more than the software scope-planning document.

Here in this project the introduction is a described as follows:

 Information content, flow and structures documented.
 Hardware, software and human interfaces described for external system elements and internal
software functions.
 The use of sensor that improve the usability efficiency.

A description of each function required to solve the problem is present in functional description.
A processing narrative also provided.
In many cases, the software requirement specification may be an accompanied by an executable
prototype, a paper prototype or a preliminary user’s manual. The preliminary user’s manual presents
the software manual as a black box, i.e., heavy emphasis laid on user input and the resultant output.
The manual can serve as valuable tool for uncovering problems at the human/machine interface.
Page No.
11
 REVIEW OF PREVIOUS WORK
I Cric (Cricket Management Club) system provides the benefits of cricket administrator, organizer,
team manager, player, fan and follower so they can experience cricket like never before! With the
help of this software, we can manage league, series, team, grounds, match schedules and match
updating. In addition, Priorcric includes reporting of matches like over commentary, summary,
scoreboard, Playing XI player info, live scoreboard. It has reporting for batting records, bowling
records, highest run scored records, most 4 runs stats, most 6 runs stats , best bowling stats records.
I Cric is powerful, flexible, and easy to use and is designed and developed to deliver real
conceivable benefits to Cricket Clubs. More importantly, it is a backed by reliable and dependable
support.

A Cricket club is a place where Players come up for playing matches inside a team under some
rules. Cricket club provide facilities like-
 Player recognitions.
 Providing Kits for players.
 Manage Team.
 Manager Players details.
 Manage records.
Various operational works that are done in a Cricket Club are-
 Recording information about the players that come.
 Recording information about the teams that come.
 Recording information about the matches of teams.
 Managing Leagues and tournaments.

Page No.
12
 Keeping records of Leagues and tournaments.
 Keeping information about the various matches and manage previous and upcoming matches.
These various jobs need to done in a Cricket Club by the operational staff. All these works done on
papers. The works is a done as follows:-
 Information about Teams is a done by just writing the Team name, Players inside a team.
Whenever the Team comes up with information is stored freshly.
 Information about Player is a done by just writing the Player name, age, batting style, bowling
style, contact details. Whenever a player comes up his information is stored freshly.
 Player’s records generated by recording runs, six, four, RR, over, etc. on a separate sheet and at
last, they all summed up.
 League, Team, Player, Schedule information is a generally recorded on the document, which
contain all information. It is a destroyed after some time to decrease the paper load in the club.

The scorer does all this work manually and other operational staff and lot of papers are needed to be
handled and taken care of. League admin have to remember various matches scheduled and
sometimes miss better alternatives as they cannot remember them at that time.

The limited time and resources have restricted us to incorporate, in this project, only main activities
that are performed in a Cricket Club Management System, but almost care has been taken to make
the system efficient and user friendly. “I Cric (Cricket Club Management System)” has designed to
computerize the following function that performed by the system.
 Registration of two types one for player registration and one for league admin registration.
 Home: It the collection of stats of players, schedules and points of teams.
 Schedule list: have fixture matches and result matches.
 Manage Schedule: creation of new schedules, edit, and update feature of the schedules.
 Create series creation of new series.
 Manage sponsor: creation of the sponsor for the series.
 Manager home ground: creation of the home ground for the series matches.
 Series details: carries details of the series.
 Player search: Search of the player and on Player name click redirect to the player detail page.
 Team creation: creation of the team.

Page No.
13
 Team list: carries the list of the team inside a particular series.
 Assign Team: carries the functionality for the assign team to the series.
 Team details: carries the details of the player inside a team.
 Batting records: have batting records player list.
 Most four records: have most four hits records player list.
 Most Six records: have most six hits records player list.
 Highest score: have highest runs scores in a single match records player list.
 Bowling records: have bowling records player list.
 Fielding records: have fielding records player list.
 Scoreboard: carries live match scoring, player in a match, over commentary, screen scoring,
Scoreboard, match info.
 Start Inning: carries player selection, toss, choose to, match playing, etc.
 Player login: carries details of series only shows to players.

The I Cric is a designed for multispecialty cricket clubs, to cover a wide range of cricket clubs
administration and management processes. It is an integrated end-to-end Cricket Club Management
System that provide relevant information across the User and Cricket Clubs to support effective
decision making for the matches.

Page No.
14
 PROJECT DESCRIPTION
The Project I Cric (Cricket Club Management System) includes registrations of Players,
Administrator, storing their details into the system, and computerized scoring and maintain
everything on system. The software has the facility to five a unique id for every players and stores
the details of every players and teams automatically. It includes a search player to know the status
of each player. User can search availability of a Player and the details of a player and also team
details and his/him scoring records.

The I Cric (Cricket Club Management System) can be entered using a username and password or
without username and password just by searching league. It is accessible either by an administrator,
Players and normal user but accessibility is different. Administrator can add or edit data into the
database. The data can retrieved easily. The interface is very-user friendly. The data is and well
protected for personal use and makes the data processing very fast.

The I Cric (Cricket Club Management System) is powerful, flexible, and easy to use and is designed
and developed to deliver real conceivable benefits to hospitals.
The I Cric (Cricket Club Management System) is a designed for multispecialty Cricket Clubs, to
cover a wide range of Cricket club administration and management processes. It is and integrated
end-to-end Cricket Management System that provides relevant information across the Cricket club
and user to support wide range of cricket’s matches and their records.
I Cric Cricket club management project designed with the motive of managing a cricket club. This
software system consists of various online booking and management functionaries needed by a
cricket club. It provides various options like ground bookings, member registrations, notice posting,
member registration, batch registration, Schedules, League, Series, Player Statistics and more. This
software system assures efficient management and maintains the functioning on a cricket club.

Salient Features:


Page No.
15
Page No.
16
1.5 FEASIBILITY STUDY

A feasibility study is a high-level capsule version of the entire System

analysis and Design Process. The study begins by classifying the problem
definition. Feasibility is to determine if it’s worth doing. Once an
acceptance problem definition has been generated, the analyst develops a
logical model of the system. A search for alternatives is analyzed carefully.
There are 3 parts in feasibility study.

1) Operational Feasibility

2) Technical Feasibility

3) Economical Feasibility

1.5.1 OPERATIONAL FEASIBILITY

Operational feasibility is the measure of how well a proposed system

solves the problems, and takes advantage of the opportunities identified
during scope definition and how it satisfies the requirements identified in
the requirements analysis phase of system development. The operational
feasibility assessment focuses on the degree to which the proposed
development projects fits in with the existing business environment and
objectives with regard to development schedule, delivery date, corporate
culture and existing business processes. To ensure success, desired
operational outcomes must be an imparted during design and development.
These include such design-dependent parameters as reliability,
maintainability, supportability, usability, reducibility, disposability,
sustainability, affordability and others. These parameters required to
consider at the early stages of design if desired operational behaviors are to
be realized. A system design and development requires appropriate and
Page No. 3
1.5 FEASIBILITY STUDY
timely application of engineering and management efforts to meet the
previously mentioned parameters. A system may serve its intended
purpose most effectively when its technical and operating characteristics
are engineered into the design. Therefore, operational feasibility is a
critical aspect of systems engineering that needs to be an integral part of
the early design phases.

Page No. 4
1.5.2 TECHNICAL FEASIBILITY

This involves questions such as whether the technology needed for the
system exists, how difficult it will be to build, and whether the firm has
enough experience using that technology. The assessment is based on
outline design of system requirements in terms of input, processes, output,
fields, programs and procedures. This can be qualified in terms of volume
of data, trends, frequency of updating inorder to give an introduction to the
technical system. The application is the fact that it has been developed on
windows XP platform and a high configuration of 1GB RAM on Intel
Pentium Dual core processor. This is technically feasible .The technical
feasibility assessment is focused on gaining an understanding of the
present technical resources of the organization and their applicability to
the expected needs of the proposed system. It is an evaluation of the
hardware and software and how it meets the need of the proposed system.

1.5.3 ECONOMICAL FEASIBILITY

Establishing the cost-effectiveness of the proposed system i.e. if the

benefits do not outweigh the costs then it is not worth going ahead. In the
fast paced world today there is a great need of online social networking
facilities. Thus the benefits of this project in the current scenario make it
economically feasible. The purpose of the economic feasibility assessment
is to determine the positive economic benefits to the organization that the
proposed system will provide. It includes quantification and identification
of all the benefits expected. This assessment typically involves a
cost/benefits analysis.

Page No. 4
1.6 Giant Chart

Page No. 5
1.7 ORGANISATION OF THE REPORT

1.7.1 INTRODUCTION

This section includes the overall view of the project i.e. the basic problem
definition and the general overview of the problem which describes the
problem in layman terms. It also specifies the software used and the
proposed solution strategy.

1.7.2 SOFTWARE REQUIREMENTS SPECIFICATION

This section includes the Software and hardware requirements for the
smooth running of the application.

1.7.3 DESIGN & PLANNING

This section consists of the Software Development Life Cycle model. It

also contains technical diagrams like the Data Flow Diagram and the
Entity Relationship diagram.

1.7.4 IMPLEMENTATION DETAILS

This section describes the different technologies used for the entire
development process of the Front-end as well as the Back-end
development of the application.

1.7.5 RESULTS AND DISCUSSION

This section has screenshots of all the implementation i.e. user interface
and their description.

1.7.6 SUMMARY AND CONCLUSION

Page No. 6
This section has screenshots of all the implementation i.e. user interface
and their description.

Page No. 7
Page No. 7
 CHAPTER 3 : DESIGN & PLANNING

3.1 Software Development Life Cycle Model

3.1.1 WATERFALL MODEL

The waterfall model was selected as the SDLC model due to the following
reasons:

Requirements were very well documented, clear and fixed. Technology

was adequately understood.
Simple and easy to understand and use. There were no ambiguous
requirements.
Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
Clearly defined stages.
Well understood milestones.Easy to arrange tasks.

Page No. 8
Page No. 9
3.2 GENERAL OVERVIEW

Page No. 9
3.3 Flow Chart

Page No.
10
3.4 ER Diagram

Page No.
11
3.5 DFD Diagram

3.5.1 Zero-Level DFD Diagram

Page No.
12
3.5.2 First-Level DFD Diagram

Page No.
13
3.5.3 Second-Level DFD Diagram

Page No.
14
 CHAPTER 4 : IMPLEMENTATION DETAILS

In this Section we will do Analysis of Technologies to use for

implementing the project.

4.1 : FRONT END

4.1.1 HTML

Hypertext Markup Language (HTML) is the standard markup language for

documents designed to be displayed in a web browser. It can be assisted by
technologies such as Cascading Style Sheets (CSS) and scripting
languages such as JavaScript. Web browsers receive HTML documents
from a web server or from local storage and render the documents into
multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the
document.

HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be
embedded into the rendered page. HTML provides a means to create
structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. HTML elements
are delineated by tags, written using angle brackets. Tags such as <img />
and <input /> directly introduce content into the page. Other tags such as
<p> surround and provide information about document text and may
include other tags as sub-elements. Browsers do not display the HTML
tags, but use them to interpret the content of the page.

HTML can embed programs written in a scripting language such as

Page No.
15
JavaScript, which affects the behavior and content of web pages. Inclusion
of CSS defines the look and layout of content. The World Wide Web
Consortium (W3C), former maintainer of the HTML and current
maintainer of the CSS standards, has encouraged the use of CSS over
explicit presentational HTML since 1997.

Page No.
16
4.1.2 JavaScript

JavaScript s a high-level, interpreted scripting language that conforms to

the ECMAScript specification. JavaScript has curly-bracket syntax,
dynamic typing, prototype-based object- orientation, and first-class
functions.Alongside HTML and CSS, JavaScript is one of the core
technologies of the World Wide Web.JavaScript enables interactive web
pages and is an essential part of web applications. The vast majority of
websites use it,and major web browsers have a dedicated JavaScript engine
to execute it.As a multi-paradigm language, JavaScript supports event-
driven, functional, and imperative (including object-oriented and
prototype-based) programming styles. It has APIs for working with text,
arrays, dates, regular expressions, and the DOM, but the language itself
does not include any I/O, such as networking, storage, or graphics
facilities. It relies upon the host environment in which it is embedded to
provide these features.

Initially only implemented client-side in web browsers, JavaScript engines

are now embedded in many other types of host software, including server-
side in web servers and databases, and in non-web programs such as word
processors and PDF software, and in runtime environments that make
JavaScript available for writing mobile and desktop applications, including
desktop widgets.

The terms Vanilla JavaScript and Vanilla JS refer to JavaScript not

extended by any frameworks or additional libraries. Scripts written in
Vanilla JS are plain JavaScript code.Google's Chrome extensions, Opera's
extensions, Apple's Safari 5 extensions, Apple's Dashboard Widgets,
Microsoft's Gadgets, Yahoo! Widgets, Google Desktop Gadgets, and
Page No.
16
4.1.2 JavaScript
Serence Klipfolio are implemented using JavaScript.

Page No.
17
4.1.3 jQuery

jQuery is a JavaScript library designed to simplify HTML DOM tree

traversal and manipulation, as well as event handling, CSS animation, and
Ajax. It is free, open-source software using the permissive MIT License.As
of May 2019, jQuery is used by 73% of the 10 million most popular
websites. Web analysis indicates that it is the most widely deployed
JavaScript library by a large margin, having 3 to 4 times more usage than
any other JavaScript library.

jQuery's syntax is designed to make it easier to navigate a document, select

DOM elements, create animations, handle events, and develop Ajax
applications. jQuery also provides capabilities for developers to create
plug-ins on top of the JavaScript library. This enables developers to create
abstractions for low-level interaction and animation, advanced effects and
high-level, themeable widgets. The modular approach to the jQuery library
allows the creation of powerful dynamic web pages and Web applications.

The set of jQuery core features—DOM element selections, traversal and

manipulation—enabled by its selector engine (named "Sizzle" from v1.3),
created a new "programming style", fusing algorithms and DOM data
structures. This style influenced the architecture of other JavaScript
frameworks like YUI v3 and Dojo, later stimulating the creation of the
standard Selectors API.Microsoft and Nokia bundle jQuery on their
platforms.

Page No.
17
4.1.4 JSON

JavaScript Object Notation (JSON) is an open-standard file format that

uses human-readable text to transmit data objects consisting of attribute–
value pairs and array data types (or any other serializable value). It is a
very common data format used for asynchronous browser–server
communication, including as a replacement for XML in some AJAX-style
systems. JSON is a language-independent data format. It was derived from
JavaScript, but many modern programming languages include code to
generate and parse JSON-format data. The official Internet media type for
JSON is application/json. JSON filenames use the extension .json.

Douglas Crockford originally specified the JSON format in the early

2000s. It was first standardized in 2013 in RFC 7158 and ECMA-404. The
latest JSON format standard was published in 2017 as RFC 8259, and
remains consistent with ECMA-404. That same year, JSON was also
standardized as ISO/IEC 21778:2017. The ECMA and ISO standards
describes only the allowed syntax, whereas the RFC covers some security
and interoperability considerations.

JSON grew out of a need for stateless, real-time server-to-browser

communication protocol without using browser plugins such as Flash or
Java applets, the dominant methods used in the early 2000s.JSON was
originally intended to be a subset of the JavaScript scripting language
(specifically, Standard ECMA-262 3rd Edition—December 1999and is
commonly used with Javascript, but it is a language-independent data
format. Code for parsing and generating JSON data is readily available in
many programming languages. JSON's website lists JSON libraries by
language.
Page No.
18
4.1.5 Css

Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language like
HTML.CSS is a cornerstone technology of the World Wide Web,
alongside HTML and JavaScript.CSS is designed to enable the separation
of presentation and content, including layout, colors, and fonts.This
separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple
web pages to share formatting by specifying the relevant CSS in a separate
.css file, and reduce complexity and repetition in the structural content.

CSS information can be provided from various sources. These sources can
be the web browser, the user and the author. The information from the
author can be further classified into inline, media type, importance,
selector specificity, rule order, inheritance and property definition. CSS
style information can be in a separate document or it can be embedded into
an HTML document. Multiple style sheets can be imported. Different
styles can be applied depending on the output device being used; for
example, the screen version can be quite different from the printed
version, so that authors can tailor the presentation appropriately for each
medium.The style sheet with the highest priority controls the content
display. Declarations not set in the highest priority source are passed on to
a source of lower priority, such as the user agent style. The process is
called cascading.

One of the goals of CSS is to allow users greater control over presentation.
Someone who finds red italic headings difficult to read may apply a
different style sheet. Depending on the browser and the web site, a user
may choose from various style sheets provided by the designers, or may
Page No.
19
4.1.5 Css
remove all added styles and view the site using the browser's default
styling, or may override just the red italic heading style without altering
other attributes.

Page No.
20
4.1.6 Bootstrap

Bootstrap is a free and open-source CSS framework directed at responsive,

mobile-first front-end web development. It contains CSS- and (optionally)
JavaScript-based design templates for typography, forms, buttons,
navigation and other interface components.Bootstrap is the third- most-
starred project on GitHub, with more than 135,000 stars, behind only
freeCodeCamp (almost 305,000 stars) and marginally behind Vue.js
framework.According to Alexa Rank, Bootstrap getbootstrap.com is in the
top-2000 in US while vuejs.org is in top-7000 in US.

Bootstrap is a web framework that focuses on simplifying the development

of informative web pages (as opposed to web apps). The primary purpose
of adding it to a web project is to apply Bootstrap's choices of color, size,
font and layout to that project. As such, the primary factor is whether the
developers in charge find those choices to their liking. Once added to a
project, Bootstrap provides basic style definitions for all HTML elements.
The result is a uniform appearance for prose, tables and form elements
across web browsers. In addition, developers can take advantage of CSS
classes defined in Bootstrap to further customize the appearance of their
contents. For example, Bootstrap has provisioned for light- and dark-
colored tables, page headings, more prominent pull quotes, and text with a
highlight.

Bootstrap is a web framework that focuses on simplifying the development

of informative web pages (as opposed to web apps). The primary purpose
of adding it to a web project is to apply Bootstrap's choices of color, size,
font and layout to that project. As such, the primary factor is whether the
developers in charge find those choices to their liking. Once added to a
Page No.
20
4.1.6 Bootstrap
project, Bootstrap provides basic style definitions for all HTML elements.
The result is a uniform appearance for prose, tables and form elements
across web browsers. In addition, developers can take advantage of CSS
classes defined in Bootstrap to further customize the appearance of their
contents. For example, Bootstrap has provisioned for light- and dark-
colored tables, page headings, more prominent pull quotes, and text with a
highlight.

Page No.
21
 CHAPTER 5 : TESTING AND IMPLEMENTATION

The term implementation has different meanings ranging from the

conversation of a basic application to a complete replacement of a
computer system. The procedures however, are virtually the same.
Implementation includes all those activities that take place to convert from
old system to new. The new system may be totally new replacing an
existing manual or automated system or it may be major modification to
an existing system. The method of implementation and time scale to be
adopted is found out initially. Proper implementation is essential to
provide a reliable system to meet organization requirement.

5.1 : UNIT TESTING

5.1.1 Introduction

In computer programming, unit testing is a software testing method by

which individual units of source code, sets of one or more computer
program modules together with associated control data, usage procedures,
and operating procedures, are tested to determine whether they are fit for
use. Intuitively, one can view a unit as the smallest testable part of
an application. In procedural programming, a unit could be an entire
module, but it is more commonly an individual function or procedure. In
object-oriented programming, a unit is often an entire interface, such as a
class, but could be an individual method. Unit tests are short code
fragments created by programmers or occasionally by white box testers
during the development process. It forms the basis for component testing.
Ideally, each test case is independent from the others. Substitutes such as
method stubs, mock objects, fakes, and test harnesses can be used to assist
testing a module in isolation. Unit tests are typically written and run by
Page No.
21
software developers to ensure that code meets its design and behaves as
intended.

Page No.
22
5.1.2 Benifits

The goal of unit testing is to isolate each part of the program and show that
the individual parts are correct. A unit test provides a strict, written
contract that the piece of code must satisfy. As a result, it affords several
benefits.

1) Find problems early : Unit testing finds problems early in the

development cycle. In test- driven development (TDD), which is
frequently used in both extreme programming and scrum, unit tests are
created before the code itself is written. When the tests pass, that code is
considered complete. The same unit tests are run against that function
frequently as the larger code base is developed either as the code is
changed or via an automated process with the build. If the unit tests fail, it
is considered to be a bug either in the changed code or the tests
themselves. The unit tests then allow the location of the fault or failure to
be easily traced. Since the unit tests alert the development team of the
problem before handing the code off to testers or clients, it is still early in
the development process.

2 ) Facilitates Change : Unit testing allows the programmer to refactor

code or upgrade system libraries at a later date, and make sure the module
still works correctly (e.g., in regression testing). The procedure is to write
test cases for all functions and methods so that whenever a change causes a
fault, it can be quickly identified. Unit tests detect changes which may
break a design contract.

3 ) Simplifies Integration : Unit testing may reduce uncertainty in the

units themselves and can be used in a bottom-up testing style approach. By
testing the parts of a program first and then testing the sum of its parts,
Page No.
22
5.1.2 Benifits
integration testing becomes much easier.

4 ) Documentation : Unit testing provides a sort of living documentation

of the system. Developers looking to learn what functionality is provided
by a unit, and how to use it, can look at the unit tests to gain a basic
understanding of the unit's interface (API).Unit test cases embody
characteristics that are critical to the success of the unit. These
characteristics can indicate appropriate/inappropriate use of a unit as well
as negative behaviors that are to be trapped by the unit.

Page No.
23
5.2 : INTEGRATION TESTING

Integration testing (sometimes called integration and testing,

abbreviated I&T) is the phase in software testing in which individual
software modules are combined and tested as a group. It occurs after unit
testing and before validation testing. Integration testing takes as its
input modules that have been unit tested, groups them in larger aggregates,
applies tests defined in an integration test plan to those aggregates, and
delivers as its output the integrated system ready for system testing.

5.2.1 Purpose

The purpose of integration testing is to verify functional,

performance, and reliability requirements placed on major design items.
These "design items", i.e., assemblages (or groups of units), are exercised
through their interfaces using black-box testing, success and error cases
being simulated via appropriate parameter and data inputs. Simulated
usage of shared data areas and inter-process communication is tested and
individual subsystems are exercised through their input interface. Test
cases are constructed to test whether all the components within
assemblages interact correctly, for example across procedure calls or
process activations, and this is done after testing individual modules, i.e.,
unit testing. The overall idea is a "building block" approach, in which
verified assemblages are added to a verified base which is then used to
support the integration testing of further assemblages.Software integration
testing is performed according to the software development life cycle
(SDLC) after module and functional tests. The cross-dependencies for
software integration testing are: schedule for integration testing, strategy
and selection of the tools used for integration, define the cyclomatical
complexity of the software and software architecture, reusability of
Page No.
23
5.2 : INTEGRATION TESTING
modules and life-cycle and versioning management.Some different types
of integration testing are big-bang, top-down, and bottom-up, mixed
(sandwich) and risky-hardest. Other Integration Patterns[2] are:
collaboration integration, backbone integration, layer integration, client-
server integration, distributed services integration and high-frequency
integration.

Page No.
24
5.2.1.1 Big Bang

In the big-bang approach, most of the developed modules are coupled

together to form a complete software system or major part of the system
and then used for integration testing. This method is very effective for
saving time in the integration testing process. However, if the test cases
and their results are not recorded properly, the entire integration process
will be more complicated and may prevent the testing team from achieving
the goal of integration testing.A type of big-bang integration testing is
called "usage model testing" which can be used in both software and
hardware integration testing. The basis behind this type of integration
testing is to run user-like workloads in integrated user-like environments.
In doing the testing in this manner, the environment is proofed, while the
individual components are proofed indirectly through their use. Usage
Model testing takes an optimistic approach to testing, because it expects to
have few problems with the individual components. The strategy relies
heavily on the component developers to do the isolated unit testing for
their product. The goal of the strategy is to avoid redoing the testing done
by the developers, and instead flesh-out problems caused by the interaction
of the components in the environment.

5.2.1.2 Top-down And Bottom-up

Bottom-up testing is an approach to integrated testing where the lowest

level components are tested first, then used to facilitate the testing of
higher level components. The process is repeated until the component at
the top of the hierarchy is tested.All the bottom or low-level modules,
procedures or functions are integrated and then tested. After the integration
testing of lower level integrated modules, the next level of modules will be
formed and can be used for integration testing. This approach is helpful
Page No.
24
5.2.1.1 Big Bang
only when all or most of the modules of the same development level are
ready. This method also helps to determine the levels of software
developed and makes it easier to report testing progress in the form of a
percentage.Top-down testing is an approach to integrated testing where the
top integrated modules are tested and the branch of the module is tested
step by step until the end of the related module.Sandwich testing is an
approach to combine top down testing with bottom up testing.

Page No.
25
5.3 : SOFTWARE VERIFICATION AND VALIDATION

5.3.1 Introduction

In software project management, software testing, and software

engineering, verification and validation (V&V) is the process of checking
that a software system meets specifications and that it fulfills its intended
purpose. It may also be referred to as software quality control. It is
normally the responsibility of software testers as part of the software
development lifecycle. Validation checks that the product design satisfies
or fits the intended use (high-level checking), i.e., the software meets the
user requirements.This is done through dynamic testing and other forms of
review.Verification and validation are not the same thing, although
they are often confused. Boehm succinctly expressed the difference
between

Validation : Are we building the right product? Verification : Are we

building the product right?

According to the Capability Maturity Model (CMMI-SW v1.1)

Software Verification: The process of evaluating software to determine

whether the products of a given development phase satisfy the conditions
imposed at the start of that phase.

Software Validation: The process of evaluating software during or at the

end of the development process to determine whether it satisfies specified
requirements.

In other words, software verification is ensuring that the product has been
built according to the requirements and design specifications, while
Page No.
25
software validation ensures that the product meets the user's needs, and
that the specifications were correct in the first place. Software verification
ensures that "you built it right". Software validation ensures that "you built
the right thing". Software validation confirms that the product, as provided,
will fulfill its intended use.

Page No.
26
From Testing Perspective

Fault – wrong or missing function in the code.

Failure – the manifestation of a fault during execution.
Malfunction – according to its specification the system does not meet its
specified functionality

Both verification and validation are related to the concepts of quality and
of software quality assurance. By themselves, verification and validation
do not guarantee software quality; planning, traceability, configuration
management and other aspects of software engineering are required.Within
the modeling and simulation (M&S) community, the definitions of
verification, validation and accreditation are similar:

M&S Verification is the process of determining that a ⦁ computer model,

simulation, or federation of models and simulations implementations and
their associated data accurately represent the developer's conceptual
description and specifications.
M&S Validation is the process of determining the degree to which a
model, simulation, or federation of models and simulations, and their
associated data are accurate representations of the real world from the
perspective of the intended use(s).

Page No.
26
5.3.2 Classification of Methods

In mission-critical software systems, where flawless performance is

absolutely necessary, formal methods may be used to ensure the correct
operation of a system. However, often for non- mission-critical software
systems, formal methods prove to be very costly and an alternative method
of software V&V must be sought out. In such cases, syntactic methods are
often used.

5.3.3 Test Cases

A test case is a tool used in the process. Test cases may be prepared for
software verification and software validation to determine if the product
was built according to the requirements of the user. Other methods, such as
reviews, may be used early in the life cycle to provide for software
validation.

Page No.
27
5.4 Black-Box Testing

Black-box testing is a method of software testing that examines the

functionality of an application without peering into its internal structures
or workings.

5.4.1 Test Procedures

Specific knowledge of the application's code/internal structure and

programming knowledge in general is not required. The tester is aware of
what the software is supposed to do but is not aware of how it does it. For
instance, the tester is aware that a particular input returns a certain,
invariable output but is not aware of how the software produces the output
in the first place.

5.4.2 Test Cases

Test cases are built around specifications and requirements, i.e., what the
application is supposed to do. Test cases are generally derived from
external descriptions of the software, including specifications,
requirements and design parameters. Although the tests used are
primarily functional in nature, non-functional tests may also be used. The
test designer selects both valid and invalid inputs and determines the
correct output, often with the help of an oracle or a previous result
that is known to be good, without any knowledge of the test object's
internal structure.

Page No.
28
5.5 : White-Box Testing

White-box testing (also known as clear box testing, glass box testing,
transparent box testing, and structural testing) is a method of testing
software that tests internal structures or workings of an application, as
opposed to its functionality (i.e. black-box testing). In white-box testing an
internal perspective of the system, as well as programming skills, are used
to design test cases. The tester chooses inputs to exercise paths through the
code and determine the appropriate outputs. This is analogous to testing
nodes in a circuit, e.g. in-circuit testing (ICT). White-box testing can be
applied at the unit, integration and system levels of the software testing
process. Although traditional testers tended to think of white-box testing as
being done at the unit level, it is used for integration and system testing
more frequently today. It can test paths within a unit, paths between units
during integration, and between subsystems during a system–level test.
Though this method of test design can uncover many errors or problems, it
has the potential to miss unimplemented parts of the specification or
missing requirements.

5.5.1 Levels

1 ) Unit testing : White-box testing is done during unit testing to ensure

that the code is working as intended, before any integration happens with
previously tested code. White-box testing during unit testing catches any
defects early on and aids in any defects that happen later on after the code
is integrated with the rest of the application and therefore prevents any
type of errors later on.

2 ) Integration testing : White-box testing at this level are written to test

the interactions of each interface with each other. The Unit level testing
Page No.
29
5.5 : White-Box Testing
made sure that each code was tested and working accordingly in an
isolated environment and integration examines the correctness of the
behaviour in an open environment through the use of white-box testing for
any interactions of interfaces that are known to the programmer.

3 ) Regression testing : White-box testing during regression testing is

the use of recycled white- box test cases at the unit and integration testing
levels.

Page No.
30
5.5.2 Procedures

White-box testing's basic procedures involves the tester having a deep

level of understanding of the source code being tested. The programmer
must have a deep understanding of the application to know what kinds of
test cases to create so that every visible path is exercised for testing. Once
the source code is understood then the source code can be analyzed for test
cases to be created. These are the three basic steps that white-box testing
takes in order to create test cases:

Input involves different types of requirements, functional specifications,

detailed designing of documents, proper source code, security
specifications. This is the preparation stage of white-box testing to layout
all of the basic information.
Processing involves performing risk analysis to guide whole testing
process, proper test plan, execute test cases and communicate results. This
is the phase of building test cases to make sure they thoroughly test the
application the given results are recorded accordingly.
Output involves preparing final report that encompasses all of the above
preparations and results.

Page No.
30
5.6 : SYSTEM TESTING

System testing of software or hardware is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified
requirements. System testing falls within the scope of black-box testing,
and as such, should require no knowledge of the inner design of the code
or logic. As a rule, system testing takes, as its input, all of the "integrated"
software components that have passed integration testing and also the
software system itself integrated with any applicable hardware system(s).
The purpose of integration testing is to detect any inconsistencies between
the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a
more limited type of testing; it seeks to detect defects both within the
"inter-assemblages" and also within the system as a whole.

System testing is performed on the entire system in the context of a

Functional Requirement Specification(s) (FRS) and/or a System
Requirement Specification (SRS). System testing tests not only the design,
but also the behavior and even the believed expectations of the customer. It
is also intended to test up to and beyond the bounds defined in the
software/hardware requirements specification(s).

Page No.
31
 CHAPTER 6 : RESULTS

6.1 Css Code

Page No.
32
6.2 User Login

Page No.
33
6.3 Admin Login

Page No.
34
 CHAPTER 7 : ADVANTAGES

Helps cricket clubs to register members online.

Allows cricket clubs to allow users to book ground online. Automates the
working of cricket club activities.
Helps cricket clubs to register members online.

Page No.
35
 CHAPTER 8 : CONCLUSION

We propose to build a software system that can efficiently handle and

manage various activities of a cricket club and all these activities will be
happening under the supervision of the administrator. The administrator
account controls everything.

Page No.
36
 CHAPTER 8 : BIBLIOGRAPHY

https://www.javatpoint.com https://www.w3schools.com https://html.com

Page No.
37