Comp405: Final Project

COMP 405/505 Spring 2016	Final Project: Cloud Games

Subject to Change! Check back often for the latest version!

Description

Each team will make a Google App Engine application that

Enables a "player" to connect and to be presented with a set of valid operations the player could perform.
- Certain operations result in the accrual of "value" for the player.
- Certain operations may result in the player connecting with a different team's application.
- Certain operations may affect the operations and values available to other players.
- A time limit is imposed on how long a player has to select an operation to perform.
A service is provided that enables a player to find out where every other player is and their accrued values.
A service is provided that enables a player to "play as another player" such that no permanent mutations are performed.
The application must participate in a cross-application turn control mechanism.

Must use the following technologies somewhere in the application:

Must be able to

System should be

At least the two following player modes or player types must be available:

Role	Responsibilities	Notes
Team Leader	Overall team direction Task assignment	Needs to look down the road and anticipate what is coming up next for the team. Make sure that conflicts between team members is minimized, e.g. not working on the same classs at the same time.
Recorder	Making sure that all documenation is created Organization of all written deliverables	Should NOT be the sole author of the written materials! Delegate, delegate, delegate!
Technologist	Researching any required technologies and techniques Creating proof-of-concept test apps	Remember that it may take some time to get certain technologies under control -- plan for this!
Tester	Unit tests of system objects Test processes for the overall system	Test early, test often and make sure that you have 100% code coverage. Testing early will enable you to provide feedback to the rest of the team on how well certain sub-systems actually work.
System Architext	Overall system architecture System block diagram, including use cases UML diagrams	Needs to work hand-in-hand with the team leader. Clear system architecture is critical for unambiguous planning and tasking.

"Responsible for" does NOT equal "Does it by themselves"!

20%	ALL participants fully functional (player and game server)
10%	Individual role execution (based on documentation of what each person did during the development process)
35%	Functionality (player & server functionality, interoperability, architecture and design)
25%	Individual Team Documentation (completeness, clarity).
5%	Group API Documentation (completeness, clarity)
5%	Individual Team Innovation (architecture, design and/or game concepts)