Scenarios

[Mabb]

Hi everyone,

maybe I'm missing something here, but it seems that the interface for entering UC scenarios makes it way more work that it needs to be.  Frankly, I wouldn't use it if it didn't offer the useful feature of importing them into test scenarios and perhaps even that's not worth the extra time it takes.  I'm perservering because I want all my doco in one place, but I'm also trying to be Agile here, and the scenarios interface just isn't doing it for me.

Is there a way that I can import scenarios from a list in another application (csv, text list, rtf).  I find the dialogue box a pain (new, save, new etc) and editing to add more detail a bigger pain.  Even when I number them, it doesn't sort them properly and I'm forever sorting and resorting going up and down (groan).  

How do y'all get your scenarios into your use cases?  Have I missed some easy way to do this?

thanks in advance

[fluxtah]

I have to agree here, the scenario dialogue just about works for me but with great awkwardness, I am following a UC style that I am particularly fond of using {Extention Points}  (following www.usecasemodeling.com book)

The Scenario dialogue provides little support for this style, to make better readable UC descriptions it makes more sense for me to use ms word or something that has better text formatting capabilities.

I know some would disagree but not having the ability to format the text in these boxes in any manner doesnt help much presentation wise :|

[Ozzone]

Any follow up on that ?

I have the same problem as Mabb: trying to make UC description all stand in one place (EA !) does not seem easy.

The way I would do it is to build up the Use Cases in EA. then export them in CVS. Write down the scenarios in a spreadsheet program. Then import back.

Then I would build up the Test Cases from my use cases and do the same.

Technical problem : I could not figure out how to select the scenarios as exported fields (in fact I always see the same basic available fields whatever the selected element types are).

Related organizational/conceptual problem : It seems a pain to maintain the use case and test case synchronized. Any idea how to do it ?

Suggestion : maybe we should also look at the XML export rather than CSV. But then what tool should we use to process them easily ?