Hello Jeff and Rusty,
I have adopted the following approach:
Use-Case View: Should depict the system as seen by the user(s)/actors. I.e.
I do have sligth problems using sequence-diagrams (SD), since SDs shows
interactions between objects (which are design-elements). Since we are not
to show design at this stage, you will end up with a very simple set of SDs
showing an Actor, the System to be developed (as one object), and exsisting
systems/legacy systems that is to be communicated with by our system.
Therefore I've started using Activitydiagrams at the Use-Case level. They
are perfect for describing the "path" through an system service to be
offered the user. Example: LogIn-scenario. I don't know at this stage which
objects I need to perform login, but the customer has his requirements to
the steps to go through. I.e. 1) User/Actor Requests to LogIn 2) System asks
user for username and password 3) User/Actor provides username and password
4) System validates Username and password .....etc. The entire sequence can
be described in one Activity-diagram, without touching design-issues. Also,
by using the Swim-Lane layout of an Activity diagram, you can indicate which
"role" is to perform which activity. And on top of all this, you can show
alternatives in the same diagram (like what if user provides wrong password
etc.)
Then in the logical view, I have Use-Case realization(s). One or more Use
Case Realizations pr. Use Case (depending on the system to be designed...).
The Use-Case Realization is (in my mind) the first step in the design of the
system. Hence this is where I'll start using sequence diagrams. First I try
to identify "analysis classes" (i.e. of stereotype <<boundary>>, <<entity>>,
<<controller>> etc.), and through iterations the analysis-classes are
"converted" into "real" classes (or intsances of classes off course...),
until I have a sequence diagram from wich I can start to code...
I have found this to be a very useful way of structuring the UML-model of
the systems I've been working on. It does seperate the users domain from the
design in a very clear way, and it provides flexibility for alternativ ways
of designing the same type of functionality (through multiple Use-Case
Realizations pr. Use-Case...).
Regards
Arne
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff James
> Sent: 21. november 2000 02:37
> To: Williamson, Rusty
> Cc: 'Rose Forum'
> Subject: Re: (ROSE) Use Case Activity Diagram Location...
>
>
>
> I place activity diagrams, sequence diagrams, and state charts
> associated with a use case in
> the use case model during the initial analysis in an effort to
> document the use case
> description more clearly. These sequence diagrams would not be
> describing interactions
> between instances of classes but would be representative of
> actors, domains, and early
> guesses at objects.
>
> In the logical view in my use case realisation I place the
> sequence diagrams for a specific
> use case. Within the logical view I'm looking at interactions
> between actual instances of
> classes and interfaces in the model. I also place my "View of
> participating classes" in
> these use case realisations.
>
> Cheers,
> Jeff
> "Williamson, Rusty" wrote:
>
> > Hello,
> >
> > We recently took the Rational OOA&D class which was very good,
> however, it
> > did leave one point of confusion regarding secondary diagrams (activity,
> > sequence and statechart diagrams) for use cases. These
> diagrams show the
> > dynamic aspects of use cases (basically more detail regarding
> the primary
> > and secondary scenarios found in the written use case) -- in other words
> > they show an external view of 'what' the system does and would
> seem to me to
> > be part of the use-case model. In fact the course material
> indicates that
> > they are part of the use-case model and, the course CD contains
> an example
> > which also shows these diagrams as part of the use-case model.
> On top of
> > this, in Rose, if you right click on a use case, it offers the option to
> > create these and, if you take this option, it also places them
> within the
> > use-case model under the related use case.
> >
> > However (and here's the point of confusion), several students asked the
> > instructor where these diagrams belonged and she specifically
> told them that
> > 'now' the convention was to place these diagrams in the Logical
> View under
> > the use case realizations.
> >
> > Does anyone know anything about this? Are we mistaken, or does
> Rational now
> > say to place these diagrams with the use case realizations in
> the Logical
> > View?
> >
> > Thanks!
> > Rusty
> > ------------------------------------------------------------
> > Rusty Williamson
> > > Sr. Systems Architect
> > GERS Retail Systems
> > http://www.gers.com/
> > The Object Workshop
> > http://home.san.rr.com/williamson/
> > Home Page
> > http://www.znet.com/~rusty/
> > ------------------------------------------------------------
> >
> > ************************************************************************
> > * Rose Forum is a public venue for ideas and discussions.
> > * For technical support, visit http://www.rational.com/support
> > *
> > * Admin.Subscription Requests: [EMAIL PROTECTED]
> > * Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
> * Other Requests: [EMAIL PROTECTED]
> *
> * To unsubscribe from the list, please send email
> *
> * To: [EMAIL PROTECTED]
> * Subject:<BLANK>
> * Body: unsubscribe rose_forum
> *
> *************************************************************************
--
<X><<>><X><<>><X><<>><X><<>><X><<>><X>
Jeffrey James, Sr Design Engineer
Tait Electronics Ltd.
Christchurch, New Zealand
<X><<>><X><<>><X><<>><X><<>><X><<>><X>
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
