Project team

ng Minh Cng 11020033 K56CA Mai Cng t 11020067 K56CA

Problem statement
Game in Android. Genre: 2D Platformer game The game must allow player to play the game, save and load the progress at any time, have score system to rate player performance, ability to player with friend over wireless. The requirements are: 7 inch Android tablet or better, Android version > 2.2. Gameplay: The game will be divided into stages. The player control a character jumping over obstacles, defeat enemies, reaching end goal to finish one stage. Player character will loss a life when collided with enemies or lethal obstacles or falling down into bottomless pit. In order to defeat an enemy, the character must jump into the head of enemy. Player must finish a stage in order to play the next stage. At any point in a stage, player can choose to save his progress in order to load later. Score will be rated according to how fast the player finish a stage. Additionally, for each enemy player defeat, there will be bonus point. Each time the player dies, score will be deduced. Player will be able to view the list of scores in main menu. Two players can connect their tablets over wireless to take part in a VS battle.

Glossary
Player The person who play the game (user of program) Save Store the progress of player Load Return the player to exact state when he save the game Score The number which rated the performance of player Character The avatar in-game, which the player control 1

Enemies The objects in-game which are hostile to the character and can move. Obstacles The unmoving object in-game which the character cannot pass Lethal obstacles The obstacles which can harm the character. Stage A part of the game. Consist of the world, obstacles and enemies. The world Consist of lands which the character can stand and walk on. Bottomless pit The part of world which doesnt have land below. Main menu The first menu which player see when the game start. Character lives How many times player can retry. If it reached zero, player cannot retry anymore.

Supplementary specifications
Objectives This Supplementary Specification lists the requirements that are not readily captured in the use case of the use-case model. Supplementary Specification and the use-case model together capture a complete set of requirements on the system. Scope This Supplementary Specification applies to the Android Game, which will be developed by OOAD students. This specification defines non-functional requirements of the system; such as reliability, usability, performance and supportability, as well as functional requirements that are common across a number of use cases. (The functional requirements are defined in the Use Case Specification). Functionality 2

The player can save game in any time. Usability The Game must be easy to use so that a new player can learn how to play the game within 10 minutes. This is very important requirement. The menu has to be nice and clear. Reliability The game can run without hanging. Performance The game can run without lagging (minimum 30 fps). The GUI transitions must be smooth.

Use case diagram

Save Game
Brief Description This Use case describe how player save the game. Flow of events This Use case start when actor player wishes to save the game.

1. Pause the game 2. Choose Save function Relationship None Activity diagram