Table of Contents

1.

Introduction.......................................................................................................................................3
1.1.

Purpose........................................................................................................................................3

I.2.

Scope...........................................................................................................................................3

I.3.

Definitions, Acronyms, and Abbreviations..................................................................................3

I.4.

References...................................................................................................................................3

I.5.

Overview.....................................................................................................................................3

2.

Positioning..........................................................................................................................................4
2.1.

Business Opportunity...................................................................................................................4

2.2.

Problem Statement.......................................................................................................................4

2.3.

Product Position Statement..........................................................................................................4

3.

Stakeholder and User Descriptions..................................................................................................5

3.1.

Stakeholder Summary..................................................................................................................5

3.2.

User Summary.............................................................................................................................5

4.

Business Model...............................................................................................................................6

5.

Functional, non-Functional requirements.......................................................................................7

6.

Use case diagram...............................................................................................................................8

7.

Use case description...........................................................................................................................8

8.

Domain Model..................................................................................................................................13

9.

Data flow diagram...........................................................................................................................14

10. DFD Level 3 Diagram......................................................................................................................15

Abstract
In this report we will be explaining all the functional requirements, business
opportunities, use case diagram, domain model, use case description and data
flow diagram of Breakout game. In this games player has to break the bricks
through the ball and handle it through paddle and scores are granted to the
player.

Introduction

In this report we will analyze and define high-level needs and features of the Breakout game. It
focuses on the capabilities needed by the stakeholders and the target users such as game players. This
report includes scope, market value and also describes working of the game, which will be solving
problems in other versions of Breakout game. The details of how the Breakout Game fulfills these needs
are detailed in the use-case and supplementary specifications.

1 Purpose
The purpose of this report is to highlight the key features and requirements of our project and also
to provide a vision of features and facilities that are provided to the game player. The purpose of project is
to provide more efficient, interactive graphical interface and multilevel game.

2 Scope
Our project deals with 2 types of users.
I.
II.

Game player
Developers

There will be different modules for different users according to their needs.

3 Definitions, Acronyms, and Abbreviations

BO

(Breakout )

4 References
http://thedoteaters.com/?bitstory=breakout

5 Overview
The present games on Breakout are less efficient, less attractive and error prone. Our project
Breakout game is efficient, attractive, fast, error free and will implement bricks breaking mechanism
using ball and paddle and then moving to next levels. This project will be implemented in Unity3d
and include one type of user that is game player.

2. Positioning
Where our game stands on business point of view.

2.1.

Business Opportunity

We can extend our project to an android application which is currently being developing in
Unity3d, and we can place it on Google play store as well as extending it into an IOS application and
place it on Apple app store, so that people can buy and download it from app store to play.

2.2.

Problem Statement

In the following table we will explain the problem statement.

2.3.

The problem of

Current versions of this game are less efficient, less

interactive graphical interface and have limited levels.

Affects

Game player, Game Developers and Gaming industry.

the impact of which is

The impact of problem is that, Game players are moving

towards other attractive arcade games which are
efficient and have interactive graphics, so for that games
they have to pay more.

a successful solution would

be

The successful solution we proposed is to build game

with high definition graphics which will be very
efficient and have multilevel in it as well as number of
broken bricks will be counted according to their color.

Product Position Statement

Following table explain the position statement of our system.

For

Game player.

Who

Microsoft Windows and Unity3d store.

The (product name)

Breakout.

That

That is a 3D arcade game.

Unlike

Unlike existing games which are slow, have poor graphics

and are limited to single level.

Our product

Our game provides interactive graphical interface, score is

updated upon number of bricks broken and according to
bricks color and it have multilevel which will load
efficiently.

3. Stakeholder and User Descriptions

3.1.

Stakeholder Summary

There are a number of stakeholders with an interest in the development and not all of them are end
users. In the table below we have described different types of stake holders:

Name

Description

Responsibilities

User

Game Player

-Purchase game.
- Play game.
- Provide feedback.

Client

Mam Maryam Kausar

Developer

Team of two
developers(XYZ)

Supervise and evaluate development

process.

ABC
Graphical User Interface
xyz
C# scripting

3.2.

User Summary

Following table present a summary list of all identified users.

Name

Description

Responsibilities

Stakeholder

Game
Player

Game Player is a key

user who plays this
game.

Purchase game.

User

- Play game.
- Provide feedback.

4. Business Model

Start
breaki
ng

Start
Game.
Level 1

Play

bricks.

Prevent
ball

Next
level.

from
falling

All
bricks
Broken.

You
won!

5. Functional, non-Functional requirements

S#

Functional Requirements

Types

None. Functional
Requirements

Category

FR
1

Player enters username.

HIGH

Display username in the middle

of screen.

Usability.

FR
2

Player selects level.

HIGH

Player can select level 1 only.

Load next in 1 sec.

Reliability.
Performance.

FR
3

Player breaks bricks through

ball.

HIGH

Scores must be stored in DB.

Technical.

FR
4

Player advances to next level.

HIGH

Display scores and lives.

Usability.

6. Use case diagram

7. Use case description

User case 1: Select level.
Table 1: Use Case 1

User ID:

User case name

Select level.

Created by:

abc

Date created:

March 15, 2015

Actor

Game Player.

Last updated by
Date last updated

xyz
May 31, 2015

Description

Game Player selects level to play game.

Post conditions:

Game Player plays game.

Pre-conditions:

Game Player must enter his/her username and has started the game.

Normal flow:

Actor
1. Game player enters
username.

System Response

2. System will display Menu of the

game.
3. Game player will select
level.
4. System will start selected level.

Alternatives
flows:

5. Game player will start

playing game
2a. System will let game player select the next level if prior level is
completed.

User case 2: Move paddle.

Table 2: Use Case 2

User ID:

User case name

Move paddle.

Created by:

abc

Date created:

March 15, 2015

Actor

Game Player.

Description

Game Player will move the paddle to handle the ball.

Last updated by
Date last updated

xyz
May 31, 2015

Post conditions:

Ball will bounce back to break bricks.

Pre-conditions:

Game Player must have started the game.

Normal flow:

Actor
1. Game player starts playing
game.
2. Game player will handle
the paddle movement.

System Response

3. System will bounce back the ball

towards the bricks.
4. If the brick breaks system will increase
scores.
Alternatives
flows:

2a. If ball is missed from paddle a live will be decremented.

User case 3: Show score board.

Table 3: Use Case 3

User ID:

User case name

Show score board.

Created by:

abc

Date created:

March 15, 2015

Last updated by
Date last updated

xyz
May 31, 2015

Actor

Game Player.

Description

Score board will be displayed to the game player by the system.

Post conditions:

Game Player will be advanced to next level.

Pre-conditions:

Game Player must have played the level and gained scores.

Normal flow:

Actor
1. Game player plays game.

System Response
2. System will generate scores.

Alternatives
flows:

3. Score are displayed to

game player.
1a. Game player didnt play game.

User case 4: Exit game.

Table 4: Use Case 4

User ID:

User case name

Exit game.

Created by:

abc

Date created:

March 15, 2015

Actor

Game Player.

Description

Game player can exit game by selecting Quit or by ending the three levels.

Last updated by
Date last updated

xyz
May 31, 2015

Post conditions:

Game will be terminated.

Pre-conditions:

Game player must open the game.

Normal flow:

Actor
1. Game player selects quit
game option.

System Response

2. System will terminate the game.

Alternatives
flows:

1a. Game player didnt select quit game option.

8. Domain Model

9. Data flow diagram

10.
DFD Level 3 Diagram

_____________________________________________________________________________________