Oral Presentation - Outline
Status
Version 0.7
No personal notes
Nearly complete
- The Risk Arena
- The Game
- Overview of Design
- Network Layer
- Graphical User Interface
- Risk Gaming Engine
- Computer Controlled Player (Robot) interface
The Risk Arena - History and Aims
- Started life when the Gauntlet was dropped
- Provide a means to play Risk on the computer against
- Human players on the same machine
- Human Players at a different machine
- Computer Players (robots)
The Game
- Board game for two to six players
- Played on a simplified map of the world
- The object is to occupy every country in the world
- Play is turn based
- Players battle with dice to take over new countries
Overview of Design
- Two Versions
- Application version (client and server distributed together)
- HTTP/Applet version (client and server distributed separatly)
- Divide and conquer approach
- GUI
- Risk Gaming Engine
- Network utilities
- Robot interface
Network Layer
- Remote Method Invocation (RMI) vs Streams
- Streams imply that communication is one way message based.
- Streams are usable in (almost) any language
- RMI is very simple to develop because comms can be two way.
- Uses interfaces
- No differentiation between local and remote objects
- CORBA is very like RMI but is language independant
Graphical User Interface
- Server Set Up
- Joining in
- Risk Game Board
- Implements the client interfaces
- Uses the server interfaces to send information.
Risk Gaming Engine
- Developed using a lightweight fusion method and Java skeletons
- Each user has a seperate point of input
- Uses broadcasters
- Implement the client interfaces
- Pass on all methods calls to multiple remote interfaces
Robot Interface
- Provides a means for robots to be developed and tested quickly (providing they are writen in Java)
- Provides a GUI to control admin tasks (joining a game, etc), leaving space for the robot to report information
- Does NOT provide a view on the game, the client has a spectator mode
Closing Remarks