View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Fall 2004 Final Exam Review: OO Design Evaluation

a. This class is the main class and handles many of the tasks.

b. We named the Warehouse class Ware becuase it is easier to type.

c. We are getting tons of code written becuase there are things we can just copy from similar classes.

d. We had one class inherit from another because the one class needed to access some information in the other class, but we had a problem that some of the inherited methods didn't make sense so we overrode them.

e. We have a type attribute in the Payment class and then we case (switch) on the type to handle billing by credit card, purchase order, create a bill, etc.

f. We put most of the code into class methods and that way we don't need to create objects to do the work.


f. We put most of the code into class methods and that way we don't need to create objects to do the work.

WHY!? PMD WOULD THROW A FIT! The classes should either be made Singletons, if the design truly matches that, or the design needs to be rethought out. The use of class methods for everything can lead to big trouble when dealing with instance variables.


Link to this Page