RE: (ROSE) Use Cases scenarios - newbie question

[Abbott Fleur]

When I create my SoDA reports off the Use Case View I sort the view by package name (which I use to break out independent requirements). I then sort the use cases by name which places the activity diagrams (which are also sorted by name) below the associated use case. Although this does no show me the hierarchy, it allows me to go to my Use Cases quickly.

Abbott

-----Original Message-----
From: Egor Shokurov [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 30, 2000 5:47 AM
To: Abbott Fleur; [EMAIL PROTECTED]
Subject: RE: (ROSE) Use Cases scenarios - newbie question

Abbott

 

That's really good trick !

I just was not aware that links are allowed in Notes fields.

My only concern is that information enterd in this way may

be not displayed in SoDA reports, but anyway it's best solution

of all.

 

Thanks very much to you and all I ppreciate your help in sorting this.

 

Egor

P.S. As I understand from this forum topics, I'm not only person faced

a problem of this sort, so I believe your suggestions will be helpful to

everyone.

 

-----Original Message-----
From: Abbott Fleur [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 11:18 PM
To: Egor Shokurov; '[EMAIL PROTECTED]'
Subject: RE: (ROSE) Use Cases scenarios - newbie question

Egor,

 

What we do is create Activity diagrams and the attach a note to the UseCase (in the UC diagram) and drag-n-drop the activity diagram into the note. When the note is clicked on, the activity diagram appears. I hope this is good enough.

 

Abbott

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Egor Shokurov
Sent: Wednesday, November 29, 2000 7:13 AM
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.