Wow. Yesterday I attended Borland's "Accelerating the Application Lifecycle" seminar in the Washington DC area. I was extremely impressed. They showed how Together, StarTeam, and Optimizeit are *seamlessly* integrated into JBuilder and C#Builder (alas not in Delphi 8 [codenamed Octane] I made a bit of a stink about that). You change a bit of code in JBuilder, and the class diagrams are automatically updated in Together - and of course, vice versa. Better yet, with CaliberRM, you can actually trace what requirement and what use cases are affected by the code change. And then you can quickly see how your change affects performance without leaving the IDE. Make a change to a Bean in Together and JBuilder writes the code, packages the JARs and updates both the client and the server in one step. Oh, and version control is seamless. It's not just check-in and check-out. FINALLY, the dream of UML/USDP has been fully realized. This is no small accomplishment. In what is effectively ONE tool, you can: document and version requirements; perform impact analysis on requirement changes; build your use cases, sequence diagrams, and class diagrams; produce your code; test your code; and deploy it. ALL with full tracability: that is, "This requirement drove this use case which is fulfilled by these classes acting in this manner, and here is the code for it." What this means is that if the pointy-haired boss wants to change a requirement, you can instantly show a compelling graphic of all the classes that would be affected by the change. Contrast this with what else is out there. I've used Rational's Enterprise Suite for 3 years. Their own tools don't talk to each other. ReqPro is document-centric and doesn't do a good job of versioning requirements. ReqPro and Rose don't talk to each other. And while Rose can generate code, that code would have to be compiled in another package. As soon as a single line of code is changed, the model no longer reflects the code and is rendered useless from a management point of view. If you add a method in the class diagram, it doesn't show up in the sequence diagram. You can open a file in JBuilder, view it as a sequence diagram and immediately see all the classes that are involved and all the messages being invoked. An automatic refactoring capability was impressive as well as being able to apply design patterns to existing code. As usual, Borland has the best technology out there. I just hope that they can get the word out. I sure was impressed. I just spoke to my customer, and we're definately getting CaliberRM and Together ($20,000).