Slashdot Mirror

Clearly you don't write (or at least read source for) applications of any substance as that would be mildly described as tedious if not impossible.

One of the best ways to understand code is to do so visually with the software equivalent of blueprints. UML is generally considered a very capable way of modeling/communicating both static structures and dynamic behavior of software. There exist any number of tools that are capable of reverse-engineering existing source into UML. Two tools that I consider to be more capable than others are IBM's Rational Rose, and No Magic's MagicDraw. If commercial products aren't a possibility there are likely a number of open-source/free tools--though likely of lesser ability--available. A Google search on "reverse engineering UML" should point you at some.

FrostWire is a Peer to Peer (P2P) information sharing client for the Gnutella network.

Aqua Data Studio is a database query tool and administration tool that allows developers to easily create, edit, and execute SQL scripts, as well as browse and visually modify database structures.

Maple is a leading Computer Algebra System

Columba is a very nice email client

Rio Music Manager is and iTunes like app that comes bundled with every Rio mp3 player (can be downloaded for free too)

MagicDraw is a very impressive UML modeler.

No I'm not an employee, but I use it every day. Would "native code" be faster? Of course, but not enough to make a difference to me.

I hate Rose 6 ways to Sunday, but ArgoUML doesn't do what I need. There's more to visualizing software than class diagrams, and ArgoUML's support for interaction and sequence diagrams is non-existent. If the world were sane, MagicDraw would be the tool of choice and Rose would be consigned to old-timers tales of "remember how bad the UI of that thing was?" and the Wayback machine.

Just to draw the pretty pictures, not generate code. What's good?

Not so true. The truth is a good design & implementation (search for "code generation"). Sorry, I'm biased.

Following words may be a bit biased since I work for a UML design tool company. This was a disclaimer.
If you're still here - look at the tutorial [pdf format] of it. This includes several UML examples which may be tried having the tool (this one, or maybe another). Since the tool is
written in Java, it should work on your platform. And, yes, you'll have to register before downloading
full-functional demo. I hope, this is the only inconvenience in this case.

One package to check out is MagicDraw. I used it a little bit during my OO software engineering class recently and it works pretty well. It's written in Java, but it ran well on my machines (566 Celeron/192M RAM and 500 Celeron/128M RAM). The nicest thing about MagicDraw is the trial period, which is usually around 4 months. That's long enough to take you through the remainder of the semester.

1. Break the diagram down by packages. Um, your coworker did use reasonable package groups, right? Otherwise you have a bigger problem than a few hundred classes.
2. If class A contains a vector of instances of class B, this is known an an association link, and you only need two widgets on the diagram to represent it.
3. MagicDraw UML