destiny team mailing list archive

[Zach Elko <zachelko@xxxxxxxxx>]

*Zach/Doug - Battleship/Frogger/Installer*

Some things off the top of my head (not a complete list):

   - Frogger needs to start using a state machine to transition between
   different game modes properly
   - In-game menus for both games
   - Battleship needs to start making use of the question manager
   - The HUD in Battleship needs to be click-able so that they can select
   which question to attempt
   - All of the game logic for Battleship needs implemented (shouldn't be
   much, though)
   - Ways to install the games need to be explored, tested, and tweaked
   - Various bug fixes listed in the tracker

*
Ian/Tom - Sleuths*

Some things off the top of my head (not a complete list):

   - All of the menu functionality needs to work. This includes logging in,
   avatar creation/editing, scenario selection, returning to the main screen,
   etc...
   - Tool selection needs to be implemented
   - Tool interaction needs to be implemented
   - Hints need to be gathered and recorded by the game
   - Various bug fixes listed in the tracker



*Andy - Bug tracking, Building levels for Frogger, Making question sets for
Frogger and Battleship*

Some things off the top of my head (not a complete list):

   - Keep hammering away at all applications to find issues, or to come up
   with suggestions for improvement
   - Using Doug's level builder, create levels for Frogger with varying
   enemies and backgrounds
   - Using Doug's question manager and the text book(s) for the course, come
   up with some applicable question sets for both Frogger and Battleship, in
   both Math and English. I advise starting a thread to the list to discuss how
   we want to attack the English questions and such. It'll be a group decision,
   but you're responsible for making sure it gets done.


*General Stuff*

   - All classes need UML
   - Updating old classes means updating their UML
   - All classes need unit tests (always! we're graded on this!)
   - If you can help someone else out, do so.
   - Don't disappear. Volunteer your services, ask for help, offer
   suggestions, file bug/suggestion reports, etc... There is *always* something
   you could be doing.


Zach J. Elko
Ball State University Unified Technology Support
Certified Hardware & Software Technician