Linked by Thom Holwerda on Fri 4th May 2007 14:18 UTC, submitted by FreeRhino
General Development "When you're designing and developing new software systems, it is often hard to see how all the pieces are suppose to fit together. Unified Modeling Language is one tool that allow developers and architects to ease the process and create a big picture before committing to a particular technology."
Thread beginning with comment 237162
To read all comments associated with this story, please click here.
On UML 2.0 and Umbrello
by eivind on Fri 4th May 2007 15:11 UTC
Member since:

The author seems to have a very clear understanding of UML 2.0, however the introduction is extremely brief---too brief. Also, it's not really an introduction to UML in itself, rather an article about his tool "Ubrello" (I will give it a try for sure).

He also holds the Use Case and Class Diagram as the two most useful diagrams in the UML 2.0. Although being very useful in itself, the biggest drawback with the Use Case diagram is the rather weak link with the rest of the UML Model.

Sequence diagrams are at least as important. They are completely interlinked with the UML Model, and together with Class diagrams they almost make up an entire "mini UML specification"---two powerful ways to express the static and the dynamic behaviours of data.

(edit: typo)

Edited 2007-05-04 15:15

Reply Score: 3

RE: On UML 2.0 and Umbrello
by Isolationist on Fri 4th May 2007 15:56 in reply to "On UML 2.0 and Umbrello"
Isolationist Member since:

I find that Use Cases are good for communicating the functional requirements during the analysis stage. The value for me is how they are modeled and written, not Use Case diagrams themselves. IMHO, UML doesn't do Use Cases any justice and Use Case diagrams offer little value most of the time. Alistair Cockburn's Writing Effective Use Cases is excellent book to read on this subject.

Reply Parent Score: 2

RE[2]: On UML 2.0 and Umbrello
by eivind on Fri 4th May 2007 15:59 in reply to "RE: On UML 2.0 and Umbrello"
eivind Member since:

I agree with you completely. Use Cases seem to be often misunderstood. They are not drawings! Use Cases are good, structural and unambigious texts, although on a high level. They are especially useful in the initial phases, although I still have to say that they're somewhat "disconnected" from the rest of the UML diagrams. Used together with a sensible method, however, they can fit in.

Reply Parent Score: 1