the point i am making is that ramping up to development from the pre-production stage is possible from properly laid out uml diagrams
i find problems in uml's how-to's in describing perl objects.
I guess i could reverse engineer some perl objects to see how it should look!
Again , i do think UML's main purpose is to help in pre-production, but i also think it can provide a useful linkage to production, helping a developer set up the perl modules for a project, wasting less time in setting up for the development stage
It also helps in post and in production systems. When a system breaks or needs to be maintained, jumping into someone's code isn't easy. With various UML diagrams, it's really easy to at least know what relates to what.