Software Requirements Specification for <Project>

Page 1

Software Requirements Specification

for

Links Barrel Blast

Version 1.0

Prepared by

Group Name: FlipAction Studios

John Ellis Jeremy LeBlanc Matt Slater <student #> <student #> <student #> Jellis4@spsu.edu Jleblanc@spsu.edu Mjsst108@mail.rmu.edu

Instructor: Dr. Jon Preston Course: Mobile and Casual Game Design

Date:

12/2/2013

Software Requirements Specification for <Project>

Page 2

Contents
Table of Contents
1 INTRODUCTION................................................................................................................................. 3 1.1 DOCUMENT PURPOSE ..................................................................................................................... 3 1.2 PRODUCT SCOPE ........................................................................................................................... 3 1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW ............................................................................... 3 1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ................................................................................... 3 2 OVERALL DESCRIPTION................................................................................................................... 4 2.1 PRODUCT FUNCTIONALITY ............................................................................................................... 4 2.2 USERS AND CHARACTERISTICS ......................................................................................................... 4 2.3 OPERATING ENVIRONMENT .............................................................................................................. 4 2.4 DESIGN AND IMPLEMENTATION CONSTRAINTS ..................................................................................... 4 3 SPECIFIC REQUIREMENTS ............................................................................................................... 5 3.1 EXTERNAL INTERFACE REQUIREMENTS .............................................................................................. 5 3.1.1 User Interfaces ...................................................................................................................... 5 3.1.2 Hardware Interfaces ............................................................................................................... 5 3.1.3 Software Interfaces ................................................................................................................ 5 3.2 FUNCTIONAL REQUIREMENTS ........................................................................................................... 5 4 OTHER NON-FUNCTIONAL REQUIREMENTS.................................................................................... 6 4.1 PERFORMANCE REQUIREMENTS ....................................................................................................... 6 5 OTHER REQUIREMENTS ................................................................................................................... 7

Software Requirements Specification for <Project>

Page 3

1 Introduction
Links Barrel Blast is a mobile game made for Android devices. With a simple one time purchase the User will be able to play this game anywhere and anytime from their Android device. The objective for the game is to launch Link from a catapult and earn money for upgrades. The character Link is taken from the Nintendo GameCube series The Legend of Zelda: Wind Waker. With a cartoony appearance we hope to attract not only existing fans of The Legend of Zelda, but also help encourage the new generation in learning about a classic game series. In addition to just having fun and launching Link, the game will keep track of the Users highest score (farthest launch). It will help encourage the User to stay ahead of their friends and family who also have the game.

1.1 Document Purpose

The purpose of this SRS document is to help keep this development group on track for goals and regulations that will be applied in the game. It is also to encourage any potential buyers/investors that will want to help produce, advertise and sell this product.

1.2 Product Scope

First and foremost, the game is to be designed originally for any and all Android devices. The original intent of the game is to provide any Users that purchase the game a quick and fun pastime. The first goal in production is to have appropriate assets and a functional menu to help introduce the game and draw in users that might be interested in playing the game. Secondly, without precoded physics on the Android SDK, our goal is to have simple, realistic looking physics that will make the game appear smooth and professional. After the initial launch and physics, the game is to have randomly generated pickups and obstacles that will either help Link travel further or hinder is progress.

1.3 Intended Audience and Document Overview

The initial audience is for anybody who has played any of the Legend of Zelda series. Other intended audience is for anyone 5+ years. The game is not violent other than Link hitting obstacles. With this in mind the game is intended for anyone from the ages of 5 years to early 30s.

1.4 Definitions, Acronyms and Abbreviations

The Legend of Zelda: TLOZ Ocarina of Time: OOT Wind Waker: WW Operating System: OS Software Development Kit: SDK Megabit: MB

Software Requirements Specification for <Project>

Page 4

2 Overall Description
2.1 Product Functionality
* Deployment of game to all Android devices. * Allows the ability for touch screen capabilities, thus the player must have an Android device that allows so. * The ability to save high scores and share with friends, family and even any other user possessing the game. * Buying upgrades to help further the players score.

2.2 Users and Characteristics

Users from ages 5 to early teens we hope to help introduce the Legend of Zelda series to help promote its popularity and continuation. Younger children will want a game to play while waiting for the bus or while bored at home. The goal is to have a game you can pick up for as short as a minute or two. Older Users who know about the Legend of Zelda series will likely purchase the game due to respect and favoritism towards the Legend of Zelda series. The oldest users will most likely buy the game for their children to play while they are on trips or errands.

2.3 Operating Environment

The game is meant for short and long term play. It can be used anywhere as long as you have the appropriate hardware. The game will be developed for Android devices. The original development will be made for Android version 16 and higher. The Android SDK version 16 allows for publication on Android phones, tablets and even deployment for the web.

2.4 Design and Implementation Constraints

The limitations include the ability for deployment to all Android devices but only with versions of the Android operation system higher or equal to version 16. The publication of the game is for Android devices with touch screen capabilities only. Memory will only consume no more than 20MB on the device, but will allow the ability to save to external storage devices such as SD cards. Original production will only be available in English; release internationally has yet to be discussed.

Software Requirements Specification for <Project>

Page 5

3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces The main menu screen will consist of several options. On the main page when the game is first launched the User will be able to interact with three buttons. The first button is to launch the game. The second button is to view High Scores among friends, family and other users who possess the game. The third button allows the User to view the help screen. The help screen allows the player to review the controls and purpose of the game. When the game has started, the player will have the ability to mute the Background music and sound effects. Other In-game buttons allows the User to visit the In-game store. On the store page, players will be able to purchase upgrades to help further Links launching distance. 3.1.2 Hardware Interfaces The only difference between devices is Resolution and Processing speed. With a more upgraded device, the processing power will be faster than older devices. This doesnt directly affect the playing ability between Users. Resolution is set differently for different devices. With larger screens, the pictures may appear more pixilated. With lower resolution screens, pictures may appear squished or stretched. 3.1.3 Software Interfaces Difference between Operating Systems is limited. As long as the user has and Android device with version 16 or higher, they will be able to play this game. Having new versions of the Android operating system will not allow any different gameplay, however, Users with Android versions lower than 16 will not be able to play this game.

3.2 Functional Requirements

< Functional requirements capture the intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform. This section is the direct continuation of section 2.1 where you have specified the general functional requirements. Here, you should list in detail the different product functions with specific explanations regarding every function. Use the bullet format defined below [FR - 1]: [FR - 2]:

Software Requirements Specification for <Project>

Page 6

4 Other Non-functional Requirements

4.1 Performance Requirements
<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. If possible provide different performance requirements based on the information you collected from the client. Example A database query shall not take more than 15 seconds> [NR - 1]: [NR - 2]:

Software Requirements Specification for <Project>

Page 7

5 Other Requirements
<This section is Optional. Define any other requirements not covered elsewhere in the SRS. Add any new sections that are important to the project.>

[OR - 1]: [OR - 2]:

Software Requirements Specification for <Project>

Page 8