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 - dlundy

Pages: 1 [2]
General Board / Re: Scenario Vs Test case
« on: May 05, 2004, 12:14:26 pm »
Just to add additional commentary:

A scenario in UML is a particular instantiation of a Use Case. For example, instead of saying the *Actor does* you would say *Bill, marketing manager, does..." and use specific values to exercise the path through the Use Case. In essence, that is what it is - one path through a Use Case.

General Board / Re: 3.6/4.0 Side-by-Side Installation
« on: March 17, 2004, 02:22:47 pm »
I have been prepping for UML 2 for a while so that is not a concern.

However, the "auto" update feature that converts 3.6 automagically to 4.0, is a concern.

I take it that 4.0 does this without notification?


Uml Process / Re: Anyone recommend a good analysis book?
« on: May 05, 2004, 10:10:42 am »
Just wanted to second that recommendation. Analysis Patterns by Martin Fowler is a must have!

Uml Process / Re: Use Case Arrows - what to use?
« on: October 06, 2003, 01:44:05 pm »
I wouldn't have done it that way. The foundational characteristics of a Use Case are "That it return some value to the Actor" endit. Your two use cases that do the same thing - are as you suspected - just one use case.

For what its worth in your model: I further disagree that everything ends up in procedures.(Granted its a sample) You are following the well traveled path of functional decomposition of Use Cases in your thinking - it will not lead you to where you want to be. Your referenced Domain Model contains Class Diagrams, Sequence Diagrams, etc. These are your: Objects!! (sorry pet peeve!)

The includes/extends are not intended for functional decomposition (although they are often used that way up to a point) - rather they are intended as notational conveniences (again, mostly) so that you do not have to repeat the entire content of a Use Case over again when you wish to use it as part of another Use Case.

A Use Case model centers around the Actors and their interactions (Use Cases) that provide value to them. If you constantly stick to that rule, you will find many so called Use Cases disappearing from your diagram.


Uml Process / Re: security components diagram??what is it...
« on: October 06, 2003, 01:47:56 pm »
I have never heard of such a diagram. It certainly isn't a standard part of UML: unless it is simply a deployment diagram that only displays Security Components??


I wish I could help you - so apologies that this post doesn't address your need.

I did want you to know that a number of us read your post, are hoping you create this new tool, and are cheering you on!!

Its not much..but its what I got to give!


Pages: 1 [2]