I like Rational Rose for UML modeling. The user interface takes a little getting used to, but it more than makes up for it as a modeling tool. Great tool for building large models and keeping the various parts consistent with one another. It supports all sorts of interesting extensions if you are wiling to use its VBScript style scripting language. Very reasonable support for group development. As of 2000, it has pretty good forward and reverse engineering capabilities. Also, it allows you to publish models to HTML. I have not tried TogetherJ or any of the other tools, so I can't compare... Hope it helps CT ------------------ C.T. Arrington Author of Enterprise Java with UML
Hi I have used TogetherJ , since I have the evaluation copy of the same I can just generate Class Diagram with it. I find TogetherJ very nice, particualy while using it with Java, How does Rational Rose compare to it, does RR have runtime code display as in the case of TogetherJ where in , when I change the function in the class Diagram the Code changes accordingly, moreover, does Rational Rose give Java Doc integration into the code as TogetherJ give. All this some more points will help me decide if I have to continue with TogetherJ or RR. I will be using these tools since I am planning to give my Architect Examinaton. Thanx
Info from our information department: RR and Together are usefull both. Together does some changes direct and automatically: change code changes (class) diagrams too or change a diagram the corresponding code is changed correspondingly.
hi all this thread was dead a while...some time passed by some new tools/versions on the market. i found this list: objectsbydesign it lists many uml tools. unfortunately there is no rating. if been using togetherJ version 6 a lot. now i work in a company who probably cant afford this (as its 3500$ + as i recon). if there is a tool out there that would do it for around 1000$...would be nice. here is what i need: - uml -> java and vice versa - class, sequence, use case, state, colaboration diagrams (i dont mind having support for more :-) ) any ideas ? thanks for sharing your thoughts. karl [ December 17, 2002: Message edited by: karl koch ]
Originally posted by karl koch: here is what i need: - uml -> java and vice versa
any ideas ?
Well, my favorite UML tool still is the whiteboard. Seriously!
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: May 25, 2001
hi ilja well, when your in the same office probably nothing beats the whiteboard. we are separated in different citys so a whiteboard wont do. uml->java: because it is comfortable....but creating some skeletons from class digrams doesnt save weeks, i agree. java->uml: to have changes in the code reflected in the diagrams (eg. attributes you missed in the diagram)... excuse me now. going to buy a whiteboard :-) karl
Originally posted by Aaron Anderson: Togethersoft has an excelent UML modeling tool that does absolutely everything you need. UML modeling,documentation, metrics, debugging, EJB deployment, everything.
They haven't publicized it yet, but they also have a plug-in for eclipse/WSAD for this. They demonstrated the plug-in for us, and it looked very nice, providing the features that you look for while leaving out all the extra "IDE" that comes with TogetherJ, which I didn't like. FWIW, I've used both Together and RR. I couldn't stand RR. Fortunately, the management above me has the same love of RR that I do.
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Daniel, it seems that you are not update. GdPro is now known as Describe. There is also Softeam's Objecteering which I quite like. There is a free download for Personal Edition. W.
Joined: Jul 11, 2001
Originally posted by karl koch: well, when your in the same office probably nothing beats the whiteboard. we are separated in different citys so a whiteboard wont do.
Uhh - I would still like to meet with those guys for some critical design sessions. For a commercial project, I would expect even airline tickets to be more cost effective than "purely distributed collaboration"... And I would even prefer using a whiteboard and sending photographs to my coworkers over using a CASE tool - but that might just be me...
uml->java: because it is comfortable....but creating some skeletons from class digrams doesnt save weeks, i agree.
It is even my experience that a diagram seems to be either optimized for communication *or* code generation, never for both. That is because you need different levels (and types) of detail for those purposes - in fact the details should even differ depending on what you currently want to communicate, shouldn't they?
java->uml: to have changes in the code reflected in the diagrams (eg. attributes you missed in the diagram)...
As I said above, I typically don't want *all* attributes to be reflected in a diagram, so I would have to maintain that anyway. All of the above might be heavily influenced by me tending to refactor very much and often, though.