Yeah, I tend to spec out things in UML quite often -

Usually for only for 2 reasons tho -
  1. I can't work out how the hell something is going to work, so I need to define it down on paper
  2. I'm required to due to documentation specificatations.
But I do find UML a good tool. For me - Class, State and Activity Diagrams, as I don't have to do work on Business requirements in my role.

It's one of those ones that really doesn't take long to learn, but is useful because everyone else knows it.

Mark

On 4/15/05, Chad Renando <[EMAIL PROTECTED]> wrote:
I'm getting my skill set ready to earn 6-figures as a system analyst
(or just trying to un-spaghetti my application) and learning a bit of
UML.

How many of you jokers use UML on a regular basis?  My spin,
interesting stuff, valid for system architecture, but I question the
relevancy of some of the operational stuff.  Mind you, I'm only up to
chapter 10.

--
E: [EMAIL PROTECTED]
W: www.compoundtheory.com
ICQ: 3094740 --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to