Hello Egor,
Being a bit new to this myself, I *may* be leading you
down the wrong route...
I
would be inclined to illustrate given instances of a Use Case by means of using
a sequence diagram - this allows the sequence of events over time to be modelled
and also allows you to demonstrate the behaviour under a given
circumstance.
Hope
this helps
Regards
Coli
-----Original Message-----
From: Egor Shokurov [mailto:[EMAIL PROTECTED]]
Sent: 29 November 2000 12:13
To: [EMAIL PROTECTED]
Subject: (ROSE) Use Cases scenarios - newbie question
From: Egor Shokurov [mailto:[EMAIL PROTECTED]]
Sent: 29 November 2000 12:13
To: [EMAIL PROTECTED]
Subject: (ROSE) Use Cases scenarios - newbie question
Hello
We've just started using Use
Cases to document/design our project.
What I can't get is how to
define scenarios ( ie sequence of actions )
on Use Case diagram. Is there
any standard way to do that or I just
need to put all this into
documentation ? Or draw additional activity
diagram ?
For example the Use Case
"Distribute a survey" should include
"Enter list of emails", "Enter
start/stop dates" etc. etc. done in the
exactly same sequence. If any
of steps fails, whole Use Case fails.
That's too simple sequence for
activity diagram and too long for
documentation. I tried to add
one more dependency stereotype
"follows" - but it makes
diagram overloaded.
Please if you have any solution
for this, post it here as it can be useful
for all use case
novices.
Thanks in
advance
Egor A. Shokurov
Netreflector.com
Inc.
