Iteration 3 -- Planned

• Single player, turn based game working.
  • GUI displays status messages (Controller, GUI).
  • GUI displays menu of choices (Controller, GUI).
  • GUI handles key press on phone interface (Controller).
  • Turn on Phone (Model, Controller, GUI).
  • Game starts (Model, Controller, GUI).
    • A piece settles
    • A player clears a line (or multiple lines)
    • Player's pieces reach top of board.
  • Game over (Model, Controller, GUI).

Iteration 3 -- Completed

• Single player, turn based game working.
  • Console displays status messages (Controller, GUI).
  • Console displays menu of choices (Controller, GUI).
  • Key presses on phone simulated through text menu (Controller).
  • Game starts (Model, Controller, GUI).
    • A piece is placed
    • Player's pieces fill the board.
  • Game over (Model, Controller, GUI).
  • Differences from Iteration 2 plan:
    • A single player game works, but there is no GUI yet. All input and output is through the console. Also, the game implemented is not Tetris, but BlockFill.
• Bluetooth device/service discovery and communication implemented as client and server threads. Network tests pass under ideal setup.
  • Differences from Iteration 2 plan:
    • In the previous iteration plan we didnt mention bluetooth implementation, but considering integration of the packages, we decided to implement one of the connection type in iteration3, and we chose bluetooth to implement.

Iteration 4

• Single player, turn based game working with GUI. The plan is to complete the implementation of BlockFill. (6 DDUs)
  • GUI displays status messages (Controller, GUI).
  • GUI displays menu of choices (Controller, GUI).
  • GUI handles key press on phone interface (Controller).
  • Turn on Phone (Model, Controller, GUI).
  • Game starts (Model, Controller, GUI).
    • A piece is placed
    • A player fills the board
  • Game over (Model, Controller, GUI).
• Single player Tetris model working. (5 DDUs)
  • Version of Tetris that can be played through console input and output (no GUI).
    • A piece settles.
    • The player clears a line.
    • Game advances to next level.
• Network setup working. (4 DDUs)
  • Player can find others who want to play the game.
  • Players can send messages back and forth.
  • Implement IR communication

Iteration 5

• Two player, real-time Tetris workng. (10 DDUs)
  • Connection is made.
  • Real-time game status update messages exchanged (Controller, Game, Network)
    • Player chooses to host game (Controller, GUI, Network).
    • Player chooses to join game (Controller, GUI, Network).
    • Game setup, starts (Model, Controller, GUI, Network).
    • Game status update messages exchanged (Controller, Network)
    • A player receives a clear line signal from other player. (Controller, Network, Model)
• Battleship model working. (4 DDUs)
  • Players place their ships. (Controller, Model)
  • Player hits opponent's ship. (Controller, Model, Network)
  • Player sinks opponent's ship. (Controller, Model, Network)
  • Game over. (Controller, Model, Network)
• Game Skin Browser. (4 DDUs)
  • Player opens browser for available skins (Controller, GUI, Network).
  • Player selects available skin (Controller, GUI, Network).
  • Player downloads new skin from remote web server (Controller, GUI, Network).

Iteration 6

• BlockFill and Tetris code debugged and polished. (2 DDUs)
• Battleship working entirely. (6 DDUs)
• GUI displays game status. (Controller, Model, GUI)
• Players communicate as game proceeds. (Controller, Network, GUI, Model)
• Documentation completed.(2 DDUs)