0% found this document useful (0 votes)
34 views9 pages

System Requirement Specification: (161B067, 161B065, 161B066) BX-B2

This document provides requirements for a soccer management system called SMS. It will allow users to create a league with teams, schedule matches between teams, and track a league table with goals scored and conceded. The system will be a desktop application developed in Java using common OOP concepts. It will include functionality for creating, deleting, retrieving, and displaying team and match data from the user's input.

Uploaded by

Chetan Choudhary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views9 pages

System Requirement Specification: (161B067, 161B065, 161B066) BX-B2

This document provides requirements for a soccer management system called SMS. It will allow users to create a league with teams, schedule matches between teams, and track a league table with goals scored and conceded. The system will be a desktop application developed in Java using common OOP concepts. It will include functionality for creating, deleting, retrieving, and displaying team and match data from the user's input.

Uploaded by

Chetan Choudhary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

VERSION 0.

0
DATE

SYSTEM
REQUIREMENT
SPECIFICATION

PRESENTED BY: CHAITANYA , BHANU PRATAP , BIKAS KUMAR SHARMA


(161B067, 161B065, 161B066)
BX-B2
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

TABLE OF CONTENTS
1.INTRODUCTION........................................................................................................................3
1.2 PURPOSE ...............................................................................................................................3
1.3 SCOPE.....................................................................................................................................3
1.4 DEFINITIONS ACRONYMS AND ABBREVIATIONS ...................................................................4
1.5 REFERENCES...........................................................................................................................4
1.6 OVERVIEW..............................................................................................................................4
2 Overall Description....................................................................................................................5
2.1 Product Perspective ...............................................................................................................5
2.1.1 System interfaces.................................................................................................................5
2.1.2 User interfaces.....................................................................................................................5
2.1.3 Hardware interfaces............................................................................................................5
2.1.4 Software interfaces..............................................................................................................5
2.1.5 Communication Interfaces..................................................................................................6
2.1.6 Memory..............................................................................................................................6
2.1.7 Operations ..........................................................................................................................6
2.1.8 Site adaptation requirements..............................................................................................6
2.2 Product Functions...................................................................................................................6
2.3 Constraints..............................................................................................................................7
2.4 Assumptions and Dependencies............................................................................................8
3. Specific Requirements............................................................................................................10
3.1 Interface Requirements........................................................................................................10
3.2 Functional Requirements.....................................................................................................10
3.3 Nonfunctional Requirements...............................................................................
3.4 Performance Requirements..................................................................................................15
3.5 Design Constraints................................................................................................................15
4 Comments...............................................................................................................................28

Date Project 1
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

PROJECT
1. INTRODUCTION
This Section introduces the Software Specification Requirement document for
the Soccer Management System . The Soccer Management System is a simple yet
effective way to manage fixtures of different teams in the league , with this you
can create your own league of teams, create you specialized matches . It
provides you a way to create a simplified and personalized soccer system of your
own with efforts close to none. It has a custom comparator for different teams
and matches . The software has used various object oriented programming
concepts and is majorly coded in JAVA language using netbeans ide which made
it rather easier to debug the code. The system can be used to create, delete,
pass, retrieve and display data according to user's input and date using a mixture
of classes such as abstracts and interfaces as well as objects and arrays. The
league will mainly consist of the teams that the user has input and according to
the users input of various matches , a league table will be maintained which can
be retrieved later for further data . The matches function in regard to a calendar .
The League table also has a goal difference feature which computes the to and
against goals for each and every team . The project contains basic oops concepts
and nothing to fancy or complicated for the user to understand.

1.1. PURPOSE
The purpose of this document is to give a detailed description of the
requirements for the “SMS” software. It illustrates the purpose and complete
declaration for the development of system. It also explains system constraints,
interface and interactions with other external applications. This document is
primarily intended to be proposed to a customer for its approval and a reference
for the development team to develop the perfect product of the system to run
smoothly.

Date Project 2
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

1.2. SCOPE
The “SMS” Software is an event based football matches simulator . It should be
primarily focused on garnering people with an interest for football simulators.
The application of the project can be multiple like mini games on PC devices , or
an android/IOS application for youngsters who wish to manage a league and can
also be available on social media sites like Facebook who entertain simple low
cost games to entertain their users in the near future with extended software
development . The immediate application of such a software is limited to pc
users .

1.3 DEFINITIONS ACRONYMS AND ABBREVIATIONS :


 IEEE: Institute of Electrical and Electronics Engineers
 iOS: Apple Mobile Operating System
 Android: Google Mobile Operating System
 MySQL: My Structured Query Language
 IDE : Integrated development environment
 Netbeans : Integrated development environment for Java

1.4 REFERENCES
 IEEE. IEEE Std 829-2008 Standard for Software and System Test
Documentation. IEEE Computer Society,2008
 IEEE. IEEE Std 830-1998 Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998
 IEEE. IEEE Std 1016-2009 Standard for Information Technology -System
Design-Software Design Descriptions IEEE Computer Society, 2009

Date Project 3
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

1.5 OVERVIEW
This document provides a high-level description of the “SMS” simulator game.
The document then describes general software and hardware constrains as well
as any assumption and dependencies concerning the projects. The majority of
this document focuses on the specific functionalities. A master list of specific
functionalities is given first, followed by each explained in detail in the next
section. Both the internal and the external interfaces are addressed in the
subsequent section. The internal interface requirements are requirements
involving system interfaces and the external interface requirements are
requirements involving user hardware, software and communications interfaces.
This requirements document concludes with Comments section of the whole
document.
2 OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The project (SMS) is a single player social simulator game with a standalone
architecture containing a database module. Since a full match simulation is
complicated and unnecessary for a football manager themed social game, an
event-based match simulation whose actions is going to be selected from
extensive predefined scenarios depending on the parameters of the teams and
its players is going to be used. That results in the fact that those who will use this
product will interact each other and can compare their football managing career
in game. In development process, Java and (in future development) Flash
technologies, will be used with several required libraries, APIs and frameworks as
it is explained below.
2.1.1 SYSTEM INTERFACES
 Mouse Interface: Running on PC devices, this interface captures mouse
events and updates the application according to it.
 Keyboard Interface: Running on PC devices, this interface is the most useful
aspect as most of the user input will be addressed through this interface.

2.1.2 USER INTERFACE


- The user interface is nothing too fancy the software runs on NetBeans ide and can run
independently on systems that has the java jdk , which enables the system to execute the
software on the system.

Date Project 4
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

2.1.3 HARDWARE INTERFACE


- The hardware interface required for the proper execution of the software is a standard personal
computer with mouse and keyboard connectivity which will ensure the proper functioning.

2.1.4 SOFTWARE INTERFACE


2.1.5 COMMUNICATION INTERFACE
2.1.6 MEMORY CONSTRAINTS
2.1.7 OPERATIONS
2.1.8 SITE ADAPTATIONS REQUIREMENTS
2.2 PRODUCT FUNCTIONS
This product will provide these features to all who join in the game. User will
interact with these features on product user interface.
1. Personalized login
This feature will request the user for a username and password so as to
access his personalized league.

2. Football League
The user will then be given access to his football league which will have
His personalized matches and his calendar.

2.3 CONSTRAINTS
 Database: The software requires extensive database knowledge to store all
the inputs of the user for comparison in later stages of the software.

Date Project 5
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

 OOPS: The object-oriented programming concepts of JAVA are a must to


develop abstracts and interfaces / arrays to store information.
 Hardware Limitation: Every software has a hardware limitation on how
much CPU will be available for the software so the project must be very
efficient in terms of usage.
 Programming Languages: JAVA and oops knowledge is mandatory.

2.4 ASSUMPTIONS AND DEPENDENCIES:


 Since this project is a game project and it contains many features,
depending on the data that is collected from the user and general
experience of the developers, to increase the playability and attractiveness
of the game several features can be added to the project in the future and
those additions can affect the requirements and design.

3. SPECIFIC REQUIREMENTS:
3.1 INTERFACE REQUIREMENTS:
 The user interface for the software shall be compatible to any operating
system such as Windows XP,7, 8,10 . There should be no compatibility
issues in running the project.
3.2 FUNCTIONAL REQUIREMENTS:
The functional requirements are the requirements of the system shall do
3.2.1 USER FUNCTIONS:
User functions section explains what a user can do in the simulator.
3.2.2 LEAGUE MENU:
 This gives a brief classification of all the possible functions that the user can
perform with the system. It contains a variety of options such as Creating a
new team for the league, adding a team to the league, deleting an existing
team that was previously added from the league. Displaying the statistics
for the team (out of the 20 teams in the league). Displaying the league
table, adding a match that was played in the league and displaying the
calendar and finding a match

Date Project 6
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

3.2.3 CREATING A TEAM AND ADDING IT


 This feature allows the user to create a team for the league which gets a
position in the league table as soon as it gets created. Every team that is
entered gets a home stadium i.e. the stadium which has their own fans in
majority. Once a team gets inputted from the user it automatically gets a
position in the league table according to the alphabetical order or in the
order in which it was added.
3.2.4 DELETING A TEAM
 Once a team gets added into the league table once the user has created it.
This feature allows the user to delete the team which had to be deleted
due to some technical error or due to an error in insertion (i.e. wrong name
or exceeding the number of teams in the league)

3.2.5 DISPLAYING STATISTICS


 The Statistics of each team can be displayed by choosing this functionality.
This enables the user to observe the statistics of each team individually.
The statistics of each team include number of goals scored for, number of
goals scored against, matches won and the points scored after every
match.
3.2.6 LEAGUE TABLE
 The league table is another feature of the project. After every team gets
inputted by the user the teams play matches according to which their
position gets evaluated in the table. The number of goals scored for and
against determine the standings of each team against one another.
3.2.7 MATCH ENTRY
 The match entry system allows the user to input a played match between
two teams and their results which is the ultimate key in their standings in
the league table and also determine their statistics in the long run.
3.2.8 CALENDER AND FIND MATCH
 The calendar is another feature of the project which displays a calendar of
a year according to which matches are scheduled , this calendar enables
the user to check the standings and the results of the teams on a day to
day basis .

Date Project 7
SYSTEM REQUIREMENT SPECIFICATION
For Soccer Management System (SMS)

Date Project 8

You might also like