Documentation of Microsoft sample apps

Any minute now I'll maybe get the time to really have a thurough look at Microsofts Windows forms sample app TaskVision. I would have had a pretty good idea about how it is built now though if they (Microsoft) would start using UML to document their samples. The guys at EMEA that are working on the new Patterns & Practices initiative are using UML for all their work, which is GREAT. Probably it has something to do with most of them beeing former j2ee wiz's.

If I get the time I'd like to sit down and make the diagrams. I'd like everything in the 4+1 view: Use Cases, Logical View, Deployment View, Component View and so forth. I'd like package diagrams for the namespaces and class diagrams for the important classes.

Instead of UML i see clouds, boxes, computers, and funny looking humans all connected with all kinds of arrows, lines and graphics. This should be considered the same way as a house documented with crayons on a napkin. The house might be fantastic, but it's hard to tell for sure.

I did notice btw that TaskVision has a good example of the concurrency functionality in ado.net that maybe Frans would be interested in with his concurrency dilemmas.