Scenario step description

[rnv]

Hi,

I have use cases with scenarios (strcutured specification). Scenarios has multiple steps.

I have created activity diagram and test scripts based on this scenario steps.

I need to enter descritpion on each individual scenario steps. These description should be in RTF documentation below individual steps as follows:
- Step 1
   Description 1
- step 2
   Description 2

how is it possible to include description of indivual steps in EA?

will really appreciate.
rnv

[Gary]

Add the description to the notes section on the activity that has been generated from the use case scenario step.

Then do an rtf report on the activities.

Having said that a use case step should be descriptive on its own. In Writing Effective Use Cases, Alistair Cockburn describes a use case step as "a simple action step".
The goal and description should set the wider scene and explain the context that the use case operates under.

If you find that you are adding a lot of comments on use case steps consider revising the use case or breaking it up a collection of simpler use cases.

Alternatively remember that a use case is only one third of the picture. the whole picture is described by the combination of use case, sequence/interaction diagram and state diagram.

Appologies if this sounds like a tutorial rather than an answer but I get this question a lot at work.

Gary

[Graham]

When building the RTF you need to include Element -> Scenario -> Structured Scenarios, the description is accessed by including the Scenario_Structured.Action field. There are other fields relating to the scenario steps available.

[Ian Mitchell]

It would be really good if a future EA version were to remove this strange 'scenario step' creature, and replace it with a 'proper' element e.g. Action or Activity, or maybe even a new one. Then the links between steps and other elements would look just like other element-to-element links, and scenario-steps wouldn't be the second-class element which they are at the moment.
And whilst they are in there, remove the restriction that Alternates can't have Alternates. Yes, I know its not perfect style to do things that way, but sometimes we all just need to break the style a little.
The Structured Scenario editor is such a great bit of function, its a shame it looks rather like a late add-on, rather than a core piece of the tool.

[Gary]

I use EA for SysML rather than UML and the number of times I come up against the alternates cannot have alternates issue is quite often even for simple use cases.
Consider for example wanting to run an alternate for a set number of iterations.

Going off topic I know but grrrrrrr.

There I am better now

Gary

[Ian Mitchell]

Perhaps there should be a 'therapy' thread, which is is write-only, no-read.

[rnv]

Thank you all for your replies.
I already have RTF templates that prints out scenario steps. I agree with Ian that would be better if EA in future have better connection between scenario structure and elements like Action or Activity.

Anyway to resolve my issue i just used the unused field 'Uses' attribute of the scenario steps to store description.