Java Interfaces and UML

Implement the following class hierarchy on paper. You do not need to fill in the method bodies for the toss or bounce methods.

Answer the following questions:

• How are abstract classes and interfaces the same?
• How are abstract classes and interfaces different?
• Why does it generally make more sense to override the equals method than to overload it?
• Fill in the following table with one of three values.
  • ✓ An object of the indicated type could be stored in a variable of the indicated type.
  • X An object of the indicated type could not be stored in a variable of the indicated type.
  • — It is not possible to instantiate an object of the indicated type.

  		Variable Type
  		Tossable	Ball	Rock	Baseball	Football
  Object Type	Tossable
  	Ball
  	Rock
  	Baseball
  	Football

  
  
  
• Which of the following will compile (mark with a C)? Which of the following will execute successfully (mark with an E)?

  
  1.        Ball ball = new Football("spalding");
          
  2.        Ball ball = new Football("Spalding");
            Baseball baseball = (Baseball)ball;
          
  3.        Object obj = new Baseball("spalding");
          
  4.        Object obj = new Baseball("spalding");
            Tossable tossable = obj;
  
  5.        Tossable tossable = new Baseball("spalding");
            Object obj = tossable;