OOppEnEnSSppaaCCee

LCA ProposalLCA ProposalCalvin ChinCalvin Chin

David CouvretteDavid CouvretteJung SonJung Son

Mikiko JamaMikiko Jama

CSE403 Summer 06CSE403 Summer 06

Operational ConceptOperational Concept

- OpenSpace is a collaborative art guessing game, in which - OpenSpace is a collaborative art guessing game, in which one player acts as an illustrator and the other players serve one player acts as an illustrator and the other players serve as his or her assistants. as his or her assistants. - The assistants attempt to guess what the illustrator is - The assistants attempt to guess what the illustrator is drawing in a short time frame, and get to alter the drawing in a short time frame, and get to alter the illustrator’s brush with a random selection of effects that illustrator’s brush with a random selection of effects that change each round.change each round.- Assistant gets points for guessing correctly, and so does - Assistant gets points for guessing correctly, and so does the illustrator (to prevent unmotivated illustrators)the illustrator (to prevent unmotivated illustrators)- Each round does not last longer than 2 minutes.- Each round does not last longer than 2 minutes.- After every round, a new person is selected as an - After every round, a new person is selected as an illustrator, so everyone gets a chance to draw.illustrator, so everyone gets a chance to draw.- After everyone has gone, scoring is tabulated and a winner - After everyone has gone, scoring is tabulated and a winner declared.declared.

System RequirementsSystem Requirements

- Coded entirely in Java using the standard - Coded entirely in Java using the standard Java librariesJava libraries- Stand alone client application- Stand alone client application- Clients need to be running JRE 1.5- Clients need to be running JRE 1.5

- Optional stand alone server application- Optional stand alone server application- Server needs to be able to handle - Server needs to be able to handle simultaneous games, with each game simultaneous games, with each game holding from 2-6 players.holding from 2-6 players.

System Requirements System Requirements

System Requirements System Requirements

System Requirements System Requirements

System Architecture System Architecture

Team StructureTeam Structure

Server/Network Team-David, Server/Network Team-David, MikikoMikiko

GUI Team-Jung, CalvinGUI Team-Jung, Calvin

-Once the high priority features are -Once the high priority features are done, all four of us will pool done, all four of us will pool together to integrate and produce together to integrate and produce the lower priority featuresthe lower priority features

TimelineTimeline

Week 1 , 2:Week 1 , 2:-develop Server/networking and GUI(client)-develop Server/networking and GUI(client)-Integration of both portions-Integration of both portions Week 3:Week 3:-refinement & adding already desired features-refinement & adding already desired features-release and gathering feedback-release and gathering feedback Week 4:Week 4:-refinement & adding more features based on -refinement & adding more features based on

feedbackfeedback Week 5:Week 5:-feature lock & final heavy testing -feature lock & final heavy testing

Test PlanTest Plan

J Unit testingJ Unit testingServer side tests:Server side tests:

- Multiple users connecting- Multiple users connecting

- Finding maximum users that the server can handle- Finding maximum users that the server can handle

- Running simultaneous games on multiple threads- Running simultaneous games on multiple threads

- Communication between clients via server- Communication between clients via server

- Listening for commands- Listening for commands

- Sending commands- Sending commands

- Keeping track of the game state (big suite of tests)- Keeping track of the game state (big suite of tests)

Test PlanTest Plan

J Unit testingJ Unit testingClient side connectivity tests:Client side connectivity tests:

- Connection to server- Connection to server

- Sending/receiving messages to and from server- Sending/receiving messages to and from server

- Interpreting messages accurately- Interpreting messages accurately

- Keeping in sync with other clients- Keeping in sync with other clients

- Listening for commands from the server- Listening for commands from the server

Test PlanTest Plan

J Unit testingJ Unit testingClient side GUI and media tests:Client side GUI and media tests:

- Synched brush effects between clients (a suite of - Synched brush effects between clients (a suite of connectivity and media tests)connectivity and media tests)- Accurate switching between illustrator and assistant mode- Accurate switching between illustrator and assistant mode- Switching between game browsing mode and game playing - Switching between game browsing mode and game playing modemode- Sound and music tests to assure that correct sounds and - Sound and music tests to assure that correct sounds and musics are playingmusics are playing- Brush effects are rendering in the right color, texture, and - Brush effects are rendering in the right color, texture, and behaving appropriately.behaving appropriately.

RisksRisks

- Custom Server/Client architecture is too- Custom Server/Client architecture is too difficult to difficult to implement in the timeframe given. However, current implement in the timeframe given. However, current tests of the built in Java libraries have lessened our tests of the built in Java libraries have lessened our worries over this risk.worries over this risk.

- Many graphical effects provided in - Many graphical effects provided in ggame may be too ame may be too difficult to implement. This is an area that still requires difficult to implement. This is an area that still requires more research for a better assessment.more research for a better assessment.

- - Feedback may indicate issues with core components Feedback may indicate issues with core components of OpenSpace gameplay, but we will not have time to of OpenSpace gameplay, but we will not have time to go back and redesign them. This is a risk that cannot go back and redesign them. This is a risk that cannot be assessed until about week 3 in our initial schedule.be assessed until about week 3 in our initial schedule.