Sports Management System

Topics: Requirements analysis, Software Requirements Specification, Application

software Pages: 7 (1588 words) Published: April 28, 2013
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.
2.1

OVERALL DESCRIPTION
PRODUCT PERSPECTIVE

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

product. 2.1.1 None 2.1.2 USER INTERFACES SYSTEM 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) (iii) (iv)

MS EXCESS 2000 as the DBMS for database future release of the application will aim
at upgrading to ORACLE-8i to DBMS.L Crystal reports-8 for generating and viewing
reports. 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 None 2.1.5

COMMUNICATION INTERFACES

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
nonrequired 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...
Continue Reading
SOFTWARE REQUIREMENT SPECIFICATION1.
INTRODUCTION
The document aims at defining the overall software requirements f
or “SPORTSMANAGEMENT SYSTEM”. Efforts are been made to d
efine the requiremente x h a u s t i v e l y a n d a c c u r a t e l y . T h
e f i n a l p r o d u c t w i l l b e h a v i n g o n l y features/functionalities
mentioned in this document and assumption for any additionalf u n c t i o n a l i t y / f e a t u r e
s h o u l d n o t m a k e b y a n y o f t h e p a r t i e s i n v o l v e d i n developing/t
e s t i n g / i m p l e m e n t i n g t h e p r o d u c t s . I n c a s e i t i s r e q u i r e d t o h a v e s o m e additi
onal features, a formal change request will need to be raised and subsequently anew
release of this document and/or product will be produced.
1 . 1 P U R P O S E
This specification document describes the capabilities that will be provid
e d b y t h e software application “SPORTS MANAGEMENT SYSTEM”. It also states
thevarious required constraints by which the system will abide. The intended audiencef o r t h i s
document is the development team, testing team and the users
o f t h e produced.
1 . 2 S C O P E
The software “SPORTS MANAGEMENT SYSTEM” will be an application that will beused for
managing sports database. The application will manage the information aboutthe
players, the matches and the events that are to be held, coaches and the board that will plan
everything.
1.3DEFINITIONS, ACRONYMS AND ABBREVATIONS
The following abbreviations have been used throughout:DBA – Database Administrator
1 . 4 R E F E R E N C E S
(a) IEEE recommended practice for software requirements specifications-
IEEEstandard 1830-1993.