Assignment 5
COMP 106

For this project you will reimplement part of your Disasteroids game in three-dimensions using Java3D. Specifically, you will draw a spaceship, bullets, and some asteroids in 3D (don't worry about aliens). The action of the game can still take place in a two-dimensional plane, but the objects themselves should have depth. You can think of this as if the asteroids and spaceship were floating in a pool of water--the objects are three-dimensional, but they move in a 2D plane. Or, if you prefer, the action can take place in 3D--each object would then have a 3D position instead of 2D and could move in all three dimensions.

As before, you need not be restricted by what you did in the previous assignments, you can redesign your program at this point if you wish. You can also remove features that were in your previous assignments, to make this one easier to complete.

Continue to follow the object-oriented programming methodology we have been using (some of our design and programming practices are repeated below).

Program Design and Practices

(The rest of this still applies from previous assignments)

Your program design should exploit the features of object-oriented programming (encapsulation of code and data, support for abstract data types, polymorphism/overloading, inheritance). In particular, object-oriented programming provides us a good way to handle the various data needed in callback routines. You should use objects to encapsulate each interactive widget with the routines and data you need to use it.

You should provide an object for each interactive widget or small group of widgets you create. That object should hold anything you need to remember about the widget from one callback to another, all the data pertinent only to the command for that widget or that you need to operate this control, (including, in most cases, a pointer to the graph or other outside object to perform the actual action the user requested), and the widget's own listener callback routines.

If you have several widgets that share some behavior or properties, you should organize your objects into an appropriate inheritance hierarchy.

You will have other data that must be accessed by several widgets, particularly shared information about the state of the program or global information about the state of the user interface. Provide additional classes and objects for holding this kind of information.

Remember to trigger your drawing to repaint itself explicitly whenever one of your commands causes a change in the state of the graph that should be reflected on the screen. And remember that the way to change the screen is first to change the data stored in the Graph or other classes and then to trigger the repaint.

You should follow these general Java programming practices:

• Make all instance variables of your classes protected or private. If you need access outside of the class, provide it with set and/or get methods.
• Avoid global variables or widely-accessible public variables; pass the data you need explicitly.
• Put each class in a separate .java file.

And, finally, for uniformity please name your Java class that has your main program in it Main, in file Main.java

Design Documentation

• An outline showing the inheritance hierarchy
• An outline showing the aggregation hierarchy (which objects contain or own which other objects)
• A list showing uses or collaboration relationships (which objects use which other objects to perform functions)
• The information hiding secrets of each of your classes (i.e., what design decisions are entirely encapsulated within that class).

Submit this documentation electronically in text form. Include it as part of the readme file that you submit with your assignment.

Program Requirements

• Render your spaceship, asteroids, and bullets in 3D. This doesn't have to be fancy--spheres, cubes, and cones will suffice. (3 points)
• Allow the user to change the view perspective using the standard Java3D controls. (2 points)
• Your spaceship should be able to move and fire bullets using keyboard input. (1 point)
• Support collision detection as in the previous assignment. (1 point)
• Follows all guidelines in Program Design and Practices section (1 point)
• Present complete and clear design documentation (1 point)
• Adds something more--more features, or interesting uses of 3D. (1 point)

Note: one of the points of this assignment is to highlight the power of object-oriented design. If your last assignment was designed well, implementing many of these items should require little effort. Remember, this is still fundamentally the same game, it's just that the objects are drawn in 3D.