UML and more.
That's how an SD Times article covering VS05's new class modeling capabilities started to describe the new features. Unfortunately, I'd have to disagree. There are two main parts to Team System's modeling environment: System Designer and Class Designer. System Designer allows an architect to piece together systems based on generic components; and, Class Designer provides basic UML class diagram capabilities. The reason I say that Team System is not “_uml_ and more” is because Microsoft's intention was never to utilize UML. I remember a conference in Seattle last October where Microsoft's position was that, if customers wanted UML integration, the “community” would have to support it. I'm not surprised things have changed, but it's always funny how Microsoft acts as if it were their intention from the beginning.
Anyway, Team System is only one small part of UML - the class diagram. Future versions are supposed to include a proprietary version of UML's sequence diagram, which I am excited about; but, as-is, Team System has quite a ways to go to meet UML's capabilities. I'd like to see use case models and activity diagrams built into it, too. This would allow a complete dust-to-dust approach...well, almost.
Team System is definitely headed in the right direction, though. I'd like to see Microsoft work with OMG to improve UML, but who knows how long that will take to come out with UML 3.0 - 2.0 took long enough. The road ahead is a bright one. I'm looking forward to traveling down it.