import scenario or requirement as test case

[cbellamy]

I am on version 4.0.  I am in the process of building test cases and would like to not duplicate entry of the test cases to requirements or scenarios.

1. Has anyone successfully used EA to build test cases?
2. Has anyone used the option to import a scenario or requirement into the Test.  I have followed the Help instructions (see below) but cannot get it to work.  When I select an element, nothing appears in the pop up Test Cases window?

nstructions in Help:
"To display the Scenario Testing screen, open the Test Cases window by selecting Testing from the View | Other Windows submenu. Then open a diagram and select an element - all of the test scripts for that element will appear in the Test Cases window. Select the Scenario tab.

[Bruno.Cossi]

The help seems to be a bit imprecise. Select the element, then right-click in the Testing window and from the popup menu select Import Element Scenario(s) (or constraints, or requirements). That should do the trick!

Bruno

[cbellamy]

Thanks so much for your speedy response.  I still could not get it to work and experimented with the EAExample project to see if I could find a requirement or use case that would work.  

This is how I got it to work:
I found a use case (Message Package/Compose Message) where ‘importing scenarios’ into the Test Case grid worked.  I clicked on the use case properties and noticed that under the tab marked ‘Scenarios’, scenarios were set up.  I then went back to Help to look at Creating Requirements and discovered that you can create requirements at the diagram level (which is what I did) or create requirements at the package level.  If you create requirements at the package level, the package properties allow you to enter requirements under the tab ‘Require’.  I experimented with adding requirements at the package level under the ‘Require’ tab and this allowed me to then populate my Test Grid.
However, it seems more advantageous to add requirements at the diagram level because a requirement added at the package level is ‘hidden’ unless you click on the package properties.  
Please advise if you have further suggestions.

[Bruno.Cossi]

Hi,

generally I believe that every requirement should be implemented ("realized") by a Use Case, otherwise there is no pint in testing it. You do this by using the <<realize>> relationship to link the Use Case back to the original requirement.
Having said that, it does not seem to help. The requirement does appear in the Require tab as external, but it won't be imported into the Testing window (unlike any internal requirements, i.e. those entered onto the Use Case directly). Is this a bug in EA?

Bruno

[thomaskilian]

Hi Bruno,
what about non functional requirements. Many of them relate to nearly all use cases. Would you bind each of those to all use cases?

[Bruno.Cossi]

Hi Thomas,

good question. My first thought is yes, even though it would be a bit inconvenient, it still seems like the cleanest solution. What do you think?

Bruno

[sargasso]

We use the relationship matrix to do this at specific points in the analysis cycle.  This lets us do it at sessions devoted entirely to NF requirements and this gets the people to focus specifically on them and their "realisticness".

For example, having all use cases specified (generally) to the point where both the designers and SMEs are in agreement about the complexity of the use cases, we then turn to the matter of deciding specifically which of the use cases that "The system must provide sub-nanosecond response times for all actions, enquiries and reports" really applies to.  

Bruce

[thomaskilian]

Hi Bruce,
good quote. Probably the matrix will ease that work quite a lot. Honestly speaking I forget to use this feature most of the  time.

Bruno: making associations in all these cases would surely be the cleanest thing. Without the matrix trick I simply would have placed these requirements at a special location, bearing in mind that I had to look at them carefully. I still keep the special location but also I will make the association.

[Bruno.Cossi]

Hi Thomas,

it would be nice (and maybe it even works that way, I have never tried) to be able to create a <<realize>> link from a Use Case to a PACKAGE that contains requirements and that would act like creating <<realize>> to all the requirements in the package. What do you think?

Bruno

[thomaskilian]

Bruno,
that would ease work shurely quite a lot. On the other hand it's one of these nuts and bolts that blow up a tool like EA.  In Rose I would have written a macro to do that job. If I only had time I would start to explore the automation interface and see what I could get out there.

[Bruno.Cossi]

Thomas,
this could be written using EA AI easily. I love the Automation interface :-)

Bruno

[thomaskilian]

Just started to read the help file (Sparx: this help really deserves the name!) and that kicked me off  
Still I have no time, but definitely I'll start working on it.

Ciao Bruno. I have to go to bed now