Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - MichaelRuschena

Pages: 1 [2]
General Board / Re: Robustness Diagrams
« on: September 04, 2002, 04:11:06 pm »
This diagram is just what I could find that looked vaguely like what I was after. That diagram is on a web page somewhere. Thruth be told, I barely looked at it.

I don't have any capacity to post to the web, so I couldn't make my own image. (Also, I couldn't make the images I was after, cos I didn't know how to get EA to make them - that's why I made the post in the first place.  :) )

So, I agree that the diagram is wrong.

General Board / Re: Robustness Diagrams
« on: September 03, 2002, 04:46:45 pm »
Kelly, that rocks.  :D


General Board / Re: Robustness Diagrams
« on: September 02, 2002, 09:42:14 pm »
Yes, that gives the right icons. Cool.


General Board / Robustness Diagrams
« on: September 02, 2002, 05:44:41 pm »
Hi folks,

I'm trying to create some robustness diagrams in EA. (e.g. something like...)

The problem I'm having with EA is in the creation of the Interface, Entity and Control objects. In order to get the effect I'm after, I'm using a logical diagram, and using objects of sterotype 'case worker', 'entity' and 'worker'.  This is a) somewhat inconvient, and b) ends up with little men in the Control and Interface objects (what does this stick figure signify anyway?)

What I'd prefer is to have the icons available in the toolbar. (They are sort of available in the sequence diagram. But - this includes an object lifeline, and is always positioned at the top of the page.)

Is there an easier way to make robustness diagrams than changing the sterotypes of classes or objects?


Michael Ruschena

Uml Process / Re: USE CASE Cookbook
« on: February 03, 2003, 06:38:37 pm »

I just wanted to throw in another idea... I've recently been thinking about a similar issue. I write Use Cases for apps, and so do half a dozen people sitting around me. We all work in pretty much the same domain, and deliver products not hugely dissimilar.

Given this, you'd expect that we could share Use Cases. (I take it this is what is meant by Use Case cookbook.) Well, it never worked out that way. Sharing tended to lead to cut-and-paste, with minor modificiations, which tended to get lost. (Of course, it was also a rather amature effort never strongly embraced. Maybe a serious author could put together something worthwhile.  ???)

I've been thinking that the problem is that a Use Case represents a way of resolving a bunch of issues. To reuse a use case, all of these issues have to be the same. In practice, this doesn't really happen.

This lead me instead to the idea of patterns (mentioned briefly above). Instead of trying to present completed solutions which may or may not fit, I'm working at the moment to sort out the particular patterns. The idea is that these patterns can be used to build use cases.

I've been thinking about this for only a few weeks when I have time, so work hasn't progressed very far. I'll see how it comes out.

(Doug, loved Applying Use Case Driven Object Modeling with UML... I'm evangalising Robustness diagrams to anyone who'll sit still long enough    :D)


Pages: 1 [2]