David Vallner wrote:

> For purposes of maintainability, UML is a more terse documentation
> artefact for some views of a system than source code documentation.

It would be interesting if it were possible to generate UML from ruby 
source and/or execution traces. Like RDoc's use of graphviz/dot to 
generate class hierarchy diagrams, but more comprehensive. Or like 
ruby-prof's call graph generation.

That would be useful for communication and understanding, though code -> 
uml is opposite to the more usual uml -> code direction.

I prefer to use metaprogramming in ruby rather than UML to express high 
level concepts in code, but as you say some kinds of communication need 
boxes and arrows....

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407