Group 10
High Level Design
COP4331C, Fall, 2014
Modification history:
Version |
Date |
Who |
Comment |
v0.0 |
10/22/2014 |
Horica Ionenscu |
Rough Draft |
v0.1 |
10/22/2014 |
Adam Stack |
Made changes for final draft. |
... |
|
|
|
Project Name: 2D Action Shooter Team Members:
Contents of this Document
The main object components will be the player, the enemies and the merchant. The player will be under user control and will be able to move up, down, left and right. He will able to toggle through and use several different weapons (see weapons section for more details). The player will also have a health status, which will be effected by the enemies. He will also be able to purchase items from the merchant. The enemies will also be able to move up, down, left and right. They will be able to inflict damage to the main player’s health. There will be several different types of enemies. The merchant will be located somewhere along each level. When the main player interacts with the merchant, a menu will show up on screen where items and weapons may be purchased.
The map will be where the game takes place. For each level in the game, the player will move from one end of the map to the other, battling enemies along the way. The map will contain different textures and boundaries where the player cannot move past. Somewhere along the map there will be a merchant.
The issues relevant to our project include testability and performance. One of the main concerns is how the game will perform once we implement it on an android platform. The main testing will take place on laptops, though there are possibilities of differences in gameplay once it is played on an android device. These issues will be tackled systematically if they do come up, though this will be further along the development process. The first step in testing these issues would be to create a prototype. One of the concerns would be getting the onscreen buttons to perform properly. There could be other unforeseen issues that pop up as well. The idea is to get a prototype early in the development process, so any issues get dealt with early. How the problems will be solved will depend entirely on the nature of the problems themselves. Not all of these issues can be anticipated beforehand. The strategy in making these problems easier to solve is to attack them early on.
Template created by G. Walton (GWalton@mail.ucf.edu) on October 8, 1999 and last modified on Aug 15, 2000
This page last modified by Adam Stack (bigstack80@knights.ucf.edu ) on 10/22/2014