Brother, I don't understand. I mean, certainly you are entitled to your opinion. But isn't one of the precepts of programming that you do your planning properly up front?

In (my) reality, object relationships change.

If you take the time to plan out your project from the beginning, you should be able to reduce the amount of coding time, by skipping the "throwaway" prototype phase. Are you talking about their relationships changing with subsequent versions or during the initial development cycle?

I mean I suppose it depends on what you're doing. CGI's for example, benefit very little from UML, but then I don't write CGI's using OOPERL. That's just me...

I don't know that a project has to be very big to benefit from a decent UML tool either. I for one, mostly use UML to build code skeletons for Java. I was thinking that it might be nice to have a tool that could do the same for me in PERL. That's all. Call me lazy, but laziness can be a virtue too.