,
Zircom is one of the links when you get to the EA site.
I support the UML Distilled recommendation given by pneutam above.
Another book that you might want to take a look at is Use Case Driven Object Modeling with UML, A Practical Approach, by Doug Rosenberg and Kendall Scott.
The disclaimer is that the recommendations are made kind of in a vacuum. What do you need to do? UML is a large beast, and 80% of things you'll be able to do with use cases, class diagrams and sequence diagrams.
Our development process has an analysis phase, but we do not produce an analysis model--as suggested by the Rational Unified Process. We just produce the use cases and the requirements that do not make it into the use cases. We call it a system specification.
After that we go into a design phase, and depending on the size of the project, we come out usually with one document per component identified. Each document contains use cases or use case realizations from the main system specification document.
Again, what we use the most is...use cases, class diagrams and sequence diagrams :-)
Ocasionally we use state diagrams and activity diagrams, whenever the flow is more complex, but as I said, class and sequence diagrams cut it most of the time.
So, after the ride bought with my two cents, take UML with a grain of salt. At the end of the day it is just a tool to convey design, and you do not need to master every single UML detail to provide a good design. Besides, providing more detail may not be permissive, particularly when you're constrained with time. In addition, detail is expen$$ive. You must strike a balance to provide just the right amount of design. How will you determine it? Usually, by the number of trips the developer pays to your office. The least the better.
A software development process helps immensely, too. If you do not have one, convince your company to adopt one. You can start small--Agile Development I think is called nowadays, or adapt RUP to your organization, or go with larger ones (CIMM?)
Regards,
Javier
