Latest Design Issues

Need to come up with an idea of justifying the TimeDistanceSettings class. I think I have all the classes that are needed defined in a static as well as sequence diagramming form. There are some other classes that need further defining, but since those are sub-classed from already preexisting classes, most of their defining structure is already done. So, for those classes, much of the functionality can (and will be determined during implementation). I don't see that as a problem. I flirted with many ideas related to the Time and Distance objects about how to set up the units for the Distance class and the time format for the Time class. I considered defining a class that held enumerated types for both sets of data. Finally, I concluded the easiest thing to do would be to just set up booleans for the time formats and static integer values for the distance units. Although it is not as elegant as other solutions, I have a problem trying to figure out enumerated types in Java. They seen far too complex for my taste. So, I settled on to me is the simplest idea.