I will say this about UML: some of us are visual people. As the token Left-Handed guy in the software world, I admit, I see the world in somewhat visual terms. I think some UML is valuable. Class diagrams, obviously. Sequence diagrams, sometimes. Use case diagram, rarely. But this goes to a larger issue with UML:
UML is not a process.
Is RUP dying a miserable death? Yes. I admit, I still think Coad is a demi-god in the OOAD world. Actually, even if you “know” the UML “answers” on the IBM cert exams, you are likely overly ceremonial. However, if UML is suffering it is because of this one fact:
People don’t pay for tools anymore.
TogetherJ 4.x was amazing. That was the last release before it became redonkulously expensive, but I loved it. Today I use NB. There are a couple of commercial UML tools, but Sun has a free UML tool for NetBeans that round trips. Frankly, the problem with Sun’s is the printed output blows, and they certainly don’t have the fantastic integrated UML/JavaDoc output that I remember so fondly from Together.
Is UML dead? No. However, I think UML documents have a place in the Agile world that they have lost. The problem is UML-as-Process was never really a great idea. UML-as-documentation in an Agile-Refactoring-CI world: sure. Someone just give us the tooling at a reasonable cost, and UML will come back with a vengeance.