>As far as tool is concerned, I highly recommend you Enterprise Architect. It is very nice and the price is reasonable for a modeling tool: http://www.sparxsystems.com.au/
>
>The use of UML depends on what you are trying to do: Are you working on a new project or on one where you've been working for years? How many developers are in your team? Who will use/read your models?

2 different projects. 1 1+ years old and another new!!!

They are with differnt clients. Old project is myself and another. New project is with 5-7 people, and I don't expect them to do much input, really have the models as design building on the front end. So 2 maybe 3 people in editing of the UML.

>I usually use UML to accomplish 2 goals. One is to reverse engineer an existing system, and create class diagrams with the important (to me) classes on it and their relationships. The second goal is to show others how a system is/will be organized.
>
>I don't use UML for code generation nor do I think people should be using it for that :)

I have to re-engineer one app, so I can extract web based functionality and put out an WIN app very similar to their web. Other is to start the second clients new financial app from the ground up.

The Fin app needs allot of business classes and as I scope their existnace I want to push a button and those .cs files are created with empty functions that I've described in the UML.

>CRC are a nice technique, although they have nothing to do with UML (not that that is a bad thing)

I like CRC in presentation to the code team, and as a first draft for Testing.

>I have a whitepaper on the use of UML that you might be interested in:
>
>http://www.hectorcorrea.com/DotWiki.htm?topic=ApplyingUmlInYourRealWorldApplications
>

Small world but I was there. ;->