Why and Why Not to use Rational Rose

That Rose V7 "only" supports UML 1.4 is, in my opinion, a minor point for several reasons.
  • UML2 includes almost everything that was in UML 1.4 so there was some new content but hardly a complete overhaul that made the prior work obsolete. Conversely, you can prepare UML 1.4 diagrams and they would easily be understood by someone who had only joined the UML camp with version 2. 
  • Many tools say "supports UML 2" but some of them shameless take advantage of that UML 1.x is a subset - same product, new label. Some support UML 2 selectively and added support for pieces of the new notation. I've found very little comprehensive support for UML 2 so far. 
  • Not using the latest and greatest notation is a very rare source of project failure. Using established notation exceedingly poorly is vastly more common. So is hopping from one "silver bullet" to another. 

Some general reasons to stick with ose V7 include:
  • Availability of skilled staff. Rose V7 follows the Rose 98/2000 to 2004 product line and many people know those products so it may be easier or cheaper to use them instead of re-tool. 
  • Very good multi-language support. Rose V7 remains a very strong product if you want one model and to connect that to code in multiple languages - e.g. C++, XML, SQL, Java, etc. 

More convincing reasons to leave Rose and go to another product would be:
  • If you are doing development in the J2EE set of technologies, RSA and other tools fit better into the workflow. 
  • If you are doing "real-time" development, Rational Rose real-time and other tools have better support for this type of work. 
  • If you need a lower cost per seat, there isn't really a Rational option but there are very popular alternatives that cost less. 

- Brian