Difference between revisions of "Software Architecture Document (Golf App)"

From Secure Computing Wiki
Jump to: navigation, search
(Created page with "== About this document== This document provides a basic architectural overview of the product, summarizing the key architectural issues and the solutions that have been decided ...")
 
Line 29: Line 29:
 
see [[Use Cases (Golf App)]]
 
see [[Use Cases (Golf App)]]
  
{{AgileProcessforAndroidGameFooter}}
+
{{CapstoneFooter}}

Revision as of 14:10, 23 May 2011

About this document

This document provides a basic architectural overview of the product, summarizing the key architectural issues and the solutions that have been decided upon. In other words, it is intended to capture and convey the significant architectural decisions which have been made for this game. Logical, Deployment and Process Views may be added later.

Architectural Factors & Decisions

Overview

Overview and development environment: The Laser Chess game will be built using the Eclipse Editor for the Android Market since all users of Android Phones will be able to use the Android Market as it comes preinstalled on the devices that will run our game

Issues in core program that have been decided

We have determined that:

  • the four different pieces will have the majority of information stored in a piece object that will be the parent object
  • the board will have the information for which pieces are on which squares and which square is which color


To be considered

Important aspects of the architecture include the ability to run 100k players at anytime peak load and the game must run with minimal bandwidth as per the Non-Functional Requirements. Solution will be worked in later iterations in the interests of getting a working product to market faster without this feature.

We also need to be able to have the AI be challenging enough to be something a human player will have trouble beating, but easy enough so that a human player can beat an AI player. Solution will be worked in later iterations in the interests of getting a working product to market faster without this feature.

The pieces have some special move types, as defined in the Game Rules and Glossary. These need to be accounted for when coding each piece and the board needs to be able to handle more than one piece on a square at once.

Use-Case View

see Use Cases (Golf App)

Project Topics

Reference Material