Let's talk UML design!

Calling all aspiring software engineers, have you come across Universal Modelling language yet? Meant to simplify designing programs, it can be used as a means by which business personal, designers and software programmers can meet on the same level to create new applications and what-not.

I've been modelling object instances on paper on and off for the past few weeks, doing class diagrams themselves and several object diagrams. Whilst that's been fine, my lecturer's been giving me sheets of paper full of questions based on UML itself to fill out, and whilst I've been doing most of it, he still somehow gives me less marks than guys who had only a portion of the work done. But look, I could go on about the bore that is my Software Development module lecturer.

Let's deign to keep on topic here; So, UML designing: Like it? Loathe it? Have you used Rational Rose yet to make diagrams consisting of use cases and actors to emulate program functionality? Say it all here!

And for those unfamiliar with UML;