ABSTRACT

This is a prediction game guided by Graphical User Interface. This can be used/played by
anyone who has basic cricket knowledge. The user must register himself and verify himself
with his g-mail account. The user will be given 500 points for registering himself. The user
should select the available matches. The user should invest his points in the options given.
The user has the freedom to invest his money in both options for the given question. If his
options are correct then his points will be doubled otherwise his invested points on the
question will be halved. The project has an admin login through which the admin sets the
match between the teams competing and feeds the answer for the question after the match has
been completed. The leaderboard positions will be shown with all the registered users
irrespective of participation. The questions are quite simple, like more run-getters, more
wickets, etc., among the players shown as options. This project is developed to provide the
fun of betting without investing a penny. I came across this project looking at various
advertisements during the Indian premier league
 Experiment-I: Software Requirements Specification

(Cricket League)

1. Problem Statement: To collect software requirements and create software requirement

specifications.

SOFTWARE REQUIREMENTS: Ms Word.

1. Introduction

1.1 Purpose Basic Description of Problem

Cricket League application provide facility to admin for managing the tournament and match
cancellation. When bidders bid on a match, the admin should be able to view all the bidders
bidding on a particular team and the percentage of users supporting a team.

2Application should also

provide facility to admin for
managing the tournament and
match
3cancellation. When bidders bid
on a match, the admin should be
able to view all the bidders
4bidding on a particular team and
the percentage of users
supporting a team.
5Application should also
provide facility to admin for
managing the tournament and
match
6cancellation. When bidders bid
on a match, the admin should be
able to view all the bidders
7bidding on a particular team and
the percentage of users
supporting a team.
8Application should also
provide facility to admin for
managing the tournament and
match
9cancellation. When bidders bid
on a match, the admin should be
able to view all the bidders
10bidding on a particular team
and the percentage of users
supporting a team.
11Application should also
provide facility to admin for
managing the tournament and
match
12cancellation. When bidders bid
on a match, the admin should be
able to view all the bidders
13bidding on a particular team
and the percentage of users
supporting a team.
1.2 Scope

The purpose of this specification is to document requirements for a system to manage Student
and Staff information. The specification identifies what such a system is required to do. The
specification is written in a format conforming to the IEEE Standard 830- 1984. Subject to
approval, the specification will complete the Requirements phase and will be followed by
detailed design, implementation, and testing.

1.3 Definitions, Acronyms, and Abbreviations

GUI Graphical User Interface

1.4 References
1. IEEE Std 830-1998: IEEE Recommended Practice for Software Requirements
Specification
2.J. Peters, and W. Pedrycz, Software Engineering – An Engineering
Approach. New York, NY: Wiley, 2000.

3.D. P. Gilliam, T. L. Wolfe, J. S. Sherif, and M. Bishop, “Software Security

Checklist for the Software Life Cycle,” in Proc.

WETICE’03, 2003, pp. 243-248.

4.A. D. Rubin, “Security Considerations for Remote Electronic

Voting,” CACM, vol. 45, pp. 39-44, Dec. 2002.

1.5 Overview

This specification includes a brief product perspective and a summary of the functions the
software will provide. User characteristics are discussed, and any general constraints or
assumptions and dependencies are listed. Requirement statements are categorized as
functional requirements, performance requirements, non-functional requirements, or design
constraints. The rest of the document contains the overall description of the system,
requirements, data model, and behavioral description of the system and project planning.

2. General Description

2.1 Product Perspective

The cricket league is maintained by system m where players have easy access to play the
game, even when they have to singly.

2.2 User Characteristics

There are two different types of users for the Cricket League.
Based on the above categorizations, in order to meet user's needs the following precautions
should be taken:

 the interface should be designed with the computer novice in mind

 data entry masks should recognize and correct improperly entered data
 for deleting or revising a record the system should ask the users for confirmation