ONLINE

Live Cricket Scores.

Software Requirement Specification

Syed Rabbani. V. Pramod Kumar.

(1) Preface:This document has been written to apply a new version of SRS Software Requirements Specification depends on IEEE-STD-830-1998 standard. So, you must compare this document with this standard.

This document is the basic intended for any individual user, developer, tester, project manager or documentation writer that needs to understand the basic system architecture and its specifications.

(2) Introduction:The following subsections of the SRS document provide an overview of the entire SRS.

Purpose:The purpose of our project is to provide scores of live cricket matches (International and domestic) daily which is happening totally around the world.Our project consists of a database which comprises of information about all the players from different countries in all formats (Date of birth, runs scored, wickets, catches etc…). Atlast our main aim was that the user can able to book the tickets for the upcoming and important matches securely.

Scope and Limitations:

The scope and limitation of this system is:

The on-line live cricket scores is designed particularly for cricket lovers. This website provides facility to users to know the live cricket scores by

staying anywhere within a short time, and they can view ball by ball commentary and videos of individual innings , matches.

It contains the info of all players which are mentioned above (in purpose). In our website we can get the latest Icc rankings of batting, bowling, team

and all-rounders in International cricket. In our website, user have a specific id and username to book there tickets

online for the upcoming matches. Verify a security, authority and safety.

Benefits: Benefits of our project is to view the live cricket scores and to view the matches lively through our servers present through our laptops, mobiles and other electronic gadgets which contain internet when they are unable to see the matches in television and when they are busy at offices and on some important work. And user can book the tickets to view the matches in live action.

Overall Description:In Online Live cricket scores user can register to book an online ticket and view the cricket records in all formats of all players. User can know the recent updates of cricket by just clicking our website.

(3) User Requirements Definition:The user requirement for this system is to make the system fast, flexible, less prone to error, and save the time.

It’s a easy way of viewing the scores. A system can be able to access the user bank details safely while they are

booking the tickets there is no need of afraiding about the hackers because we built our system with utmost security cares .

A facility to generate a result chart as pre required without manual interface.

The system should have records of users that can be access to the system which can be used only for the authorized person.

The system should be more secure for user records and more reliable to work at any conditions.

(3.1)The products and process features:This system must be designed as user required. So, the complete requirement must be found:

Easy to store and retrieve information:

Our system consists of database management to store and retrieve the information needed by the different type of users according a report generated by the system.

View Matches Online :Our system consists of different types of servers so that the user can view the match online when he away from home or from working place.

(4) System Requirement Specification:

(4.1) Functional System Requirement:This section gives a functional requirement that applicable to the On-Line Live cricket scores.

There are two sub modules in this phase.

User module.

Live Scores module.

Book-Tickets module

Rankings module

Videos and Images.

Records

The functionality of each module is as follows:

User module: It consists of login page and register page for the user.The candidate will logon to the webpage. He can book his tickets and he can view previous booking details also.

Live Scores module: In this module user can view the live cricket scores up to date with-out logging in to there account normal user who is not having his account also can view the scores .

Book-Tickets module: In this module user can book his tickets by logging in to his account where our system can access the bank details of the user safely and securely.

Rankings module: In this module user can view the latest Icc rankings of team , batsmen , bowlers and all-rounders.

Videos and Images: In this module user can view the videos and images of cricketers and there matches.

Records: In this module user can view the records of cricket by there team and by individually.

The features available to the User are:

Can view the different categories of Test available in their account. Can change password. Can view there details. Can view the stuff present in our website. Can view and modify its profile but can modify it to some limited

range.

(4.2) Non-Functional System Requirements:

(4.2.1) Performance RequirementsSome Performance requirements identified is listed below:

The database shall be able to accommodate a minimum of 10,000 records of students.

The software shall support use of multiple users at a time. There are no other specific performance requirements that will

affect development.

(4.2.2) Safety RequirementsThe database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup.

(4.2.3) Security RequirementsSome of the factors that are identified to protect the software from accidental or malicious access, use, modification, destruction, or disclosure are described below. Keep specific log or history data sets

Assign certain functions to different modules Restrict communications between some areas of the program Check data integrity for critical variables Later version of the software will incorporate encryption

techniques in the user/license authentication process.Communication needs to be restricted when the application is validating the user or license. (i.e., using https).

(4.3) System Interfaces:This section describes how the software interfaces with other software products or users for input or output.

(4.3.1) User InterfaceApplication will be accessed through a Browser Interface. The interface would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to access any part of the application without logging on to the system.

(4.3.2) Hardware InterfacesServer Side:

Operating System: Windows 7/xp Processor: Pentium 3.0 GHz or higher RAM: 256 Mb or more Hard Drive: 10 GB or more

Client side:

Operating System: Windows 9x or above, MAC or UNIX. Processor: Pentium III or 2.0 GHz or higher. RAM: 256 Mb or more

(4.3.3) Software Interfaces Client Side: HTML, Web Browser, Windows XP/2000/Vista/7 Web Server: .HTML, Windows XP/2000/Vista/7

(4.3.4) Communications InterfacesThe Customer must connect to the Internet to access the Website:

Dialup Modem of 52 kbps Broadband Internet Dialup or Broadband Connection with a Internet Provider.

(4.4) Software Quality AttributesThe Quality of the System is maintained in such a way so that it can be very user friendly to all the users.

The software quality attributes are assumed as under:

Accurate and hence reliable. Secured. Fast speed. Compatibility.

(5) System Models:In this system we are using waterfall model to apply these ideas. Which will help us to separate each step and when we finish a one phase the output of it is the input to the next phase. Also, we can backwards if there is a new requirement or to apply any update.