How many people can use UML?
 

Out of curiosity, how many people can use UML?

There's no option for "Sort of" :( As that would be me.

I'm in the "sort of" category as well, I really wouldn't consider myself knowledgeable on the subject above and beyond having drawn up some of the diagrams before for use cases, classes, etc.

I used "sort of" aswell, i've used it a couple times, but at the moment it would be quicker to make a drawing on paper than in a UML program!

lol, I guess we're all in the "sort of" category. I'm pretty knowledgeable with class diagrams, but that's about it.

Never heard of it...

Sort of.. :-)

Whats UML?(googles..)

Well, Karl created you a UML diagram in your hook thread :) ! Just a standardised way to describe a system.

I have just finished it along with OOP at my class at the university, otherwise i got nothing from that class coz the teachers suck. There are two teachers teaching a subject. This one said this and another said that!! OOP & UML sessions drove me crazy. Yet, gonna take OOP and UML exam soon..:(

Good to see they're teching UML at Uni now. When I was there (just over a year back), my tutors had only just themselves started to study it. It's a great way to model a system. Rids us of all the ambiguity of standard speech.

Unfortunately, UML study in my University is just the name; the effectiveness for the student understanding is 0. That's what i have been upset to be there, at my current university. Otherwise, Need to find out more by myself then..:) UML is really great for the OOP system performance.

been doing it on the job for the last couple years. its one of those things you just have to do... helps a lot though.

Eh I'd also go with the "sort-of" option. Don't get me wrong, UML is a great way to get your system ready and organized, but I haven't really followed the exact standard for any jobs. It also just seems to bloated to me. It tries to cover everything for all programmers.

I was doing some UML diagramming last night with two other programmers, we were able to effectively model the conceptual design of our system using Use Cases. We already had some requirements jotted down on paper (as most people do), but it was amazing to see how much ambiguity there was with the requirements, we all had different ideas of how to go about common tasks.

The Use Cases helped us to clear up those inconsistencies, we didn't get it finished, but for the hour or two that we put in we got a lot back, and I know that the time we would have lost through our misunderstandings would have run higher than those 2 hours spent.