SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION

The document aims at defining the overall software requirements for “SPORTS
MANAGEMENT SYSTEM”. Efforts are been made to define the requirement
exhaustively and accurately. The final product will be having only
features/functionalities mentioned in this document and assumption for any additional
functionality/feature should not make by any of the parties involved in
developing/testing/implementing the products. In case it is required to have some
additional features, a formal change request will need to be raised and subsequently a
new release of this document and/or product will be produced.

1.1 PURPOSE

This specification document describes the capabilities that will be provided by the
software application “SPORTS MANAGEMENT SYSTEM”. It also states the
various required constraints by which the system will abide. The intended audience
for this document is the development team, testing team and the users of the
produced.

1.2 SCOPE

The software “SPORTS MANAGEMENT SYSTEM” will be an application that will be

used for managing sports database. The application will manage the information about
the players, the matches and the events that are to be held, coaches and the board that will
plan everything.

1.3 DEFINITIONS, ACRONYMS AND ABBREVATIONS

The following abbreviations have been used throughout:

DBA – Database Administrator

1.4 REFERENCES

(a) IEEE recommended practice for software requirements specifications-IEEE

standard 1830-1993.

1.5 OVERVIEW
The rest of this SRS document describes the various system requirements, interfaces and
functionalities in details.

2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The application will be a window based, self-contained and independent software

product.

2.1.1 SYSTEM INTERFACES

None

2.1.2 USER INTERFACES

The application will have a user friendly and menu based interface.
Following screens can be found:

(a) A login screen for entering the user name, ID number and password for the
operator will be provided. Access to different screens will be based upon the
role of the user.
(b) There will be a screen for capturing and displaying player details viz. name,
age, matches played,runs scored..
(c) There will be a screen for capturing and displaying info, regarding the
schedule of the matches/events that have been planned by the board.

2.1.3 HARDWARE INTERFACES

(a) Screen resolution of at least 800 X 600 is required for complete and proper viewing
of screens. Higher resolution will not be any problem.
(b) Support for printer: proper drivers must be installed and printer connected will be
requested for printing of monthly reports.
(c) Standalone or network based not a concern as it will be possible to run the application
of any of them.

SOFTWARE INTERFACES

(i) Any windows based operating system.

 (ii) MS EXCESS 2000 as the DBMS for database future release of the
application will aim at upgrading to ORACLE-8i to DBMS.L
(iii) Crystal reports-8 for generating and viewing reports.
(iv) Visual basic for coding developing the software. The final application
packages as an independent setup program that will be delivered to the
client.

2.1.4 COMMUNICATION INTERFACES

None

2.1.5 MEMORY CONSTRAINTS

At least 64 MB of RAM and 2 GB on hard disk will be required for running the
application.

2.1.6 OPERATIONS

This product release will not cover any automated housekeeping aspects of the data base.
The DBA at the client site will be responsible for manually deleting old or non-
required data. Data base backup and recovery will also be handled by the DBA.

2.1.7 SITE ADAPTATION REQUIREMENTS

The terminals at client site will have to support the hardware and software interfaces
specified ` in the above section.

2.2 PRODUCT PERSPECTIVE

The system will allow access to only authorized personnel. Depending on user’s role,
he/she will be able to excess only specific modules of the system. A summary of the
major functions that the software will perform are:

(i) A login facility for enabling only authorized person to the system.
(ii) Board (with role of DBA) will be able to add/modify/delete information
about different players, coaches and the different matches/events that have
been scheduled.
(iii) User (with role of a operator) will be able to access details regarding a
particular player, matches and the events that have been scheduled.

2.3 USER CHARACTERISTICS

(i) Educational Level: At least graduate should be comfortable with English

Language.
 (ii) Technical Expertise: Should be comfortable using general purpose
applications on a computer.

2.4 CONSTRAINTS

(i) Since the DBMS being used is MS EXCESS 2000, which is not a very
powerful DBMS, it will not be able to store a very large number of
records.
(ii) Due to limited features of DBMS being used, performance tuning features
will not be applied to the queries and thus the system will become slow
with the increase in number of records being used.
(iii) Due to limited features of DBMS being used, database auditing will not be
provided.

2.5 APPORTIONING OF REQUIREMENTS

None

3. SPECIFIC REQUIREMENTS
This section contains the software requirement to a level of detail sufficient to enable
designers to design the system and testers to test the system.

3.1 EXTERNAL INTERFACES

3.1.1 USER INTERFACES

The following screens will be provided:

(i) LOGIN SCREEN

This will be the first screen to be displayed. It will allow user to access
different screen based upon the user’s role. Various fields available on this
screen will be :

(a) User ID : Alphanumeric upto 10 characters

(b) Password : Alphanumeric of length upto 10 characters.
(c) Role : will have the following values (data entry operator).

(ii) PLAYERS NFORMATION SCREEN

This screen is accessible to the data entry operator, controller. It allows the
user to access the players profile. Coaches can also access the same page
but any modifications required can only be done by the board.
 (iii) COACHES INFORMATION SCREEN

This screen is accessible to the data entry operator which allows to

add/modify/delete details about the coaches.. This screen will display
coach name, age and the team coached by him.

(iv) MATCHES/EVENTS SCREEN

This screen is accessible to the to everybody who can login.. The board
can add’/modify information. Screen displays the date, time and the venue
of the matches/events that are to be held.

3.1.2 HARDWARE INTERFACES

(i) Seen resolution of at least 800X600 is required for complete and proper
viewing of screens. Higher resolution will not be any problem.
(ii) Support for printer: Proper drivers must be installed and printer connected.
Printer will be requested for printing of monthly reports.
(iii) Standalone or network-based-not a concern as it will be possible to run the
application of any of them.

3.1.3 SOFTWARE INTERFACES

(i) Any windows based operating system

(ii) MS EXCESS-2000 as the DBMS for database future release of the
application will aim at upgrading to ORACLE-8i to DBMS.
(iii) Crystal reports-8 for generating and viewing reports.
(iv) Visual basic for coding developing the software. The final application
packages as an independent setup program that will be delivered to the
client.

3.1.4 COMMUNICATION INTERCACES

None

3.2 SYSTEM FEATURES

3.2.1 PLAYERS INFORMATION MANAGEMENT

DESCRIPTION

The system will maintain record of players name, age, matches played, runs
scored, average and their current ranking. The system will allow
creation/modification/deletion info about new or existing players .
 SEQUENCING INFORMATION

Players information will have to be entered before anyone can access those
details.

ERROR HANDLING/RESPONSE TO ABNORMAL SITUATIONS

If any of the above validations/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

VALIDITY CHECKS

(i) Only user with controller or data entry operator will be authorized to
access the passengers information management module.
(ii) Every passenger will have allotted a unique ticket number, seat number.
(iii) Seat number and passenger name can not be blank.

3.2.2 MATCHES/EVENTS INFORMATION MANAGEMENT

DESCRIPTION

The system will maintain information about the matches/events that have already
been played or are yet to be played. It also tells us about the venues and the
timings of the matches/events to be held. The system will allow
creation/modification/deletion of new or existing schedules.

VALIDITY CHECKS

Only user with role of controller or data entry operator can access this module.

SEQUENCE INFORMATION

The information will be present in the system before it can be accessed.

ERROR HANDLING/RESPNOSE TO ABNORMAL SITUATIONS

If any of the above validations/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

3.3 OTHER REQUIREMENTS

3.3.1 PERFORMANCE REQUIREMENTS

None
3.4 DESIGN CONSTRAINTS

None

SOFTWARE SYSTEM ATTRIBUTES

3.4.1 SECURITY

The application will be password protected. Users will have to enter correct
username, password and role to access the application.

3.4.2 MAINTAINABILITY

The application will be designed in a maintainable manner. It will be easy to in

corporate new requirements in the individual modules .

3.4.3 PORTABILITY

The application will be easily portable on any WINDOW based system that has
MS-ACCESS 2000 installed.

3.5 LOGICAL DATABASE REQUIREMENTS

The following information will be placed in a database.

(i) Players information which will include details about their cricketing
career.
(ii) Coaches information which will include information about their coaching
career.
(iii) Matches/Events information which include the date, time and the venue
for the matches/events to be held.

3.6 Other Requirements

None