Arguably, class diagrams are the most often used ... Generalization is the UML element to model inheritance. In Java, this directly translates into use of the extends keyword.

Using sample class and sequence diagrams, you can see how UML conveys unambiguous code ... Also, notice the structural inheritance relationships depicted on this diagram that weren’t apparent ...

Even though I have Team Suite MSDN subscription, since we run VS2008 apparently we can't use the "reverse engineer solution to Visio UML class diagrams" functionality that VS2005 had. Thanks ...

We are not opposed to UML: there are certain things that a UML class diagram can render much clearer than the forms described above. Inheritance is one example: the DSFA application used inheritance ...