I haven't used VSAE/Viso yet.  Generally speaking, an association is a
static relationship between two classes.  Associations show dependencies
between classes, but not actions.  Two primary types of Association are
aggregation and composition.

Read through a book on modeling with UML, or browse the web.  It will help
immensely.  Sorry I can't help you with the EA version of VS.  I only have
the Pro version now.  No budget for EA until June 1 2003 :(


-----Original Message-----
From: Mathieu Rachlin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling


Thanks Joe!

With regards to VSAE/Visio, do you have any idea what the "Association Ends"
are for on a "Communicate" link. (Which is what, I assume, one uses to link
an actor to an action/use case.)

In all of the Use Case diagrams I've seen, there are no names listed for the
AE's...

- Mat

-----Original Message-----
From: Myrick, Joe M. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 2:44 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling


Yeah, I have about 3 other books on Use Cases and 4 or 5 on the rest of the
Unified Process ;)

The one I suggested is a condensed methodology that I've found useful.  I
wear all the hats.  (Analyst, Designer, Developer, etc...)

Anything by (Booch, Rumbaugh or Jacobsen) is good.  They all have their
specialty.

Good luck.

-----Original Message-----
From: Mathieu Rachlin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 1:22 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling


Before I go out and buy this book, does anyone have any objections and/or
differing opinions?

=)

- Mat

-----Original Message-----
From: Myrick, Joe M. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 1:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling


Also, check out:
        "Use Case Driven Object Modeling with UML"
        ISBN: 0201432897

Joe...
-----Original Message-----
From: Steve Holak [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 12:28 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling


Mathieu,

Generally, Use Cases are a vehicle for a business analyst to capture the
user interaction requirements of an application, and confirm with the user
that  they are all on the same page and that all the needs have been met.
They're written in a language that a user can understand; they're the first
part of the bridge spanning the gap between the user requirements and the
actual code that implements the application.

Here's some good refernences on the subject (and UML) that I leveraged for
a presentation on Use Cases within our company:

?    http://www.omg.org/
?    http://www.uml.org/
?    http://www.pols.co.uk/usecasezone/index.htm
?    http://www.unantes.univ-nantes.fr/usecase/
?    http://www.zoo.co.uk/~z0001039/PracGuides/pg_use_cases.htm
?    http://www.platinum.com/corp/uml/uml.htm


Steve Holak
Senior Software Architect

Brokerage Concepts IS Dept.
610-491-4879

email:  [EMAIL PROTECTED]




                    Mathieu Rachlin

                    <mathieu_rachlin@MARKE        To:
[EMAIL PROTECTED]
                    TREND.COM>                    cc:

                    Sent by: dotnet               Subject:     [DOTNET]
Enterprise Architect - Visio Modelling
                    discussion

                    <[EMAIL PROTECTED]

                    P.COM>





                    04/30/2002 12:06 PM

                    Please respond to

                    dotnet discussion









Hi everyone,

This is actually my very first post. I just wanted to take a moment to
thank everyone for keeping things so active in here. I find that even by
just being an observer, I'm learning alot about .NET (vicariously
however!).

I installed VSEA today as well as Visio. I'm somewhat new to formal
architectural diagrams but I believe that I understand the fundamentals
quite well. Where I'm having some confusion is with regards to the
transition between a "Use Case" and a "Static Structure".

I've noticed that you can setup all sorts of things like operations and
their arguments. You can even specify what their types should be. This
leads me to believe that, based on a Use Case, one should be able to
generate, to some capacity, a Static Structure.

Is this true? Otherwise I don't understand the point behind drilling down
to such detail in a Use Case...

Thanks!

- Mat

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.


You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to