SOFTWARE REQUIREMENTS SPECIFICATIONS

FOR GAMING APP

CONTENTS

1. INTRODUCTION
1.1 Purpose
1.2 Document conventions
1.3 Intended audience
1.4 Definitions
1.5 Project scope
2. OVERALL DESCRIPTION
2.1 Product perspective
2.2 Product features
2.3 User classes and characteristics
2.4 Operating environment
2.5 Design and implementation constraints
2.6 User characteristics
2.7 Assumptions and Dependencies

SPECIFIC REQUIREMENTS
3. FUNCTIONAL REQUIREMENTS
3.1 Functional requirement 1
3.2 Functional requirement 2
3.3 Functional requirement 3
3.4 Functional requirement 4
3.5 Functional requirement 5
4. NON FUNCTIONAL REQUIREMENTS
4.1 User interface
4.2 Hardware interface
4.3 Software interface
5. OTHER NON FUNCTIONAL REQUIREMENTS
5.1 Performance requirements
5.2 Safety requirements
5.3 Security requirements
5.4 Software quality attributes
6. OTHER REQUIREMENTS
6.1 Data base
 1. Introduction

1.1 Purpose

This document describes the software requirements specification for a gaming website. This SRS
document provides a detailed overview of gaming app, its functional and non functional
requirement, parameters and goals.

1.2 Document Conventions

Any standards and information that were followed when writing this SRS, such as fonts or
highlighting that have special significance. For example, every requirement statement which is
specified here has its own priority.

1.3 Intended audience

The document is intended for all the customers, stake holders, and the developers including
designers, testers and maintainers. The main audience is assumed to have basic knowledge of
accessing a website and knowing about controls of games. Knowledge and understanding of
UML diagrams are also required.

1.4 Definitions

Account
A single account must be created on a website by joining through which gamers profile is
maintained. Accounts can be created in various ways like with e-mail, face book, goggle etc. A
user cannot hold more than one account with similar email-id/personal details.

Class Type
Class type is a category of gamer such as bronze with lower access followed by silver, gold
and platinum. Class type will be decided with the performance of gamers and also game cards
can also be purchased to increase their class type. Gamers Card Gamers card will be of four
categories Gold, Silver, Bronze and platinum. The bronze card user played game less times and
he is not so good at that particular game but the platinum class player already mastered the game
by spending his time to increase his performance and class.

Payment
The payment option is to purchase games and to buy the game cards to increase their rank.

Gamers/Customers
The people who play the game are commonly called game players or users. The gamers are
those who will login into the website putting their bank details and joining through their
Facebook ID’s or email-ID’s.
1.5 Project Scope

The app gives the user complete access to the games depending on their class type and will allow
them to play games as multiplayer as well as single player. In multiplayer game mode, the
opponents will be selected randomly and the user has his ability to choose his team members and
it will require a good internet connection to play such games.
The gamers can purchase game cards to play in offline mode and also, they can go for free
offline games which won’t need to be purchased. The app will send a gamers card to the user
after verifying all his personal details and payment details. The developer of the game allows you
to see the profiles of other gamers, make teams, join tournaments, see gaming videos, put
reviews, etc. The achievements of the gamers must be properly recorded so that gamer class can
be pushed up and also the gamer can avoid already completed levels by playing again.

2. Overall Description

2.1 Product Perspective

The gaming network does not work alone or independently. It works together with the multiple
computers through a channel connected over a wide area network and the app connection run by
the server maintained locally in a company.

Communication interface
The gamers communicate over world wide web through the internet connections. Users can
chat in some gaming applications while playing and in some other games gamers can
communicate too it all depends upon in which platform they are playing it needs good internet
connection for communication network are specific to the target gamer systems. Only limited
number of players can access this communication, At present known 10 gamers will access this
gaming website and will participate in the gaming network.

Hardware interface
The software will run on an all type of system having high quality of graphic card and having
good speed of internet connections.

User interfaces

Gamers/Target
The customer user interface should be intuitive, like all new users are able to complete their
registrations and enhance their gaming experience without much assistance.

Game Designer
There must not be any difficulty in uploading the new features with same interface and
requirements by the game designers.
Maintainer
The maintainer is responsible for adding new features to the game and maintaining the
records of all the game features as well as adding new features into games. A maintainer should
provide the privacy and security to the user information provided by the user to access the game.
The maintainer should provide quick access to the gamer to play his game.

2.2 Product Features

The game server should work all day and night. The game must to identify the customer by his
gamer card number, username and password. It collects information about a simple profile
maintained with the details provided by the user himself during joining process, this profile helps
the gamer to communicate with the game features as well as with other gamers during an
amazing gaming experience, and allows to play games to the gamers. The app requires
appropriate record keeping and security provisions. The website must handle the concurrent
access of the same user correctly.

2.3 User Classes and Characteristics

Characteristics
There are several users of the website:

Gamers
Gamers are simply members of the general public with no special training from the developer
or the company in which the game is being developed.

Game designers and web designers

Game designers and app designers need have special education or developing Experience in
their corresponding fields as per requirements of the company.

Maintainers
Maintainers must be experienced network administrators, app designers as well as game
developers who are capable of maintain the app within time and the feasible features required.

2.4 Operating Environment

The hardware, software and technology used should have following specifications:
• Ability to read the profile of the gamer by another gamer.
• Ability to access the game features according to their class and game cards.
• Assistance and customer support given wherever needed.
• Continuous access of the game whenever needed.
• Ability to connect to website with respect to the users internet speed.
• Ability to access multiplayer mode.
• Ability to validate user and allow user to add friends
• Once login user must not be required to ask to re-login at the same system at same time.
2.5 Design and Implementation Constraints

• Login

Validating Gamers Card

• Validate gamers card before Expiration Date
• Validate that the card's expiration date is later than today's date .
• If card is expired, prompt error message "Card is expired" and remove the card access of the
user.

Validate for card upgrade

• Validate for card upgrade and access the card.
• While upgrading ask the details of previous card.
• Ask for payment.
• Update user profile.
• Upgrade the card.

Validate for Disabled Card

• Validate that the card is not disabled.
• If card is disabled, prompt error message, "Card has been disabled as of <expiration date>" .

Validate for Locked Account

• Validate that the account is not locked
• If account is locked, prompt error message "Account is locked"

Validate Password
• Validate that the password is not blank.
• If password is blank, prompt error message "Please provide correct password".
• Validate that the password entered matches the password on file.
• If password does not match, prompt error message "Password is Incorrect".

Blocking Account
• If user is found to access the any kind of private data or misleading the data by hacking into the
server or troubling any users.
• Permanent block of the login address of that user and block and do not show the profile of that
user.

2.6 User Characteristics

The gaming website is targeted to all aged users above 13 years. As this is the age group
knowing how to interact with the systems and they also love gaming. The gamers who are
always in search of some interested and interacting games are always be our main targets.
2.7 Assumptions and Dependencies

• System hardware never fails

• Internet speed is always good.
• Limited number of users at a time.
• Limited number of gamers played a game in single moment of time.

Specific Requirements
3.Functional requirements

3.1 Functional Requirement 1

• Ask personal details such as name, email-id, Date of Birth, Phone number (optional) and if he
purchased card than ask card details.
• Inputs (details).
• Check all inputs are correct or not.
• Check whether any mandatory input is not left blank.
• Process the input given by the user.
• Save processed data.

3.2 Functional Requirements 2

• Set the default payment modes to purchase game card and extra features.
• Ask the customer to insert the card type such as master or visa if credit card selected.
• Ask for credit card details such as number, expiry and pin.
• Ask to insert debit card number and pin/cvv if debit card selected.
• Move to payment gateway option if net banking is selected

3.3 Functional Requirements 3

• Make a default gamers profile.
• Update gamers profile as per the achievement of the gamer/user with the gamers class type.

3.4 Functional Requirement 4

• Sanction a gamer card assigning a random password and number.
• The card number must not match with any other card hence make it unique.
• Match check with the others user game card number.
• Set expiry date as per the membership of the user.
• Update expiry date if user asks to update it and ask for payment.

3.5 Functional Requirement 5

• The app must contain detailed player profile, both single and multiplayer mode, help and like
options.
• Each option must be present in its own location.
• When user switches the multiplayer mode it must give access to multiplayer mode or else
single player can play alone.
•Help option must solve user troubles and solving the query of every user.
4. Non-Functional Requirements
4.1 User Interface
The user interface should be intuitive, such that all of all new web users are able to complete
their website registration without any assistance can access to games with least assistance
required.

4.2 Hardware Interface

The hardware should have following specifications:
• Ability to read the profile of the gamer
• Ability to access all the games falling in the respective class of the gamer.
• Assistance given wherever needed.
• Continuous power supply
• Ability to connect to website at the mentioned internet speed
• Ability to access multiplayer mode
• Ability to validate user and allow user to add friends
• Once login user must not be required to ask to re-login at the same system at same time.

4.3 Software Interface

No additional software is required to access the website. You just need network access software
to access to internet and get into the network.

5. Other Non-Functional Requirements

5.1 Performance Requirements.

• It must be able to perform in adverse conditions like high/low temperature etc.
• Uninterrupted connections (one users connection must not interrupted by other).
• High data transfer rate.

5.2 Safety Requirements

• Must be safe enough to avoid any data lose.
• Must not leak the card details of any user.
• There must an auto checker assigned to check any unidentified action of the user.
• Secured enough to stop hacking at maximum instance.
• The Personal details of user must not leak if user wants to keep it personal.
• No leakage of confidential data from the website.
• Bug tracking must be there.

5.3 Security Requirements

• Users accessibility is censured in all the ways.
• Users are advised to change their Password on first use.
• Users are advised not to tell their Passwords to anyone.
• The maximum number of attempts to enter password will be five [After that, account will be
temporarily locked].
5.4 Software Quality Attributes.
5.4.1 Availability
The website has to be accessible 24 hours a day.
 5.4.2 Security
The website should provide maximal security. The maintainer should not leak any data of
user and it must be protected from hackers.

5.4.3 Maintainability
Only maintainers are allowed to connect the app network interface for maintenance.

6. Other Requirements
6.1 Database
All the database of particular users must be kept into different databases and they all must be
updated with every action done the user on the website.