vdashneg diversity and square root board inc initial
play

Vdashneg, Diversity and Square Root Board Inc Initial Design and - PowerPoint PPT Presentation

Vdashneg, Diversity and Square Root Board Inc Initial Design and Intent of the Framework Architecture Interaction among teams. Interaction among teams. Testing Experience Plurals Demo RMI Service Create Start Game


  1. Vdashneg, Diversity and Square Root Board Inc

  2. � Initial Design and Intent of the Framework � Architecture � Interaction among teams. � Interaction among teams. � Testing Experience � Plurals � Demo

  3. RMI Service

  4. Create Start Game <ResponseMessage> <RequestMessage> <Game InstanceID =“100”/> <Operation Name=“Start”/> <More fields……> <RequestMessage> < ResponseMessage > RMI Service

  5. <ResponseMessage> <RequestMessage> <Game InstanceID =“100”/> <Game InstanceID=“100”/> <More fields……> <Operation Name=“Move”> < ResponseMessage > <Param Name=“Colum” Value=“1”> <RequestMessage> RMI Service

  6. Main Feature: � Decoupling of game development and UI development once a protocol of communication was agreed on communication was agreed on � We used RMI and java interface methods as protocol There was one change: � Communication from asynchronous to synchronous

  7. � Clear interfaces defined by Java interface. � Only clarification required was the type of commands being passed around. commands being passed around. � Minimal interaction was required between game team and framework team. � However…

  8. � The communication protocol was not clearly defined (web service? RMI?). RMI was chosen. � Generality of the framework was unrealistic Generality of the framework was unrealistic for the amount of development resource. � Some modification in framework was required to accommodate resource. Two players play on one screen.

  9. � What worked: � Initial meeting with all three teams. � Clear definition of interfaces. � What didn’t work: � Ideal, general framework is not realistic in terms of resource. � Critical path. Some teams depended on other teams to finish.

  10. � Unit testing required scaffold tests. � Difficult to automate test for the UI. Use of Selenium testing tool considered. Selenium testing tool considered. � System tests passed smoothly. Good coordination among teams. � Game plug-in bug found at UI system test (draw).

  11. � The below method did everything… processCommand (GameState gameState, Command c) � Behavior different according to instance of Command. Plural states can’t change states Command. Plural states can’t change states according to instance of Command. � Would require major refactoring to work around plural. � All teams needed to coordinate to make plural work, instead of using it as verification.

  12. Let’s play:

Recommend


More recommend