A Scorecasting System for Cricket

This application claims benefit of Indian provisional patent application number IN 724/CHE/2008, filed on March 25, 2008, the entire contents of which are incorporated herein by reference. 1. INTRODUCTION

This document provides product specifications for a web-based social networking application which would provide a platform for showcasing various kinds of focusing on around the game of CRICKET. 1.1 About Cricket Cricket is a bat-and-ball sport contested by two teams - batting team & fielding (bowling) team -, usually of eleven players each. A cricket match is played on a grass field, roughly oval in shape, in the centre of which is a flat strip of ground 22.5 yards long, called a cricket pitch. Three wickets, usually made of wood, are placed at each end of the pitch. The bowler, a player from the fielding team, bowls a hard, fist-sized leather ball from the vicinity of one wicket towards the other. The ball usually bounces once before reaching the batsman, a player from the opposing team. In defense of the wicket, the batsman plays the ball with a wooden cricket bat. Meanwhile, the other members of the fielding team stand in various positions around the field as fielders, players who retrieve the ball in an effort to stop the batsman scoring runs, and if possible to get him or her out. The batsman — if he or she does not get out — may run between the wickets, exchanging ends with a second batsman (the "non-striker"), who has been waiting near the bowler's wicket. Each completed exchange of ends

Cricket has been an established team sport for hundreds of years and is the second most popular sport in the world. More than 150 countries are affiliated to the International Cricket Council, cricket's international governing body. The sport's modern form originated in England, and is most popular in the present and former members of the Commonwealth. In the countries of South Asia, including India, Pakistan, Bangladesh and Sri Lanka, cricket is the most popular sport. It is also a major sport in England, Australia, New Zealand, South Africa, Zimbabwe and the English-speaking countries of the Caribbean, which are collectively known in cricketing parlance as the West Indies. Many countries also have well-established amateur club competitions, including the Netherlands, Kenya, Nepal and Argentina. 1.2 Purpose - Addressing the market need

Cricket, as a game has been gaining immense popularity across the world. However, the media attention has been limited to international matches and to a much lesser level to representative cricket played between regions in the major cricket playing countries.

While there has been a lot of passion for the game in the Indian sub-continent, with numerous matches being played, including in by-lanes and residential neighborhoods, there has been a total lack of availability of publishing and broadcasting platforms for the community as a whole. This disclosure teaches a system and techniques that are targeted at providing a web-centric and mobile-supported platform for all cricket players, cricket clubs, teams, coaches, umpires and also the fans of the game to collaborate with each other and to broadcast any cricket related content, including ball-by-ball detailed live cricket scores of their matches to a global audience.

1.3 Vision

The vision for this disclosure is to provide equal opportunities to all cricket lovers and stake holders to create and broadcast their own cricket- related content, including ball-by-ball detailed live cricket scores to a global audience.

1.4 Objectives

• To build a web-centric, mobile supported Web 2.0 platform for the global cricketing community, which will be driven almost entirely by user-generated content. » To serve as an active networking tool for players, teams, coaches, umpires and ordinary fans to interact with each other. SUMMARY

To meet some of the above objectives there is a provided a scorecasting system to record scores in a cricket match comprising a Scorecaster, wherein the Scorecaster comprises a Calculator Interface to record a score of the cricket match.

An aspect of the disclosed teachings is a method of broadcasting a score for a cricket match comprising recording the score for the cricket match on a Calculator Interface in a Scorecaster, uploading the score from the Scorecaster onto a Webpage, displaying the score on the Webpage.

BRIEF DESCRIPTION OF THE DRAWINGS

The above objectives and advantages of the disclosed teachings will become more apparent by describing in detail preferred embodiments thereof with reference to the attached drawings in which:

Figure 1 is a top-level block diagram showing various components in an exemplary embodiment of the disclosed system.

Figure 2 shows a top-level flow diagram that depicts an example implementation of some of the techniques according to the disclosed teachings. Figure 3 shows an example implementation of the user registration process.

Figure 4 shows an example user-interface of a system embodying the disclosed teachings including a scorecaster.

Figure 5 a-f show an example implementation of a scorecaster and a scorecasting method according to the disclosed teachings. Figure 6 shows a example implementation of a match setup according to the disclosed teachings.

Figure 7 a-b shows an example implementation of setting up and conducting a tournament.

Figure 8 shows an example of the system with the scorescaster afeter performing a certain operation.

Figure 9 shows an example of the system with the scorescaster afeter performing another operation.

DETAILED DESCRIPTION

1.5 References

• The disclosure and the accompanying figures provide: o Block Diagram - this would provide a high level view of the system

o Top Level Data Flow Diagram - this provides a view of key data interaction and entities involved o Flow Charts - this provides logical insight to key processes in the system 2. FUNCTIONAL OVERVIEW

Underlying business case for the disclosed teachings is rooted on the fact that the large following enjoyed by the cricket in the Indian sub-continent and elsewhere is portrayed in the media through international cricket.

It fails to bring to the fore numerous tournaments or matches being played across cities, towns, villages, schools etc.. Similarly, there are no public spaces where a stake holder - be it a player, umpire, coach, commentator or an expert - can broadcast himself/ herself.

The disclosed teachings are steps towards linking all the lovers of the game and to help them participate in a 'global' way to provide better visibility.

3. FUNCTIONAL FEATURES FOR THE EXEMPLARY IMPLEMENTATION

Main list of features envisaged for phase-1 is provided in Section 3.3 3.1 High Level Flow: • The community will have 2 kinds of participants - registered members and casual visitors. • All registered members are the 'Creators' of their own virtual SPACES (My

Turf) and can also create content. Casual Visitors can browse through content created by registered members.

• There will be a simple 'Sign up' procedure to register as a member of the community and as part of the process, confirmation through the e-mail is mandatory.

• A registered user will utilize his/her allocated space to; o Describe himself/ herself or publish a salutary message o Categorize oneself as a fan/player/umpire/coach/scorer/administrator/ sports promoter/ talent hunter/ commentator/journalist with the ability to choose multiple options o Depending on the options chosen above, provide more detailed promotional information about oneself. o Post detailed live scores using the SCORING ENGINE - ScoreCaster o Create, own and manage GROUPS which will have SPACES as members. o Define Rules for the membership of these GROUP SPACES, including privileges of members and the exposure of the spaces ( Public or Private)

• Link the group to any other groups or predefined categories

• Create or Provide options to create: o Teams o Tournaments o Matches o Score sheets o Pictures/Videos o Etc.

• Broadly classifying, there will be 2 categories of contents viz. Public and Private. 'Public' is available for all visitors to the community and 'Private' will be available based on the rules defined by the creator.

• This will be augmented by tools like ScoreCaster, Blogs, User rating of contents, Popularity charts etc.

• In order to upload scorecards or live data, it is necessary to mention a few essential details of the particular game like Venue, Name of Teams, Players, Umpires etc.

• No restriction is being put on creating 'virtual' spaces for matches. This means that the matches could be taking place between teams which may not have a profile already defined in this site. Otherwise, it is not mandatory to register teams or players for uploading match information.

• All registered members of the community have equal rights and there is no limit on the contents they can put into their own spaces. • There will be multiple CHANNELS available to feed live scores ( Say, CHl

TO CH99)

• Scorers may opt to feed their live scorecards through a designated CHANNEL.

• These Channels will be allotted based on bookings for specific time slots.

• This would enable a match to be available with an easy URL reference eg: Match between Cordiant Sports Foundation and Taj Residency available live between 9:30 am and 5:00 pm on Nov 20, 2007 at , for example, http://ch23.cricketmaidan.in

• Exclusive links to these channels will provide ease of reference.

• Typical User Scenarios:

Scenario- 1 (Registered member) o When signing in, the user will be guided to his/her allocated space, called 'My Turf, as defined by them. o This page is user specific and cannot be viewed by others. Scenario-2 (Scoring) o User needs to record the score for a match. o First step is registration to the community. o Once the registration is complete, the user needs to set up 'My Turf. o Once the setting up is complete, the user is taken to 'My Turf. o He/she could choose the link 'Create New Match' or 'Upload

Scorecards' to record the scores. o If no match has been scheduled, it should be scheduled before proceeding to record the scores. o Once the match has been set up with relevant details like Venue, Date, Place, Name of Teams, Players, Umpires etc., the scoring can be done using the ScoreCaster tool either in on-line mode or off-line mode. o A unique reference number is provided when each time a match is scheduled. o The user can choose to upload scorecards in periodic intervals or can type in ball-by-ball account as it happens or uses a video camera interface to broadcast it live. o After scheduling the match, the user can choose to publish it live through one of the dedicated 'Channels' after booking the appropriate time slot. This would enable him/her to provide a URL that would be easy to refer.

o The above scenario assumes that the user has internet connectivity during the course of the match.

Scenario-3 (Scoring) o Same as above but without internet access. o For such people, a downloadable off-line application would facilitate capturing of the same kind of match information as in scenario- 1. o Once the match is over and the person is back to a place where he/she can access the internet, this client application would upload the captured information on to the internet site. o The match reference number will be generated for this match when the information has been successfully uploaded.

Scenario-4(Scoring) o The match information can be uploaded using a PDA or mobile phone.

Scenario-5(Casual Visitor) o A casual visitor will be able to view any of the matches going on at that instant. o He/she can also view any content which is available publicly.

• What kind of information is available to people of this community? o Detailed information about matches played at various levels across the globe.

• How this information could be used? o Possibilities are enormous. o It provides an even platform for all active cricket lovers to showcase their contribution in front of the global community.

o This could act as a showcase of untapped talent available across geographical regions. 3.2 General Navigation:

1. Person signing up. 2. Email confirmation - clicks on the link provided in the email to complete registration.

3. Opens the 'Home' page.

4. This displays list of live matches taking place at that moment.

5. Other options available are: D Set up Matches

D ScoreCasting D Tournaments D Networking

6. Setting up 'My Turf : D 'My Turf Settings

• Cricket Profile

• Preferences URL

• Location D Groups

• Create Groups

• My Groups

D Schedule Matches

• Set up a Match

• My Matches D Set up Tournaments 7. Complete setting up.

8. Display the user's 'My Turf.

9. Schedule a match providing essential details.

10. Record scores using ScoreCaster for the match or broadcast the match live through a channel. 3.3 Main features for the Exemplary Implementation Registration for Users

• Facilities for registered users: o Set up a Match o Upload Score cards live or post match o Upload live Video / Photos o Set up Tournaments & Fixtures o Designate official scorers for a match or tournament o Create and maintain own special interest Groups o Publish own Cricket profile and related interests o Provide platform for networking of various individuals having interests in any aspects of the game o Post public and private messages

• All users will be able to view any match and related contents

• Search facility

4. SCHEMATIC REPRESENTATION

Following sections provide a schematic representation of an Exemplary Implementation through different levels. The block diagram gives a snapshot of the whole system; top level data flow diagram provides insight into the processes, entities and how they interact; flow charts provide exploded view of key processes.

5. SNAPSHOT - BLOCK DIAGRAM

Core objective is to empower the people to upload / publish all contents related to cricket matches which interest them. The contents could be score cards, photographs, videos etc. This could be uploaded live or post event depending on the user convenience. It also provides an exclusive user networking platform for the user community involved in the game.

Only restriction enforced in utilizing these facilities is a simple user registration process to ensure that contributors to the community are genuine lovers of the game. However there is no restriction in viewing the matches being webcasted through the disclosed system and is available to any internet user.

The block diagram given below represents key features of the system. As given in the diagram, all contents in the disclosed system are essentially contributed by its (registered) users which are enclosed in the large box with a given title for example Cricket Maidan. The contents can be created through various modes. Any internet user (symbolized by the smaller box with title 'Internet Users') who visits the disclosed system can view all match related contents like live Score cards, videos, photos etc.. One of the distinguishing features is the self contained tool - ScoreCaster - which would be used for recording scores through a simple, calculator like interface.

Following pages provide a Top Level Data Flow Diagram providing key data exchanges between various entities and processes in the system. Further, it would provide detailed flow of key processes involved in the system through flow charts. 6.1 Figure 1 Following sections provide brief notes on the blocks featuring in Figure 1

Figure 1 :

1. User Registration

In order to leverage the power of the disclosed system, any person is required to go through a simple registration procedure where some essential identification data needs to be provided. As a verification procedure, the user will receive an email from the disclosed system after the information has been saved and a click on the link provided in the mail will complete the registration procedure.

Only registered users have the privilege to upload any contents - Score cards, set up matches, photos, videos etc. - to the disclosed system. Unregistered users can only view the contents of the disclosed system.

2. Set Up Matches

Setting up a match on the disclosed system is a prerequisite for uploading the score card using the ScoreCaster tool. This captures the essential information related to a typical cricket match. They are: • Match Venue

Country City

• Type of Match

• Dates From & To

• No. of Innings

• Teams Information

• Name of Umpires

• No. of sessions Any registered user can set up a match.

3. Set Up Tournaments

The disclosed system also facilitates setting up of tournaments. Tournaments generally have multiple rounds of matches being played between various teams. This feature allows a user to define fixtures for the whole tournament. Fixtures would define Date & time of matches, Venue, Location and Names of teams.

Any registered user can set up a tournament.

4. Create Teams

It is important to define the players before the commencement of a match and this feature is intended facilitate it. It captures essential data about teams like Name of the Team, Name of the players, their roles (Batsman/Bowler/Wicket Keeper), Style of batting, Style of bowling, Name of the Captain, Name of the manager, Name of the coach and Name of the Physio.

5. Match in progress

This block refers to sources of live contents on the disclosed system. The main live event on the disclosed system is a cricket match and key events associated with a match are real time score card, videos and photographs.

a. ScoreCaster

ScoreCaster is the software device provided by the disclosed system to record scores of a cricket match. It provides a simple, easy to use, user interface to record the scores unlike the conventional complex scoring sheet used for cricket matches. ScoreCaster has online and off-line versions. Essentially it provides a calculator like interface to record the runs scored, wickets to fall etc. Detailed flow of ScoreCaster is provided in latter sections of this document.

Any registered user can record the scores for a match. b. Digi Cams Digi Cams or digital cameras are the sources for uploading live videos or photographs to the disclosed system. They can be connected to a portable computer and the content can be uploaded. All uploaded contents can be linked to a particular match and any user can view this on the disclosed system.

Any registered user can record the scores for a match. c. Mobile Devices

Mobile devices like cellular phones, iPods and PDAs can be used for uploading scores through the ScoreCaster interface installed in them. Some of these devices are also equipped with cameras which can be used for uploading pictures.

Any registered user can upload contents using a mobile device. 5. Data

This block refers to the typical data contributed by registered users which gets stored in the disclosed system. a. Tournament Fixtures b. Matches - Live, Scheduled or Completed

c. Teams - team created by users d. Messages - messages exchanged between the users e. Videos f. Photos 7. Live Contents

This is the repository for various kinds of live data which is available for viewing by all the users of the disclosed system. Main types of live data are: • Score cards

Photographs • Videos

7. Stored Contents

Stored contents mainly have results of completed matches with score cards, video footages, photographs, upcoming tournament fixtures etc.

8. Internet Users This block refers to all the individuals who visit web site to view the events.

This is typically an interface provided by any internet browser.

As indicated in the block diagram, block-7 & block-8 provides interface to view the contents stored in block-5 & block-6. 10. User Networking As the users belong to a genuine, sport loving community, mutual interaction among the community members are encouraged and this block refers to a networking platform for the registered users to share ideas, seek assistance, provide mentoring and join with people with common specific interests with respect to the game.

7. TOP LEVEL DATA FLOW DIAGRAM

The Top Level Data Flow Diagram helps in understanding the key interactions and data exchanges between various entities and processes. Following paragraphs provides an overview of the key processes involved in the system. User Registration: A typical process begins when a User provides data for registration to the disclosed system. Top left hand side corner of the diagram represents this scenario. An authentic email ID is required for registration purposes. The disclosed system uses this email ID to send a verification mail to the user for acknowledgement. Once the registration is successful, the User (who is now a member of the disclosed system) can set up a profile which would best represent the person's interests, preferences etc. This private space is known as 'My Turf in the disclosed system. Further, the person now has the ability to set up new Matches, Tournaments, use ScoreCaster, upload Videos, photos etc. Match Setup: In order to set up a new match, the registered user sends in essential information attributed to a match like Venue, Date, Time of play, Number of Innings / Overs, Type of Match, details of both Teams, Umpires etc. The system would generate a unique reference ID for each match. This reference ID could be used to link any content being uploaded to the disclosed system. Tournament Setup: Similarly, some of the essential data required to set up a tournament are Name of the Tournament, Sponsor, Period, Fixtures, Number of Pools(Groups), type of matches, Number of rounds, Match details etc. Each tournament will have a unique reference ID generated by the system.

ScoreCaster: This is a tool used for recording the scores during a match. It fetches essential data from the match information and provides a versatile calculator like interface to record the scores for the particular match. This could be live uploads or periodical uploads. Simultaneously, live videos or photos of the match also could be uploaded by referencing the match in progress.

At any given point of time, all visitors to the disclosed system will be able to view live matches or completed matches or upcoming matches / tournament fixtures.

Uploads: The system provides registered users facilities for uploading other contents like photographs, videos, articles etc. 7.1 Figure 2

8. USER REGISTRATION - PROCESS FLOW

A user will need to register as a disclosed system member to use all features available in the disclosed system. Non registered members can only view publicly available content. Figure 3 in the following page provides the process flow for 'User Registration'.

• 'User Registration' process will start when a user clicks on 'Sign Up' and it captures essential details of the person like (indicated by block '3.01 ' in Figure

3): o First Name o Last Name o Email ID o Password o Re-enter Password o Gender

O Date of Birth

O Country

O State

O City

O Postal Code

• A Security Check is done to ensure that the registration is done by a human and is not computer generated. This is achieved by requesting the user to type in a few characters as displayed on the specific area (indicated by blocks '3.02' to '3.04' in Figure 3). • Once the security check is passed, user should read the 'Terms of Service' and agree before he registers with the disclosed system (indicated by blocks '3.05' & '3.06' in Figure 3).

• Once the user accepts the terms, a confirmation email is sent to the email id (indicated by block '3.07' in Figure 3). A valid email id is mandatory to register with the disclosed system.

• The user needs to acknowledge by clicking on the link provided in the email to complete the registration process (indicated by blocks '3.08' to '3.10' in Figure 3).

8.1 Figure 3 9. SCORECASTER - PROCESS FLOW

ScoreCaster is a tool for recording scores for matches. Its uniqueness is the familiar user interface in the form of a 'calculator' for this purpose. This makes use of combinations of 16, programmable, buttons to record scores for a game. A compact display area is provided above the buttons to display the result of each click

of these buttons. The keypad (buttons) is dynamic and functions of the buttons change based on the scenarios during the course of a match. Though the user interface is a familiar one for most of the people, it is unique in its usage for this kind of purposes. The tool has an online version and a downloadable off-line version. Following paragraphs show how the ScoreCaster can be used to record scores in a cricket match. Features of this tool can be extended to any game with minor modifications.

The picture shown below provides a view of Standard key configuration of ScoreCaster used in a cricket match: 9.1 Figure 4

Following table gives the functions of keys used in the standard layout of ScoreCaster:

Flow charts given below provide logical overview of ScoreCaster functionality with respect to recording of Cricket scores. 9.2 Figure 5 9.3 How the ScoreCaster works?

A prerequisite for using ScoreCaster to do scoring is that a match should have been set up (scheduled) in the system. This could be done through 'Match Setup' process.

The user may select any of the matches scheduled by him/her for Scorecasting. The ScoreCaster is functionally divided into the following sections on the screen:

• Team Batting - list of players for the batting team is displayed or can be selected

• Team Bowling — list of players for the bowling team is displayed or can be selected • Match Control — This part provides fields / buttons to select Striker, Non- striker, Bowler, Toss, Start and Stop match.

• Scoring Calculator - This is the interface used for doing the actual scoring during the match.

• Current Match Report - This section displays the scorecard as it would appear for any other user who looks at the scorecard.

Following sections provide indicative flow as given in the logical flow chart shown above and also covers typical steps involved in scoring for a cricket match:

• Select a scheduled match (indicated by block '5.01 ' in Figure 5).

• User should click the 'Toss' button to indicate the tossing event (indicated by block '5.02' in Figure 5).

• Then the user should select the team which won the toss and mention if the team has elected for batting or bowling (indicated by block '5.03' in Figure 5).

• Based on this selection, respective players of the teams will be displayed under the sections 'Batting' and 'Bowling' (indicated by block '5.04' in Figure 5).

• The user should then select 'Striker' and 'Non Striker' from the batting team and the 'Bowler' from the bowling team (indicated by blocks '5.05' & '5.06' in Figure 5).

• Commencement of the game or start of new session is indicated by clicking the 'Start match' button in 'Match Control' section (indicated by blocks '5.07'

& '5.08' in Figure 5).

• Depending on the result of each delivery, different actions are recorded using ScoreCaster.

• If a batsman is ruled 'Out' by the umpire, 'W button on the 'scoring calculator' is pressed to indicate fall of a wicket (indicated by blocks '5.09' &

'5.10' in Figure 5).

• This triggers a sub-process, 'Fall of a Wicket', which provides options to capture details of the manner in which the batsman got out (indicated by block

'5.1 1 ' in Figure 5). Flow of the sub-process is given below in the table under section 9.3.1.

9.3.1 Fall of a Wicket

The table below provides the detailed functions of the keys used to define fall of a wicket during the match and the image in Figure 8 below shows the changed configuration of buttons on the calculator interface:

• The system will check if it is the end of an innings at the fall of each wicket (indicated by block '5.12' in Figure 5).

If the umpire, signals the runs taken as extras, 'Ex' button on the 'scoring calculator' is pressed to indicate extra runs (indicated by blocks '5.13' & '5.14' in Figure 5).

• This triggers the sub-process, 'Extras', which provides for possible combinations to account for extra runs (indicated by block '5.15' in Figure 5). Flow of the sub-process is given below in the table under section 9.3.2.

9.3.2 Handling Extras

The table below provides the guidelines for the keys used to indicate the extra runs scored during a match and the image in Fig. 9 shows the changed configuration of buttons on the calculator:

If the batsman scores runs off the bat, the scorer makes use of the numeric buttons from 1 to 6 on the calculator interface and their combinations with '+' button to enter the scores into the system (indicated by blocks '5.16' & '5.17' in Figure 5).

Scorer then presses dot ('.') button to indicate the completion of a delivery and the number of balls for the over is incremented by 1 (indicated by blocks

'5.19' & '5.20' in Figure 5).

If any exceptions other than the above standard scenarios occur, the scorer has the facility to indicate this by clicking 'Ot' button on the calculator interface

(indicated by blocks '5.21 ' & '5.22' in Figure 5) and various scenarios in this is mentioned under the sub process 'Special Cases' (indicated by block '5.23' in Figure 5).

Table 5.3.3 details various instances of special cases that may occur in a standard game of cricket:

9.3.3. Special cases

Scenario Description

Penalty Penalty runs/overs can be awarded by the umpire to any team for Runs violation of certain rules by the other team or reduced from a team's total for violations. Once the scorer chooses the option 'Penalty Runs' from the list of special cases, the system prompts the scorer to choose the team and whether it is 'runs' or Overs'. Then the control is passed back to the calculator interface where the scorer will mention if it is to be added or subtracted by clicking '+' or '-' and the number of runs or

• The system checks if it is the 'End of Over' after each delivery (indicated by block '5.24' in Figure 5).

• If it is not the end of an over, the control (indicated by connector '2') passes back to account for the next delivery. • The scorer will be prompted to press 'Over' button on the calculator interface at the end of each over (indicated by block '5.25' in Figure 5).

• If the end of over coincides with end of an innings, the systems prompts the scorer to mention if it end of match (indicated by blocks '5.26' & '5.27' in Figure 5). • If it is not end of an innings or end of match, the control passes on to the calculator interface to select the bowler and striker (indicated by connector T).

If it is end of the match, the scorer will be presented with option to capture the result of the match (indicated by blocks '5.28' to '5.29' in Figure 5). 10. MATCH SET UP - PROCESS FLOW

In order to scorecast a match, it is necessary to create essential details regarding the match in the system. Data required to set up a match are:

• Type of the match - with respect to cricket whether it is a Test, One- Day International (ODI), 2-day, 3-day, T-20 I etc. • Form of cricket - level in which the match is categorized like

International or First Division etc.

• Date of the match

• End date of the match - if the match type is one which spreads over more than one day like Test, 2-day etc.

• Starting time for the match

• Name of the ground City

• Country • Number of overs per innings for a cricket match

• Name of Umpires

• Name of Match referee

• Follow on decision - runs taken as criterion for enforcing follow on in a multiple innings cricket match • Name of participating teams

• Names of players in participating teams Officials of the teams

Logical flow of the process is provided in the flow chart given below: 10.1. Figure 6 Following lines explains the flow to set up a new match as shown in Figure 6:

• Select the type of match from the displayed list (indicated by block '6.01 ' in Diagram-6).

• Pick up the appropriate form of cricket from the selection list (indicated by block '6.02' in Diagram-6). • If the type of match is 'ODF or 'T20' or 'Limited Overs' (LO), provide the date of the match (indicated by blocks '6.03' & '6.04' in Diagram-6).

• If the type of match is any others, provide also the end date for the match and the runs set for follow on criteria in a multiple innings cricket match (indicated by blocks '6.05' & '6.06' in Diagram-6).

Fill in rest of details like 'Start time', 'Overs per innings', 'Name of ground', 'City', 'Country', 'Name of umpires' and 'Name of match referee' (indicated by block '6.07' in Diagram-6).

• On completion of the above entries, the user needs to define both the teams participating in the match.

• Team-1 and Team-2 needs to be defined sequentially as shown by the sub processes 'Set up Team(l)' and 'Set up Team(2)' (indicated by blocks '6.08' & '6.09' in Diagram-6).

• User will be provided with a list of teams created by him/her to choose from. • If a selection is made, name of players, captain, wicket keeper, coach, manager and physio will be displayed (indicated by blocks '6.08.01 ' & '6.08.05' in Diagram-6).

• If the team is not available in the list, proceed to create the new team (indicated by blocks '6.08.02' to '6.08.04' & '6.08.06' in Diagram-6). Details required to set up a team are: o Name of the team o Short name for the team o Name of players o Captain of the team o Wicket keeper o Name of coach o Manager o Physiotherapist

• On completion of setting up of teams, a unique ID is created for the match by the system and is displayed to the user confirming the completion of match set up (indicated by blocks '6.10' & '6.1 1 ' in Diagram-6).

11. TOURNAMENTS - PROCESS FLOW The system offers registered users ability to set up and manage any type of tournaments. Tournaments have various matches played between number of teams held in multiple rounds or in round-robin league basis. Standard steps in organizing a tournament involve:

• Fixing the dates • Setting up detailed fixtures mentioning the schedules of matches

• Defining participating teams

• Recording the match scores

• Tabulating the results Publishing the results Main details required to set up a tournament are:

• Name for the tournament

• Name of the Sponsor

• Name of the Organizer of the Tournament

• Brief write up on the tournament • From which date to which date the tournament is being conducted

• The prizes associated with the tournament

• Teams that participate in the tournament

• Number of rounds for the tournament

• Grouping of teams

• Fixture/schedule for the tournament Designated scorers for the matches

Logical steps to set up and manage a tournament are explained through the process flow chart in Figure 7. 11.1 Figure 7

Main steps involved in setting up and conducting a tournament depicted in the above flow chart are narrated below. The process begins after the user select the option to 'Set up Tournaments':

Fill in the essential details related to the tournament such as Name of the Tournament, name of the Organizers, Name of Sponsors, Prize, Duration,

Country, City (indicated by blocks '7.01 ' & '7.02' in Figure 7).

• Provide name for the 1st round in the tournament (indicated by block '7.03' in Figure 7).

• If the tournament has multiple rounds, enter names for each of the round, names for groups in each round and choose option 'There are no Groups' if the round does not have grouping of teams (indicated by blocks '7.04' to '7.09' in Figure 7).

• If the tournament does not involve multiple rounds, choose the option to mention that it has only one round (indicated by block '7.10' in Figure 7). • Select the option to set up matches for the tournament (indicated by block

'7.1 1 ' in Figure 7).

• Select a round which is already defined (indicated by block '7.12' in Figure 7).

• Select groups under the particular round (indicated by block '7.13' in Figure 7).

• Option is provided to enter Date, Time, Venue, Teaml, Team2 and the scorer for the match and a unique match ID is generated (indicated by blocks '7.14' & '7.15' in Figure 7).

• The process is repeated till all the groups for the round and all the rounds for the tournament are covered (indicated by blocks '7.16' & '7.17' in Figure 7).

• The system compiles these data to create the fixture for the tournament (indicated by blocks '7.18' in Figure 7).

• The fixture is published and displayed to all the users once the user chooses the option to publish it (indicated by blocks '7.19' & '7.20' in Figure 7). • The fixture is the main input for conducting the tournaments which is mentioned as a sub process - 'Conduct Tournament' (indicated by block '7.21 ' in Figure 7).

• In order to conduct the tournament, the scorer selects the respective match from the displayed fixture for the tournament (indicated by block '7.21.01 ' in Figure 7).

• Scorecast the matches as per the processes detailed in 'Section 9' (indicated by block '7.21.02' in Figure 7).

• At the end of each match, the fixture is updated with the result for the respective match (indicated by blocks '7.21.03' & '7.21.04' in Figure 7). • If the match is the last match in the tournament, details of the final results are captured to declare the winner and data is compiled to create statistics for the tournament (indicated by blocks '7.21.05' & '7.21.06' in Figure 7). • Final results and statistics for the tournament are published for viewing by all the users ((indicated by blocks '7.07' in Figure 7).

Other modifications and variations to the invention will be apparent to those skilled in the art from the foregoing disclosure and teachings. Thus, while only certain embodiments of the invention have been specifically described herein, it will be apparent that numerous modifications may be made thereto without departing from the spirit and scope of the invention.