Group 10
Detailed Design
COP4331C, Fall2014
Modification history:
|
Version |
Date |
Who |
Comment |
|
v0.0 |
10/22/14 |
Michael Paulsen |
Rough Draft |
|
... |
|
|
|
Team Name: Group 10
Team Members:
Contents of this Document
Trace of Requirements to Design
Firstly, performance and usability on the native platform is a major concern.
The application is being developed across UNIX and Windows based workstations that simulate the target
Android environment for the application. As this type of operating system emulation is never fully accurate,
there exists concerns that the performance and test results observed during testing conducted on the development
machines will not accurately prepare the application for native execution on the Android platform. The software
may experience significant performance hitches, or in an extreme case, may experience fatal errors that were not
experienced during development testing. This will require a back-and-forth series of tests between the development
and native environments that will result in a longer testing phase.
Secondly, the control interface for the application will be drastically different between the development and
native environment. In the development environment, the control interface involves a mouse and keyboard that
is not present in the native environment which will be utilizing an on-screen directional pad and buttons.
This adds further importance to the native environment testing process as any changes that affect the control
interface might fail to carry over.
Specific Requirements:
The software is a two-dimensional top-down shooter for the Android platform that features
a single player character that has an inventory, equipment, and weapons. The player gains
experience points used for character development as the player defeats various enemies and
progresses through the levels.
The game will have a main front menu with selections for game mode, character select, and
options. The game mode selection will branch into the options of starting a new game or
resuming from a previous save. The character select option will offer a choice of characters
for the user to select from, and also offer a character customization sub-menu.
The player character will have an integer represented level associated with it. Through defeating
encountered enemies and progressing through the levels, experience will be accumulated causing that
level value to periodically increase.
The character controlled by the user will be selectable and customizable from a character select screen.
Choosing different character will change the visual appearance of the character controlled by the player.
In addition to customizing the character appearance, there will exist an inventory system from which
the player can select weapon and equipment items that will affect the mechanics of the character.
The weapons and equipment involved with the inventory system will be acquired through an in-game merchant NPC mechanic.
The merchant NPC will be located within the levels where it can be discovered by the player, and the player will be
able to interact with the merchant then.
There will be multiple maps (or levels) through which the player will progress. Upon reaching the end of one level,
the player will progress onto the next until the final level which will terminate in a game over state with a score displayed.
The previously mentioned score will be the result of a scoring system that accumulates points for various accomplishments
and interactions throughout the course of the game. This score will be a quantified indication of the player performance
throughout the game.
Trace of Requirements to Design:
SRS Requirement 1: Leveling
SRS Requirement 2: Inventory
SRS Requirement 3: Merchant
SRS Requirement 4: Character Select
SRS Requirement 5: Maps
SRS Requirement 6: Score
Template created by G. Walton (GWalton@mail.ucf.edu) on October 8, 1999 and last modified on August 15, 2000
This page last modified by Michael Paulsen on 10/22/14
Displaying DetailedDesign.html.