COMP 310
Spring 2010

Final Project

Home  Info  Owlspace  Resources

The final project combines the technologies developed in the Ballworld and Chat App systems.

Students will be allowed to work in pairs for this assignment whose final product will be due on the last day of exams, though we will probably have a "game day" prior to that.

Minimum requirements:

For inspiration, you can look at the "GalaxyBall" project from the 2007 Comp202 final project:

The specifics of the final project's API and requirements will be posted in the Owlspace Wiki and Resource pages.

Milestone requirements:

For all milestones, ALL partners should submit IDENTICAL work to Owlspace and the SVN turn-in repository.  Always include a README.txt file that lists all partners names.    For Owlspace materials, please zip up all work into a single file for submission.

Milestone 1:

For this milestone, you and your partner, if you have one, need to show that you have a well-thought out, coherent design ready for implementation.

You will need to submit the following to Owlspace (zipped up into a single file please):

  1. UML diagram of the interfaces and implementing classes

  2. A prose description of how your design will implement the required common API as well as any features specific to your implementation.   The above UML diagram may be imbedded in this document if desired (recommended!).   

  3. Javadocs for the classes and interfaces in the UML diagram.   A minimum detail level of class/interface and method descriptions is required.   Descriptions of fields and input parameters is recommended but not required.   The Javadocs should be in the form of HTML web pages so they can be easily read, not just the comments in the code.

  4. The submitted code should have a minumum functionality of being able to connect to other users plus any agreed upon functionality as detailed in the final project wiki.

Milestone 2:

For this milestone, you will submit your fully operational code plus full documentation.  The submission requirements are:

  1. Documentation:

    1. Fully detailed and accurate UML diagram and operational description from Milestone 1 with any changes and additions as were done since then.

    2. Full Javadocs, this time including descriptions for all methods with input parameters and all fields.

    3. A user's manual that describes at least:

      1. How to start the program, both the program itself as well as any individual games or processes.

      2. How to connect to other users

      3. How to use every feature of the program. 

      4. How to end and exit the program.

  2. Fully operational code should be committed to the SVN turn-in repository.



© 2010 by Stephen Wong