Anyone have any recomendations for drawing UML diagrams, specifically class diagrams.Am using UMLet at the moment, which is ok, but not great. A lot of the stuff I've seen seems to want to do your code for you as well in some way or other, whereas I just want to document software. An extention to word shapes would be good, but have never seen anything like that.

QuoteOriginally posted by: MikeCroweAnyone have any recomendations for drawing UML diagrams, specifically class diagrams.Am using UMLet at the moment, which is ok, but not great. A lot of the stuff I've seen seems to want to do your code for you as well in some way or other, whereas I just want to document software. An extention to word shapes would be good, but have never seen anything like that.MikeI was wondering when you would ask this question When using patterns one needs UML.This might be a start.UMLCASEBTW my company uses MS Visio, works fine but costs a bit ($800 roughly)

If you like Word shapes, you might like Visio which I prefer to most dedicated UML tools, but that's my taste.If your firm has the BFO version of Visual Studio or MSDN, ought to be lying around.

Dia is an open-source drawing program with some UML functionality.

A modest proposal...Instead of communicating in text-based language (English, C++, matlab), impart your design intent using UML diagrams (just like CAD, MCAD).Other disciplines have been doing it for centuries

UML's all well and good, but you can't beat a flow chart IMO for that 'a picture paints 1000 words' factor.When a UML diagram requires an A3 piece of paper in order to be printed there's only so much of it you can take in.

QuoteUML's all well and good, but you can't beat a flow chart IMO for that 'a picture paints 1000 words' factor.UML uses Activity Diagrams for flow charts .. it's a de facto standard and precise while flow charts - which originate in the 70's - tend to be ambiguous and imprecise. In fact, Component Diagrams are the bees knees these days...Are you associating UML with class diagrams only?QuoteWhen a UML diagram requires an A3 piece of paper in order to be printed there's only so much of it you can take in. Then break it up into loose subsystems before you daw it in Visio or Rose. The problem in not UML but more a sign of a weak design. // Our inability to process too much information is a fact, as here:The magic number 7

QuoteOriginally posted by: CuchulainnQuoteUML's all well and good, but you can't beat a flow chart IMO for that 'a picture paints 1000 words' factor.UML uses Activity Diagrams for flow charts .. it's a de facto standard and precise while flow charts - which originate in the 70's - tend to be ambiguous and imprecise. In fact, Component Diagrams are the bees knees these days...Are you associating UML with class diagrams only?QuoteWhen a UML diagram requires an A3 piece of paper in order to be printed there's only so much of it you can take in. Then break it up into loose subsystems before you daw it in Visio or Rose. The problem in not UML but more a sign of a weak design. // Our inability to process too much information is a fact, as here:The magic number 7Yes, class diagrams only. I don't find it much help when working on a new subsystem. I usually end up having to do a trace.When things like allowing for future expansion are built in, more-than-likely by indirection, things get messy. I'm not at allsaying UML is entirely useless.Bought your book by the way, look forward to playing around with stuff.

I find Viso gives me the most flexibility. Used Rational Rose quite a bit - but Visio is better at drawing and placing shapes on pages.The Class Diagram tool in MS VS 2005 is nice - but obviously only caters for the Class Diagram.

Oh yes. Visual Paradigm is quite decent too. Think they have a free version.

QuoteOriginally posted by: ioancwI find Viso gives me the most flexibility. Used Rational Rose quite a bit - but Visio is better at drawing and placing shapes on pages.And there is a huge pri$ce difference. RR costs an arm and a leg and much of it does not correspond to the way real programmers work. Like Japanese auto manufacture, much but not all activities are automated. But managers like these tools.

White boards work fine too. You just need the ones that print off a copy.....

QuoteOriginally posted by: ioancwWhite boards work fine too. You just need the ones that print off a copy.....Yes, and flip-over charts are also great because you can tear the chart, fold it up and bring it to the next meeting. It works well. Every project manager should have one. The ideal dimensions of a white board are 3 metres X 1.5 metres, many of my students take fotos of the contents of the white board.

More than once I've had to send JPGs of UML diagrams, we knocked up.

QuoteOriginally posted by: DCFCMore than once I've had to send JPGs of UML diagrams, we knocked up.This is a read-only format. Is there a possibility of red lining for the receivers of the drawing? Why?