UMLDesigner is one of these unloved children (ObjectExtender seems to be the other one) - nobody really cares about
.
I used RationalRose (some years ago) and there the main work is done by drawing of diagrams: first are the diagrams, then comes the rest. And this is what the general users expect. You draw a diagram, then create the source code and then: ready. Very fast. Even in the .NET world this is the expectation.
UMLDesigner is completely different and this makes the life harder for the user. In the world of the UMLDesigner the specifications come first and then - for documentation purposes only - come the diagrams. The tools is based on the idea to describe the solution in detail via text (and later in addition in diagrams - and connect them via links) and this tools leads you towards the specification of classes and interfaces. What a pity, that interfaces are not available in Smalltalk and VASmalltalk - the tool guides you to interfaces - a thing, that the main target language (Smalltalk) actually does not support.
UMLDesigner is not a tool for fast turnaround programming. The GUI shows its ages - as the Report feature's GUI.
But after all drawbacks: it's the best what we have now and it is integrated within VASmalltalk (and ENVY/QA), which is a big plus. I do not need UML (I know, larger companies do need that - or they think, that they have to need that), but I would like to see a specification tool, with a much better code generator - perhaps even for other languages.
I wrote my own specification tool for our C# project (in Smalltalk) and it was designed (though without diagrams) to build classes pretty fast. The longer we are developing our C# system I would like to have UMLDesigner to write down more textual specifications for our model and a more interface oriented design.
I'm still thinking to put some work on this tool to make it more suitable for me:
* extract the code generation out of this tool into an own tool with language specific extensions (Smalltalk and C# and perhaps relational database support)
* extend the reporting services by integrating my OpenOffice wrapper into the ENVY/QA documentation suite.
* extend the format of the first comment of a compiled method to define actions, parameter specification, return values and perhaps exception - as the programmer did with some success in the SST framework.
With these ideas the UMLDesigner might be a good start ...