Your instructor will assign one or more of the following problems. Submit all appropriate files for grading, including code files, screen captures, supplemental files (e.g., image files), and text files.

1. Design and build a class hierarchy for media types. Your hierarchy should support Books, Periodicals, DVDs and CDs. Some attributes for these kinds of objects include: title, author, ISBN number, subject, running time, volume number, rating, and lending length. Store each of these attributes in the appropriate place in the hierarchy and override the toString() method of each class in an appropriate manner.

   Write a program that creates an array of media types and uses that to demonstrate the correctness of your design and implementation. One way to do this would be to write a CLI driver that does the following:

   • Create an array of media type objects.
   • Load that array with media objects of various types. You can just hard-code this as you did with the PointComputation objects in the lab exercise.
   • Loop through that array, printing out the text representation of each of the media objects.

2. Design and build a class hierarchy for shapes. Your hierarchy should support circles, ovals, triangles, right triangles, squares, rectangles, quadrilaterals. Each class should have appropriate attributes in order to be able to determine: the smallest rectangle that bounds the shape, the area of the shape, the circumference of the shape, whether a point is inside the shape, and whether two shapes bounding rectangles intersect.

   Store the hierarchy in a package and then write a program that creates an array of shape types and uses that to demonstrate the correctness of your design and implementation.

3. Design and build a class hierarchy for types of vehicles that can be used by a travel agent to build trip itineraries. Your hierarchy should include cars, airplanes, rental cars and bicycles. Here's an example of the output for a 4-step itinerary:

   Business trip for Brenda Doe:
   1. Drive to GRR airport.
   	Volkswagon Golf	10.0 miles	0.20 hours
   2. Fly to OHR airport non-stop.
   	Boeing 777	200.0 miles	2.40 hours
   3. Fly to RNO airport non-stop.
   	Airbus A319	2000.0 miles	5.81 hours
   4. Drive to Lake Tahoe.
   	Jeep Commander	55.0 miles	1.60 hours
   Total Distance: 2265.0 miles 	Total Time: 10.01 hours
   Have a safe trip.
   

   This output can be generated using the following pre-built classes:

   • CLI driver: TripCLIDriver.java
   • Trip class: Trip.java

   Start with these two classes and add the following classes:

   • Leg Class: This class models a single leg of the trip (see the four numbered legs in the sample output above).
   • Vehicle class hierarchy: This set of classes models various sorts of vehicles.

   Note the following things:

   • The Leg class must implement the methods used in the given Trip class (i.e., getDistance(), getTime(), toString()).
   • All vehicle objects must implement the methods used in the given CLI driver and Leg class (i.e., getName(), getTime(), getDescription()).
   • In general, the time estimates are computed using distance divided by speed, but airplane legs add 2 hours (for check-in and security) and rental car legs add 30 minutes (for check-in).
   • Different vehicle types produce different descriptions. You can see some of the differences in the example above. Here are two more examples that you should support (note the comments - bicyclists are encouraged to consider driving if it is icy and personal car drivers are encouraged to bike if the distance is less than 8 miles):

     Daily commute for Keith Doe:
     1. Bike to the office.	(Consider driving if icy.)
     	Trek 730	3.0 miles	0.15 hours
     Total Distance: 3.0 miles 	Total Time: 0.15 hours
     Have a safe trip.
     
     Daily commute for Keith Doe:
     1. Drive to the office.	(Consider bicycling.)
     	Volkswagon Golf	3.0 miles	0.06 hours
     Total Distance: 3.0 miles 	Total Time: 0.06 hours
     Have a safe trip.

   • You should think carefully about what leg objects “know” about themselves as opposed to what vehicle objects “know” about themselves. This will help you distribute the features between the object classes appropriately.