Use cases for UML

re: Use cases for UML

Pat McGovern — Wed, 15 Dec 2010 10:19:05 GMT

#3, #1, #2

In order to satisfy #2 & #1 I think we've sacrificed some of the simplicity that allowed for effective communications.

That being said, once the communication is agreed upon, it would be nice to be able to use those diagrams for #1 and #2 so that it's not just a drawing exercise (valuable as that is) but that the materials used can be taken to the next level.

re: Use cases for UML

CCVirginia — Tue, 14 Dec 2010 01:46:54 GMT

Yes to all - because all are a part of any systems design, and a view of the system is where code is lacking and visual paradigms shine. Any view of a system has to be able to cover all the aspects of that systems design - communication (#3), systems synthesis (#3) and implementation components (#1). Why should we have only part of the solution?

re: Use cases for UML

Jim — Fri, 19 Nov 2010 00:44:04 GMT

Perhaps the need for #2 is greater, but UML would be better served trying to be #3.

re: Use cases for UML

rjcox — Thu, 18 Nov 2010 15:40:00 GMT

Also #3.

Using the pieces of UML that are useful in this role, drop unnecessary details and adding anything that will help communicate. If the communication is long term (e.g. part of a design overview document) then I'll be a little more formal. But always the language has to serve the communication, not the other way around.

re: Use cases for UML

iamleeg — Thu, 18 Nov 2010 11:19:33 GMT

Definitely #3. I don't tend to use diagrams except when I'm writing a book, or talking to another developer over a pad of paper or a whiteboard.