< Mobile Car Racing (3D Game) >

Software Requirements Specification

Version 1.0

Group Id: S1902D35CF >

Supervisor Name :<Muhammad Bilal >
Revision History

Date Version Description Author

(dd/mm/yyyy)
1 June,2019 1.1 Scope of the Project is to BC150202588
provide user with a simple and
user friendly game . so that
user can enjoy 3d car racing
game .
Functional Requirements,
Non-Functional Requirements,
Use Case Diagrams and Usage
Scenario are written.

Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology
 6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS Document

Scope of Project:

The idea of this project is to create a 3D car racing game which can be played offline . It
will be fun to play and use get excited and relaxed while playing the game .

Functional and non Functional Requirements:

Functional Requirements

Definition:

“The functional requirements are those system/software requirements that specify a

function that a system/software system must be capable of performing in correct manner.
These are software requirements that define behavior of the system, that is, the
fundamental process or transformation that software and hardware components of the
system perform on inputs to produce desired outputs”.

Level Selection:
User will select the Levels from the given lists over here.

Cars lists:
All best available Car will be appeared on the screen for the user.

Gameplay :
When user will choose one of the Car the Gameplay screen will appear and user will get
to play the game.

Nonfunctional Requirements
Definition:

“Nonfunctional requirement in software system engineering that not describes

what the software will do, but how the software will perform the task”.
  Minimum Requirement:
PC/MOBILE PHONE

 Security Requirements:
It will be totally secured, no personal data of the user will be taken, simply user
can use it .

 Reliability:
The Game application will be fully reliable and will provide the maximum
operation of its working.

 User Friendly:
The Layout of the Game will be user friendly that the user can easily understand
and use .

Use Case Diagram(s)

Usage Scenarios:

Use Case Title

Use Case Id SI-01

Actor: User
Description: In our Game user will get to play a car racing game.
Pre Conditions: User wants to win the race .
Task Sequence: Exceptions
1. First user will open up the Game.
The only exception
2. Then user will select play option .
is that user tries to
3. The Game will start for user to play .
excess invalid
command.
Post Conditions: User successfully Get to play, Or if the exception of invalid selection
occur than user will be told properly.
Author:

Adopted Methodology

Waterfall Model Definition:” The waterfall model is a sequential design process,

often used in software development processes, in which progress is seen as flowing
steadily downwards through the phases of Conception, Initiation, Analysis, Design,
Construction, Testing, Production/Implementation, and Maintenance.”

Waterfall Model
 System Analysis
Validation

Plan & Requirements

Validation

DB Design
Verification

GUI Design
Verification

Coding
Unit Test

Testing
Product Verification

Implementation
System test

Maintenance or BUG Removal

Revalidation

In this approach, we see that processes flows in a downward fashion from requirement
phase to Testing phase which meets to client satisfaction. Requirements phase collects
software specifications, functional and non functional requirements in SRS (software
requirement specification). Analysis phase analyzes cases and work plan on the basis of
software requirement phase that covers use case scenarios up to methodology and work
plan. Design phase goes through with flow charts, algorithms and GUI on the basis of
analysis phase. Coding phase generates the actual logic of the application and provide
functionality to the system. The system logic is tested if it is working as it is as in
designing phase.

Spiral Model Definition:-

“The spiral model is a risk-driven process model generator for software projects. Based
on the unique risk patterns of a given project, the spiral model guides a team to adopt
elements of one or more process models, such as incremental, waterfall, or evolutionary
prototyping.”

Spiral Model
 Planning Risk Analysis:
Software Requirement Cost effectiveness with
Specification and work plan Minimum risk

Project delivery with Designing, Coding, Testing

Quality otherwise
Recycle it for further Development:-
Evaluation

Client Evaluation:-
Planning phase covers scope, requirements and functionality of the system. Second phase
Risk analysis is most important phase of spiral model which defines cost-effective
strategies in project development. Risk at any stage indicates that requirements must be
reviewed to find out solution for the problem by given data in the previous phase before
proceed to the next. Development phase covers the designing, coding and testing. And In
case of any change it is required to iterate the application from all four phases again.
That’s why it is called spiral model.

Combination of Waterfall and Spiral Model:-

Requirements System Analysis

Planning Risk Analysis:

Software Requirement Cost effectiveness with
Specification and work plan Minimum risk

Project delivery with Designing, Coding, GUI Design

Quality otherwise Testing
Recycle it for further
Evaluation Development:-

Client Evaluation:-
Coding
Acceptance

Testing

Combination of both waterfall and spiral model is called hybrid approach of system
development that maximize the quality of system and minimize the disadvantages and
risk.
Work Plan (Use MS Project to create Schedule/Work Plan)