resetting the numbering of steps in the use case scenario

[slavok1]

I do not know if it is a bug or feature (if yes then very strange). When I write a scenario with list numbering, then in case of inserting list bullet points (full stop) between 2 numbered steps (as I want to use the second level of structuring within the one-step), then EA makes the reset of the numbering and numbers starts again from 1.

Situation looks like next:

• step
• step

• sub step
• sub step
• sub step

• step
• step
• step

I tried to use sub-steps in the scenario, but the second level of numbering does not exist, so I hoped that bullets can be used inside.

I also tried to use a structured scenario but there is also not possible to do the second level of numbering (or using the bullets).

The only solution I can use is to use manual own numbering (then I can use the second or even third level of numbering), but the problem is if there is a new step inside the scenario, then everything has to be renumbered manually.

Maybe this topic was already solved within this forum (I am new and did not find any).

Could anybody advise how to solve this problem?[/list]

[Geert Bellekens]

I can only suggest to use structured scenario's instead. It supports just enough to avoid creating massively complex scenario's (with sub-sub-sub scenario's)
We have used those extensively (hundreds if not thousands of use cases) and never met a case that couldn't be solved

Geert

[qwerty]

When I wrote Cockburn-style UC scenarios I just ended up using plain text and doing the numbering manually. However, I only used textual description with simple scenarios. In any case where it was complicated (i.e. several nested if clauses) I used activity diagramy. Never did I use both for the same UC since that way one never knows which is the truth: the text or the diagrammatic description.

q.

[wivel]

I fully agree with both Geert and Qwerty on this.

I have used, and taught, Cockburns UC style for decades and on of the pitfalls can be overly complex and really deeeply nested UC descriptions. Using the structured scenarios in EA helps you keep our UC descriptions simpler and easier to both read and use further in your design and development efforts.

If I have UC's that cannot be described using the structured scenarios, it is usuall because:

• The Use Case needs to be split up
• The Use Case is of a complex nature, where other tools as e.g. Activiy or Sequence diagrams or an Excel matrix is a better choice

Henrik

[slavok1]

I can only suggest to use structured scenario's instead. It supports just enough to avoid creating massively complex scenario's (with sub-sub-sub scenario's)
We have used those extensively (hundreds if not thousands of use cases) and never met a case that couldn't be solved

Geert

If I understood correctly, every step which has nested sub-steps is taken as a single alternate scenario.

However, the problem is also that I can't use text edits like Bold/italic/underline, text color and others within a structured scenario.

Another problem is that if I want to copy the whole scenario to the clipboard, I can't do it as CRTL+A and also I can't delete more than one step of the scenario at a time. It's very hard to edit. Maybe there is more problems, I just wrote the problems that came to my mind now.

Also thanks to Peter and Jim for their reply

[Richard Freggi]

I may be wrong but I suspect that you are using the use case scenario as a stand-in for sequence diagrams.
You can get the same result more easily by limiting the text description of the use case to just the end result the Actor wants, without reference to the steps to achieve it.  Then append a sequence diagram to the use case - sequence diagrams are perfect for describing steps, special logic, sub (scenarios (fragments)) etc.  Same result, but easier, cleaner and more extensible to changes, new requirements etc!

[slavok1]

I may be wrong but I suspect that you are using the use case scenario as a stand-in for sequence diagrams.
You can get the same result more easily by limiting the text description of the use case to just the end result the Actor wants, without reference to the steps to achieve it.  Then append a sequence diagram to the use case - sequence diagrams are perfect for describing steps, special logic, sub (scenarios (fragments)) etc.  Same result, but easier, cleaner and more extensible to changes, new requirements etc!

Thanks for the reply, but I have not thought sequence diagram for this case.

I am searching for the best way how to record use case scenarios of all scopes and to have the best benefit from using the EA

[qwerty]

I would not recommend SDs here. They are intended for object collaboration. Either use Activity diagrams or plain Cockburn for simple scenarios. Instead of ADs you might look into BPMN. Gives you a lot more details but takes some effort to learn it in detail.

q.