Folks

I've just posted the first set of exercises on class diagrams for .NET
developers. Solutions will follow in the next week or so, plus the
second - harder - set of class diagram exercises.

You'll discover that there are several different ways of interpreting
class diagrams in relation to code. There's a literal translation,
which I find less helpful because it often misses the design intent
(eg, modeling a relationship between a business object and an
ArrayList instead of a 1..* association between two types of business
object).

I'd be interested to see what interpretations you can come up with :-)

Jason Gorman
http://www.jasongorman.co.uk