COMP 310 Fall 2011	Lec41: Game Issues and Sequence Diagramming

Today we will discuss the latest version of the WWJ map package, which features serializable objects.

A short demo of joining a team will be shown.

And outstanding game issues will be discussed:

• Do people stay in lobby after joining a team or do they leave when they join a team?  
  • If they are to leave, are they automatically put back into the lobby when the game is won? 
  • If they stay, nothing needs to be done.   The game server simply leaves the team rooms.
• How and when do you plan on starting a game?   Not everyone enters a team room at the same time.  
• "Taunting" support?

Word of advice:   Those who accomplish more, earlier, will have first dibs at suggesting and effecting common API changes that would naturally benefit their game the most!   Straglers will be forced to modify their code to accomodate other people's desires.

When trying to figure out how to accomplish a process in your system, carefully trace out exactly what packets are going to and from the server.    In class, we will trace through a sample transaction using a UML Sequence Diagram.

Sequence Diagram Resources:   (just pay attention to the basics, don't worry about the details!)

• http://en.wikipedia.org/wiki/Sequence_diagram
• http://www.agilemodeling.com/artifacts/sequenceDiagram.htm
• http://www.ibm.com/developerworks/rational/library/3101.html
• http://www.tracemodeler.com/articles/a_quick_introduction_to_uml_sequence_diagrams/

Scheduling coding and testing sessions?    Highly recommend at least 2 sessions before demo day!

© 2011 by Stephen Wong and Scott Rixner